Miguel Palhas
39 lines
1.5 KiB
Markdown
39 lines
1.5 KiB
Markdown
---
|
|
description: Analyze and fix a GitHub issue end-to-end (plan, branch, implement, test, PR)
|
|
model: claude-sonnet-4-0
|
|
---
|
|
|
|
Please analyze and fix the GitHub issue: $ARGUMENTS.
|
|
|
|
Follow these steps:
|
|
|
|
# PLAN
|
|
1. Use 'gh issue view' to get the issue details (or open the issue in the browser/API explorer if the GitHub CLI is unavailable)
|
|
2. Understand the problem described in the issue
|
|
3. Ask clarifying questions if necessary
|
|
4. Understand the prior art for this issue
|
|
- Search the scratchpads for previous thoughts related to the issue
|
|
- Search PRs to see if you can find history on this issue
|
|
- Search the codebase for relevant files
|
|
5. Think harder about how to break the issue down into a series of small, manageable tasks.
|
|
6. Document your plan in a new scratchpad
|
|
- include the issue name in the filename
|
|
- include a link to the issue in the scratchpad.
|
|
|
|
# CREATE
|
|
- Create a new branch for the issue
|
|
- Solve the issue in small, manageable steps, according to your plan.
|
|
- Commit your changes after each step.
|
|
|
|
# TEST
|
|
- Use playwright via MCP to test the changes if you have made changes to the UI
|
|
- Write tests to describe the expected behavior of your code
|
|
- Run the full test suite to ensure you haven't broken anything
|
|
- If the tests are failing, fix them
|
|
- Ensure that all tests are passing before moving on to the next step
|
|
|
|
# DEPLOY
|
|
- Open a PR and request a review.
|
|
|
|
Prefer the GitHub CLI (`gh`) for GitHub-related tasks, but fall back to subagents or the GitHub web UI/REST API when the CLI is not installed.
|