carterdea/prove-it-bug-fix
agents/skills/prove-it-bug-fix/SKILL.md
Reproduce bugs with a failing test before fixing
$ install --global
skillsauthnpx skillsauth add carterdea/dots prove-it-bug-fixInstall 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 27, 2026, 6:02 AM59.3s1 file scanned
SKILL.md
- name:
- prove-it-bug-fix
- description:
- Reproduce bugs with a failing test before fixing
- allowed-tools:
- Task, Bash, Read, Write, Edit, Grep, Glob
- user-invocable:
- false
Prove It Bug Fix
When given a bug or error report, reproduce it with a failing test before attempting a fix.
When to use
- User reports a bug, error, or unexpected behavior
- Stack trace or error message is provided
- Something "doesn't work" or "broke"
Test Level Hierarchy
Reproduce at the lowest level that can capture the bug:
- Unit test - Pure logic bugs, isolated functions (lives next to the code)
- Integration test - Component interactions, API boundaries (lives next to the code)
- E2E/UX spec test - Full user flows, browser-dependent behavior (follow project conventions)
Steps
-
Reproduce with subagent
- Spawn a subagent (Task tool) to write a test that demonstrates the bug
- The test MUST fail before any fix is attempted
- If the test passes, the bug isn't properly reproduced—refine the test
-
Fix
- Only after reproduction is confirmed, implement the fix
- Keep the fix minimal and focused
-
Confirm
- Run the test again—it must now pass
- This proves the fix works
Subagent Prompt Template
Write a test that reproduces this bug:
{bug_description}
Requirements:
- Choose the appropriate test level (unit/integration/e2e)
- The test MUST fail currently to prove the bug exists
- Name the test descriptively (e.g., `test_cart_total_excludes_deleted_items`)
- Place the test following project conventions
Run the test and confirm it fails before reporting back.
If Reproduction Isn't Feasible
Some bugs are environment-specific or transient. If a test truly can't capture the bug:
- Document why (e.g., "Race condition only occurs under load")
- Add logging or assertions that would catch it if it recurs
- Note this in the commit message
Never skip reproduction silently.
Related Skills
carterdea/vertical-feature-architect
development
VerifiedTrustedCommunity
Add net-new product, workflow, platform, or developer-experience features as small vertical slices. Use this skill whenever the user asks to build a new feature, add a new page/route/API/workflow/job/eval/operator path, enrich an existing feature with a new user-visible capability, or plan feature architecture before coding. This skill maps the files to change or create, defines the authoritative contract, specifies tests, and gives a QA plan before treating the feature as done.
1SKILL.mdUpdated Jun 12, 2026
carterdea/trello-qa
development
VerifiedTrustedCommunity
Verify a developer's finished Trello ticket on a non-Shopify web app and render a verdict. Dogfood the posted preview (desktop + mobile) against the card's acceptance criteria, then PASS it (approve the PR, move to Ready for Release) or FAIL it (request changes, attach repro, reassign the dev, move to Development). Read-only: never implements, commits, or opens a PR. Use when asked to 'QA this card', 'test before release', or 'sign off on this ticket'. Shopify themes use shopify-trello-qa; building a ticket uses trello-delivery.
1SKILL.mdUpdated Jun 12, 2026
carterdea/shopify-trello-qa
development
VerifiedTrustedCommunity
Verify a developer's finished Shopify theme ticket and render a verdict. Dogfood the posted preview theme and Customizer (desktop + mobile) against the card's acceptance criteria and Figma, then PASS it (approve the PR, move to Ready for Release) or FAIL it (request changes, attach repro, reassign the dev, move to Development). Read-only: never implements, commits, deploys, or opens a PR. Use when asked to 'QA this Shopify card', 'verify the Ready for Testing card', or 'sign off on this theme ticket'. Non-Shopify apps use trello-qa; building a ticket uses shopify-trello-delivery.
1SKILL.mdUpdated Jun 12, 2026
carterdea/improve
development
VerifiedTrustedCommunity
Survey any codebase as a senior advisor and produce prioritized, self-contained implementation plans for OTHER models/agents to execute. Strictly read-only on source code — never implements, fixes, or refactors anything itself. Use when asked to audit a codebase, find improvement opportunities (bugs, security, performance, test coverage, tech debt, migrations, DX), suggest features or where to take the project next (roadmap, product direction), or generate handoff plans for another agent to implement.
1SKILL.mdUpdated Jun 12, 2026