imabusyman/prove-it-bugfix
prompts/squad/skills/prove-it-bugfix/SKILL.md
DevSquad-style bug-fix flow — reproduce, write a failing test, fix, verify. Use this whenever the squad task is "fix bug X" or the Planner flags a step as a bug repro.
development
Updated Apr 25, 2026
$ install --global
skillsauthnpx skillsauth add imabusyman/CodebrewRouter prove-it-bugfixInstall this skill globally with one command. Works with Claude Code, Cursor, and Windsurf.
Security Scan Results
3 of 9 scanners reported clean
Some scanners were skipped, did not run, or reported a non-clean status. Review each row below.
3
Scanners Passed
9
Scanners in report
Clean
TrivyContainer and dependency vulnerability scanner
95%
Clean
SemgrepStatic code analysis for vulnerabilities
95%
Clean
mcp-scan (Snyk)Model Context Protocol security validation
95%
Skipped
Snyk (dep)Open source security scanning
50%
Skipped
Socket.devSupply chain security analysis
50%
Skipped
VirusTotalMulti-engine malware detection
50%
Skipped
CrowdStrikeAdvanced threat intelligence
50%
Skipped
OSV-ScannerOpen Source Vulnerability database check
50%
Skipped
OWASP Dep-Check
50%
Last scanned: Apr 25, 2026, 7:20 PM127.8s1 file scanned
SKILL.md
- name:
- prove-it-bugfix
- description:
- DevSquad-style bug-fix flow — reproduce, write a failing test, fix, verify. Use this whenever the squad task is \"fix bug X\" or the Planner flags a step as a bug repro.
Prove-It — bug-fix flow
When the task is to fix a bug, the squad proves the bug before the fix, then proves the fix with the same test.
Flow
- Reproduce. Read the failing code path. Reconstruct the exact inputs that trigger the failure.
- Red. Tester writes the smallest possible failing test that captures the bug. Test MUST fail against the pre-fix baseline.
- Root cause. Coder identifies the compiler / runtime / logic reason the test fails.
- Green. Coder makes the minimal change that flips the test from red to green. No scope creep.
- Gate.
dotnet build --no-incremental -warnaserror dotnet test --no-build --collect:"XPlat Code Coverage" - Prove-It check. If the new test passes against BOTH the pre-fix and post-fix code, it's insufficient — tighten the assertion or narrow the inputs until it truly distinguishes the two states.
Roles in the flow
| Phase | Owner | Output |
|---|---|---|
| Reproduce | Planner | spec.md §"Current state" with the failing code path cited |
| Red | Tester | <Area>/<Class>Tests.cs with [Fact] that fails against baseline |
| Root cause | Coder | Log entry (MEDIUM): "Failure reason: <compiler | runtime | logic>" |
| Green | Coder | Minimal diff on the bug site |
| Gate | Coder (build) → Tester (test + coverage) | [CHECKPOINT] then [DONE] |
| Verify | Reviewer | Reread diff, confirm fix is minimal, no new CRITICAL/HIGH findings |
Anti-patterns (reject)
- Adding a test that asserts the fixed behavior but would have also passed against the bug. Not a proof.
- Expanding the fix to "while I'm here" scope. Every new file touched is a new envelope — route back to the Conductor.
- Silencing the compiler / test instead of fixing.
#nullable disableorAssert.True(true)in place of real assertions → CRITICAL.
Reporting
Prove-It runs append one reasoning-log entry per phase flip:
## <ts> — tester — HIGH
Decision: captured <bug-name> with assertion on <invariant>
Rationale: test fails against commit <sha> (pre-fix); passes against current HEAD
Evidence: Blaze.LlmGateway.Tests/<Area>/<Class>Tests.cs:<line>
Related Skills
imabusyman/write-a-prd
development
VerifiedTrustedCommunity
Generate a Product Requirements Document from a task description, user intent, or PRD outline. Structure the PRD with sections: Overview, Problem Statement, Goals, Scope, Features, Acceptance Criteria, Metrics. Use this when the Planner or Orchestrator needs to formalize requirements before decomposing into implementation steps.
SKILL.mdUpdated Apr 25, 2026
imabusyman/team-builder
development
VerifiedTrustedCommunity
Compose parallel teams of specialized agents for a multi-faceted task. Map subtasks to agent roles, balance workload, and validate team composition. Use this when breaking a task into parallel streams that require different expertise (Coder, Tester, Infra, etc.).
SKILL.mdUpdated Apr 25, 2026
imabusyman/subagent-driven-development
development
VerifiedTrustedCommunity
Delegate implementation work to specialized subagent instances, each inheriting a task scope and constraints from the parent. Emit structured handoffs, monitor completion signals, aggregate results. Use this in the Orchestrator parallel path when spawning independent Coder/Tester/Infra subagents from a single coordinator.
SKILL.mdUpdated Apr 25, 2026
imabusyman/reasoning
testing
VerifiedTrustedCommunity
Maintain the append-only reasoning log and write handoff envelopes for every squad delegation. Use this when the Conductor delegates to a specialist or when a specialist records a non-trivial decision.
SKILL.mdUpdated Apr 25, 2026