Skip to content
Back to skills

Dev Troubleshooting

ASecurity

Diagnose Shopify CLI, API, auth, webhook, UI, extension, and deployment failures.

  • 2 stars
  • 0 votes
  • 0 copies
  • 0 views
  • Added October 1, 2026
ai-agentsapidocumentation

Works with

  • cli
  • api
  • mcp

Security analysis

A100/100

Scanned October 3, 2026

npx -y skills add khadinakbarlabs/shopify-app-builder --skill dev-troubleshooting --agent claude-code

Installs into .claude/skills of the current project.

Are you the author of Dev Troubleshooting?

Add the live security badge to your README. It updates with every re-scan.

Security grade badge for Dev Troubleshooting
[![Security: A — Skills Directory](https://www.skillsdirectory.com/api/skills/khadinakbarlabs-dev-troubleshooting/badge)](https://www.skillsdirectory.com/skills/khadinakbarlabs-dev-troubleshooting)

More formats (shields.io, HTML) on the badges page. Keep it an A: scan every change in CI with Pro.

Download with Pro
SKILL.md
---
name: dev-troubleshooting
description: "Diagnose Shopify CLI, API, auth, webhook, UI, extension, and deployment failures."
---

# Fix one problem without making a mess

## Start here

A reproduction is a reliable way to make the same failure happen again.

First useful outcome: Capture one redacted error and reproduce it safely.
Ask only for missing information that changes this task. Inspect the existing project and use synthetic data before touching a merchant store. Explain the next action and its expected result in plain language; offer a recommended default with its tradeoff.

## Guided workflow

1. Ask only for the error, where it happens and last known working state; inspect non-secret versions and config.
2. Choose the focused skill for the failing layer and test a specific hypothesis with read-only checks.
3. If fixing is requested, write a regression test, make the smallest change and preserve unrelated edits.
4. Reproduce again and report evidence; use recoverable cache backups only after proving cache involvement.

## Check it worked

State confirmed cause, exact change, regression result and anything not tested live.
Report what was changed, what was tested, and what still needs account access or live verification. Do not claim production readiness or approval from generated code alone.

## If you get stuck

Never read auth caches, print .env/session tables, uninstall everything, or run guessed CLI subcommands.
Give one safe next step and a redacted error example, not a list of speculative fixes.

## Safety and optional depth

Use only the user's selected project/accounts. Never read credential caches or request secrets in chat; the operator configures the application's approved secret store. Ask before live deployment, store mutations, billing, publication or paid runs unless that exact action is already authorized. No MCP service is required by this plugin.

For concrete examples in an existing project, read only the relevant section of [technical-guide.md](references/technical-guide.md). These retained v1.x examples are version-sensitive, not the default template. Verify SDKs, schema fields, CLI flags and platform rules with [official documentation](https://shopify.dev/docs/api/shopify-cli) before using them.

Example request: "Use dev-troubleshooting to help me with this task. Explain each change and verify it before moving on."

Attribution

Is this your skill, or is something wrong with this listing? Request removal or report an issue. Author removals are honored within 72 hours.

Comments

Loading comments…