
Fix Issue
- 1 installs
- 13 repo stars
- Updated June 3, 2026
- aws-samples/sample-finops-agent
fix-issue is a skill that implements a GitHub issue by exploring the codebase, planning, coding, and creating a pull request.
About
Turns a Claude agent into an autonomous engineer that implements a single GitHub issue. It reads project docs, explores the codebase, writes an implementation plan, makes focused changes following existing conventions, runs linters or tests, and opens a pull request referencing the issue. A developer invokes it with an issue number, title, and body to get a scoped PR back.
- Four-phase flow: understand codebase, plan, implement, verify and commit
- Keeps changes focused and minimal, only what the issue needs
- Opens a PR with a description of what changed and why, referencing the issue
Fix Issue by the numbers
- 1 all-time installs (skills.sh)
- Ranked #524 of 733 Git & Pull Requests skills by installs in the Skillselion catalog
- Data as of Aug 5, 2026 (Skillselion catalog sync)
fix-issue capabilities & compatibility
- Capabilities
- terraform skill
- Works with
- github
- Use cases
- refactoring · code review · project management
- Pricing
- Free
What fix-issue says it does
Implement a GitHub issue by exploring the codebase, planning, and creating a PR
Keep changes focused and minimal — only what's needed for the issue
npx skills add https://github.com/aws-samples/sample-finops-agent --skill fix-issueAdd your badge
Show developers this skill is listed on Skillselion. Paste this into your README.
| Installs | 1 |
|---|---|
| repo stars | ★ 13 |
| Last updated | June 3, 2026 |
| Repository | aws-samples/sample-finops-agent ↗ |
What it does
Autonomously implement a GitHub issue by exploring the codebase, planning, coding, and opening a pull request.
Who is it for?
Developers wanting an agent to take a GitHub issue and return a focused, PR-ready implementation
Skip if: Ambiguous or exploratory work not scoped to a single GitHub issue
When should I use this skill?
You have a defined GitHub issue and want it implemented and turned into a pull request
What you get
A focused commit and pull request that implements the issue and references it.
- Implementation plan
- Focused code commit
- Pull request referencing the issue
By the numbers
- 4-phase workflow
Files
You are an autonomous software engineer working on a GitHub issue.
Issue Details
$ARGUMENTS
Workflow
Phase 1: Understand the Codebase
- Read CLAUDE.md and any project documentation
- Explore the directory structure and key files
- Understand existing patterns, conventions, and architecture
- Identify the files and modules relevant to this issue
Phase 2: Plan the Implementation
- Design your approach based on what you learned about the codebase
- Consider edge cases and potential impacts on existing functionality
- Identify all files that need to be created or modified
- Write out your plan before making any changes
Phase 3: Implement
- Make the changes following existing code patterns and conventions
- Write clean, well-structured code consistent with the project style
- Include tests if the project has a test suite
- Keep changes focused and minimal — only what's needed for the issue
Phase 4: Verify & Commit
- Review your changes for correctness
- Run any available linters or tests
- Commit with a clear message referencing the issue
- Create a PR with a description of what was changed and why
Related skills
FAQ
What input does it take?
An issue number, issue title, and issue body passed as arguments.
How large are the changes it makes?
It keeps changes focused and minimal, only what is needed for the issue.