stevenmburns/fix-issue
skills/fix-issue/SKILL.md
Read a GitHub issue, implement a fix, and open a PR that references the issue
tools
Updated Apr 20, 2026
$ install --global
skillsauthnpx skillsauth add stevenmburns/dot-claude-files fix-issueInstall 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 20, 2026, 4:34 AM26.2s1 file scanned
SKILL.md
- name:
- fix-issue
- description:
- Read a GitHub issue, implement a fix, and open a PR that references the issue
- user-invocable:
- true
- allowed-tools:
- Bash, Glob, Grep, Read, Write, Edit
Fix Issue
Read a GitHub issue, implement a fix, and open a PR that references the issue.
Usage
/fix-issue <issue-number>
Steps
- Read the issue with
gh issue view <number> --json title,body,commentsto understand the bug - Explore the codebase to locate the relevant code — read files, search for patterns mentioned in the issue
- Create a feature branch named descriptively (e.g.
fix/<short-description>) - Write a failing test that reproduces the bug — run it to confirm it fails before making any fix
- The test must fail because of the behavior described in the issue, not due to a technical problem (missing file, unresolvable import, missing module, etc.)
- If the test fails for a technical reason, fix that problem first so the test fails for the right reason before continuing
- Implement the fix — edit only what is necessary to fix the bug; do not refactor or clean up surrounding code
- Run tests to confirm the new test passes and nothing else is broken — check the project's CLAUDE.md or pyproject.toml/package.json for the test command; if tests fail, fix them before continuing
- Stage and commit the changed files with a descriptive conventional commit message; include
Closes #<number>in the commit body - Push the branch with
-uflag - Create a PR with
gh pr create:- Title: concise description of the fix (under 70 chars)
- Body must include
Fixes #<number>so GitHub auto-closes the issue on merge; summarize root cause and changes
- Report the PR URL to the user
Related Skills
stevenmburns/triage-issues
tools
VerifiedTrustedCommunity
Scan open GitHub issues, flag duplicates, and summarize with suggested priorities
SKILL.mdUpdated Apr 20, 2026
stevenmburns/tidy-branch
testing
VerifiedTrustedCommunity
Interactively clean up the current branch's commits (squash fixups, reword sloppy messages, reorder, drop) before merging — especially important on repos using rebase-merge where every branch commit lands on main verbatim
SKILL.mdUpdated Apr 20, 2026
stevenmburns/rename-pr
tools
VerifiedTrustedCommunity
Analyze the changes in the current PR and suggest a more accurate title if the current one no longer fits
SKILL.mdUpdated Apr 20, 2026
stevenmburns/merge-pr
data-ai
VerifiedTrustedCommunity
Merge the open PR for the current branch into main, delete the branch, and pull main
SKILL.mdUpdated Apr 20, 2026