Skip to content
Agentmart
Submit a tool

debugging

Diagnose defects systematically by reproducing the issue, isolating the failing layer, testing hypotheses, fixing root cause, and adding regression protection.

Skill by PHENOMVALENCE

IndexedMIT
Write a review

Install

Works with Claude Code, Claude apps, Codex, Cursor, Gemini CLI, GitHub Copilot, VS Code, OpenCode, Goose, Windsurf. Read the repository before you give any tool access to your data.

npx agentmarket install skill/phenomvalence-debugging

Asks which of your tools to add it to (Claude Code, Codex, Cursor, VS Code, Windsurf, Gemini CLI, Claude Desktop) and shows the change first. See https://agentmart.dev/cli.

Get the weekly diff

The weekly diff: one email a week with new agent tools, notable updates and grade changes, plus security alerts for tools you follow. Double opt-in, one-click unsubscribe.

We use your email only for this newsletter. Privacy

About

Diagnose defects systematically by reproducing the issue, isolating the failing layer, testing hypotheses, fixing root cause, and adding regression protection.

Use cases: testing

No reviews yet. Installed it? Reviews come from verified installers only. How reviews work

Permissions

What this skill can do and what it asks for, from its SKILL.md. Checked Oct 25, 2026.

Tools
No tools found
Secrets
None asked for
Install scripts
None found

Network hosts it talks to 1

  • codeload.github.com · found in install command

Files it touches

  • ~/.claude/skills/debugging

What's inside

Skill name
debugging
Description
Diagnose defects systematically by reproducing the issue, isolating the failing layer, testing hypotheses, fixing root cause, and adding regression protection.
License
MIT
Instructions
20 lines in SKILL.md · view on GitHub

Files (1)

  • SKILL.md

SKILL.md (first lines)

# Debugging

## Workflow
1. Reproduce the failure with the smallest reliable case.
2. Capture exact symptoms: inputs, outputs, logs, status codes, stack traces, environment, timing, and recent changes.
3. Identify the failing layer: UI, client state, network, API, auth, domain logic, database, queue, external service, infrastructure.
4. Form a specific hypothesis and gather evidence before editing.
5. Compare against nearby working paths and historical behavior where useful.
6. Fix the root cause with the smallest coherent change.
7. Add a regression test when practical.
8. Re-run the original reproduction plus adjacent relevant tests.
9. Remove temporary instrumentation and review the final diff.

## Rules
- Do not shotgun-edit multiple unrelated areas.
- Do not swallow errors unless the product intentionally handles them.
- Do not treat symptoms with arbitrary delays/retries without understanding the cause.
- Record unresolved environmental or upstream causes explicitly.

From PHENOMVALENCE/engineering-agent-skills, MIT.

More from PHENOMVALENCE/engineering-agent-skills

Signals

Stars
0
Forks
0
Open issues
0
Last commit (this folder)
Sep 16, 2026 (1 month ago)

From GitHub (fetched Oct 24, 2026).

Details

License
MIT
First seen
Oct 24, 2026
Last checked
Oct 24, 2026

More from PHENOMVALENCE

Cite this page

debugging skill. Agent Mart. https://agentmart.dev/skills/phenomvalence-debugging (last updated 2026-10-24)