debug-issue

A guided command for investigating and fixing a software issue. It uses project files and a staged workflow to discover the problem, plan a change, implement it, and verify the result.

In plain words
What is it for?
Use it to debug projects built with Click, pytest, or the listed architecture tools, while producing a patch plan and verification checks.
Why use it?
It gives debugging work a repeatable path instead of leaving the agent to guess where to start or how to check the fix.

Command for Claude Code

Install

Getting it into your agent

One page per mod, every tool's command on it. A separate URL per tool would split the same page into five that compete with each other.

agentmods
npx agentmods add commands/apexiq/skillsmith/debug-issue
Clone the repo
git clone --depth 1 https://github.com/ApexIQ/skillsmith

Made for: Claude Code.

Per session 0 Only the description is in the session, so the agent can decide to use it. The body loads when it is invoked.
When invoked 543 The whole file, excluding the scripts and references it only reads on demand.
Security scan A 0 findings. Scan, not verified.
Origin 83% copy Near-identical to another mod in the catalogue.
Token cost

What it costs to keep this loaded

Counted locally with the o200k_base tokenizer, which is exact for GPT models; Claude uses its own tokenizer and its counts differ. Treat this as one consistent yardstick across the catalogue rather than a bill. Prices are per million input tokens.

ModelPer sessionOnce invoked
Fable 5 $0.00000 $0.00543
Opus 5 $0.00000 $0.00271
Sonnet 5 $0.00000 $0.00109
Haiku 4.5 $0.00000 $0.00054

Measured 2d ago against content hash 1ab51842782d, method: parsed. Prices are Anthropic first-party input rates as of 2026-08-30, from the pricing page.

Security

Grade A, and why

debug-issue scanned grade A with 0 findings against 26 rules in 11 categories — prompt injection, anti-refusal, data exfiltration, privilege escalation, supply chain, agent snooping, system-prompt leakage, SSRF and excessive agency — measured 2d ago.

A static scan of the body, not an audit. Every finding is printed with the line that produced it so you can judge whether it matters here. A mod is markdown that instructs an agent; that is exactly why what it instructs is worth reading.

Nothing flagged

None of the 26 patterns this scan looks for appear in this file: no shell pipes, no recursive deletes, no credential paths, no hidden text, no instruction-override or anti-refusal phrasing, no agent-config snooping. That is not a guarantee, it is the absence of the things that are checkable.

Origin

This is a copy

83% identical to align — 12 lines differ, which has more behind it and is treated as the original. This page carries a canonical link to it rather than competing with it.

.claude/commands/debug-issue.md · 28 lines

How it starts

The opening of the file, as written. The whole thing — 28 lines — stays where its author put it; the contents beside it link to each section on GitHub.

Command: /debug-issue

This command is powered by a dynamic Skillsmith workflow bundle.

Goal

debug issue for library click, pytest, arch-business-logic, arch-ui, arch-unknown

Resources

Execution Plan

  1. Read .agent/project_profile.yaml and .agent/context/project-context.md.
  2. Confirm the requested goal against the current project stage and target tools.
  3. [AND] Discover stage: Read .agent/project_profile.yaml and .agent/context/project-context.md before taking action. Acceptance: Project profile and generated context are present or inferred without error.; The ranked skill list is deterministic for the current goal and profile..
  4. [OR] Plan stage: Turn the goal into a minimal patch plan with explicit verification checkpoints. Acceptance: The plan names concrete files, commands, or subsystems.; Every planned step has at least one verification check..
  5. [OR] Build stage: Implement the smallest coherent change needed for the goal. Acceptance: Reproduce the issue and capture the failing behavior before the fix is applied.; Implement the fix with focused verification for the affected area..
  6. [AND] Review stage: Inspect the changed files for correctness, regressions, and missing coverage. Acceptance: The review names concrete risks or confirms the change is safe.; The review output is ordered and actionable for the next agent..
  7. [AND] Test stage: Run the relevant automated tests for the changed workflow behavior. Acceptance: Targeted tests pass after the implementation change.; The failure mode is observable if the stage structure regresses..
  8. [AND] Ship stage: Make the workflow output usable as a release-grade handoff artifact. Acceptance: The generated workflow includes both stage structure and the legacy steps list.; Compose output remains stable across repeated runs with the same inputs..
  9. [AND] Reflect stage: Summarize what the evidence says about the current run. Acceptance: Reflection text is grounded in the run's actual feedback or retry state.; Any mode suggestion comes from the current evidence, not a dummy rule..
  10. Load the top relevant skills: notebooklm, loki_mode, javascript_testing_patterns, makepad_skills, context7_auto_research.
  11. Verification loop: run 1 verification pass before completion.
  12. Run the most relevant test or validation command before completion.

Read the full file on GitHub · 28 lines

Changes

What this file has done since we first saw it

Hashed on every crawl. A supply-chain change to an agent config is a question of when, not whether, so the history is kept rather than the latest state alone.

  1. 2d ago First seen · 28 lines · 0 tokens per session scan A 1ab51842782d

Subscribe to this mod's changes

debug-issue is a command published in the GitHub repository ApexIQ/skillsmith (5 stars, last pushed 5mo ago), licensed MIT. It costs nothing until one of its globs matches a file; then it loads 543 tokens. A static security scan graded it A with 0 findings. It is 83% identical to align, differing in 12 lines, and is treated as a copy.