packbot/fix-bug
.claude/skills/fix-bug/SKILL.md
Fix a bug following the Reproduce > Diagnose > Fix > Verify workflow. Use when something is broken, there's an error, or the user reports unexpected behavior.
testing
Updated Apr 16, 2026
$ install --global
skillsauthnpx skillsauth add packbot/agentic-coding-boilerplate fix-bugInstall 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 16, 2026, 9:05 PM4.5s1 file scanned
SKILL.md
- name:
- fix-bug
- description:
- Fix a bug following the Reproduce > Diagnose > Fix > Verify workflow. Use when something is broken, there's an error, or the user reports unexpected behavior.
- disable-model-invocation:
- true
Fix Bug: $ARGUMENTS
Follow this structured workflow. Do not skip phases.
Phase 1: Reproduce
- Read the bug description: $ARGUMENTS
- Find the relevant code by searching for related functions, error messages, or file paths
- Understand the expected behavior vs. actual behavior
- Identify a way to reproduce the issue (test case or manual steps)
- Write a failing test that demonstrates the bug
Phase 2: Diagnose
- Trace the code path that leads to the bug
- Identify the root cause — not just the symptom
- Check if this bug exists in other similar code paths
- Understand why the original code was written this way before changing it
Phase 3: Fix
- Make the minimal change that fixes the root cause
- Do NOT refactor surrounding code unless it's directly related to the bug
- Ensure the failing test from Phase 1 now passes
- Add additional edge case tests if the bug reveals gaps in test coverage
Phase 4: Verify
- [ ] The originally failing test now passes
- [ ] All existing tests still pass:
{{TEST_COMMAND}} - [ ] Linting passes:
{{LINT_COMMAND}} - [ ] Build succeeds:
{{BUILD_COMMAND}} - [ ] No regressions in related functionality
- [ ] The fix addresses the root cause, not just the symptom
Phase 5: Document
- Add a brief comment explaining the fix if the logic isn't self-evident
- If the bug came from a common pattern, note what to watch for in similar code
Related Skills
packbot/write-tests
development
VerifiedTrustedCommunity
Write comprehensive tests following the Analyze > Strategy > Implement > Verify workflow. Use when adding tests, improving coverage, or when the user asks to write tests for specific code.
SKILL.mdUpdated Apr 16, 2026
packbot/.claude/skills/review-code
development
VerifiedTrustedCommunity
Review code changes or a GitHub PR
SKILL.mdUpdated Apr 16, 2026
packbot/refactor
development
VerifiedTrustedCommunity
Refactor code safely following the Analyze > Plan > Refactor > Verify workflow. The key rule is that behavior must not change. Use when improving code structure, readability, or modularity.
SKILL.mdUpdated Apr 16, 2026
packbot/push
tools
VerifiedTrustedCommunity
Push commits to remote and optionally create a PR. Use when the user wants to push their changes.
SKILL.mdUpdated Apr 16, 2026