tdd-bug-report
From the author
Workflow for analyzing bug reports, tracing root causes, and generating structured bug-fix implementation plans enforcing the Prove-It pattern (failing regression test first) with rollback strategies.
Install
npx skills add GulajavaMinistudio/awesome-copilot-id --skill tdd-bug-report -a claude-code
Installs to .claude/skills/tdd-bug-report/ · Each command fetches the skill straight from GitHub with the open skills CLI.
Byte-identical to the scanned commit, with the repository’s licence and a SOURCE.txt.
Want your agent to suggest skills while you type? See how to use skills from your IDE.
Safety checks on SKILL.md
No warnings.
Why 83
aiqbench computes the trust score from public signals. It is not a security audit, so read a skill before you install it.
Similar skills
Closest to this one by what they do and when they are used.
- sdlc-bug-reportGulajavaMinistudio/awesome-copilot-idWorkflow for analyzing bug reports, tracing root causes, and generating structured bug-fix implementation plans with rollback strategies.Planning★ 86
- nw-bugfixnWave-ai/nWaveBug fix workflow: root cause analysis → user review → regression test + fix via TDDTesting★ 622
- ca-fixarbiterForge/codeArbiterFix a confirmed bug: a failing regression test first, then a minimal fix, then the rest of the tdd gates.Testing★ 148
- tdd-workflowhashgraph-online/awesome-codex-pluginsUse this skill when writing new features, fixing bugs, or refactoring code. Enforces test-driven development with 80%+ coverage including unit, integration, and E2E tests.Testing★ 1.4K
- tdd-guideforyourhealth111-pixel/Vibe-SkillsTest-first development route for TDD, writing failing tests first, RED -> GREEN -> REFACTOR, and behavior-changing feature/bug/refactor work. Do not use for already-failing test root-cause debugging, test-report packaging, or final completion evidence.Testing★ 3.8K
- root-cause-debuggingthiientv/godmodeInvestigates a bug, failing test, build error, regression, flaky behavior, performance symptom, or unexpected result by reproducing it, minimizing the case, testing ranked hypotheses, tracing the first incorrect state, and locking the root cause with a regression check. Use before proposing a fix. Not for planning a new feature or reviewing a healthy diff.Engineering★ 99
Ratings & reviews
—
no reviews
Tried this skill? Rate it to help others. Sign in
Discussion
Join the discussion. Sign in