Prompt file imported from valbeat/dotfiles (.codex/prompts/fix-issue.md). Copyright stays with the author.

Fix GitHub Issue

Name: fix-issue
Author: valbeat

Context

Current repository: !gh repo view --json nameWithOwner -q .nameWithOwner 2>/dev/null || echo "Not a GitHub repository"
Current branch: !git branch --show-current
Project standards: @.claude/CLAUDE.md
TDD approach: Follow t-wada's TDD methodology when applicable

Your task

Analyze and fix a GitHub issue by its issue number. Understand the problem, implement a solution following project standards, and ensure proper testing.

Usage

Fix issue #<issue-number>

Steps

View the issue details

gh issue view <issue-number>
gh issue view <issue-number> --comments  # Include comments for more context

Create a feature branch

git checkout -b fix/issue-<issue-number>
# Or for features: git checkout -b feat/issue-<issue-number>

Analyze the problem
- Read issue description and acceptance criteria
- Check linked issues or PRs
- Review any provided error messages or logs
- Understand the expected vs actual behavior
Search the codebase
- Use grep/glob to find relevant files
- Look for error messages mentioned in the issue
- Find related tests and documentation
Implement the fix
- Follow TDD principles if requested
- Make minimal changes to fix the issue
- Follow existing code conventions
- Add comments only if explicitly needed

Run quality checks

# Format code
npm run format || cargo fmt

# Run linter
npm run lint || cargo clippy

# Type check
npm run typecheck || cargo check

# Run tests
npm test || cargo test

Create commit

git add .
git commit -m "fix: <description> (#<issue-number>)"
# Example: git commit -m "fix: handle null response in API client (#123)"

Push and create PR

git push -u origin fix/issue-<issue-number>
gh pr create --title "fix: <description>" --body "Fixes #<issue-number>" --assignee @me

Commit Message Format

Use fix: prefix for bug fixes
Use feat: prefix for new features
Reference the issue: (#123) or in body: Fixes #123
Keep subject line under 50 characters

Notes

Always link the PR to the issue using "Fixes #123" in the PR body
The issue will automatically close when the PR is merged
If the issue is in a different repo, use full reference: "Fixes owner/repo#123"
Run all checks locally before pushing to avoid CI failures

# Fix GitHub Issue ## Context - Current repository: !`gh repo view --json nameWithOwner -q .nameWithOwner 2>/dev/null || echo "Not a GitHub repository"` - Current branch: !`git branch --show-current` - Project standards: @.claude/CLAUDE.md - TDD approach: Follow t-wada's TDD methodology when applicable ## Your task Analyze and fix a GitHub issue by its issue number. Understand the problem, implement a solution following project standards, and ensure proper testing. ## Usage ``` Fix issue #<issue-number> ``` ## Steps 1. **View the issue details** ```bash gh issue view <issue-number> gh issue view <issue-number> --comments # Include comments for more context ``` 2. **Create a feature branch** ```bash git checkout -b fix/issue-<issue-number> # Or for features: git checkout -b feat/issue-<issue-number> ``` 3. **Analyze the problem** - Read issue description and acceptance criteria - Check linked issues or PRs - Review any provided error messages or logs - Understand the expected vs actual behavior 4. **Search the codebase** - Use grep/glob to find relevant files - Look for error messages mentioned in the issue - Find related tests and documentation 5. **Implement the fix** - Follow TDD principles if requested - Make minimal changes to fix the issue - Follow existing code conventions - Add comments only if explicitly needed 6. **Run quality checks** ```bash # Format code npm run format || cargo fmt # Run linter npm run lint || cargo clippy # Type check npm run typecheck || cargo check # Run tests npm test || cargo test ``` 7. **Create commit** ```bash git add . git commit -m "fix: <description> (#<issue-number>)" # Example: git commit -m "fix: handle null response in API client (#123)" ``` 8. **Push and create PR** ```bash git push -u origin fix/issue-<issue-number> gh pr create --title "fix: <description>" --body "Fixes #<issue-number>" --assignee @me ``` ## Commit Message Format - Use `fix:` prefix for bug fixes - Use `feat:` prefix for new features - Reference the issue: `(#123)` or in body: `Fixes #123` - Keep subject line under 50 characters ## Notes - Always link the PR to the issue using "Fixes #123" in the PR body - The issue will automatically close when the PR is merged - If the issue is in a different repo, use full reference: "Fixes owner/repo#123" - Run all checks locally before pushing to avoid CI failures

{ "prompt": "# Fix GitHub Issue\n\n## Context\n\n- Current repository: !`gh repo view --json nameWithOwner -q .nameWithOwner 2>/dev/null || echo \"Not a GitHub repository\"`\n- Current branch: !`git branch --show-current`\n- Project standards: @.claude/CLAUDE.md\n- TDD approach: Follow t-wada's TDD methodology when applicable\n\n## Your task\n\nAnalyze and fix a GitHub issue by its issue number. Understand the problem, implement a solution following project standards, and ensure proper testing.\n\n## Usage\n```\nFix issue #<issue-number>\n```\n\n## Steps\n\n1. **View the issue details**\n ```bash\n gh issue view <issue-number>\n gh issue view <issue-number> --comments # Include comments for more context\n ```\n\n2. **Create a feature branch**\n ```bash\n git checkout -b fix/issue-<issue-number>\n # Or for features: git checkout -b feat/issue-<issue-number>\n ```\n\n3. **Analyze the problem**\n - Read issue description and acceptance criteria\n - Check linked issues or PRs\n - Review any provided error messages or logs\n - Understand the expected vs actual behavior\n\n4. **Search the codebase**\n - Use grep/glob to find relevant files\n - Look for error messages mentioned in the issue\n - Find related tests and documentation\n\n5. **Implement the fix**\n - Follow TDD principles if requested\n - Make minimal changes to fix the issue\n - Follow existing code conventions\n - Add comments only if explicitly needed\n\n6. **Run quality checks**\n ```bash\n # Format code\n npm run format || cargo fmt\n \n # Run linter\n npm run lint || cargo clippy\n \n # Type check\n npm run typecheck || cargo check\n \n # Run tests\n npm test || cargo test\n ```\n\n7. **Create commit**\n ```bash\n git add .\n git commit -m \"fix: <description> (#<issue-number>)\"\n # Example: git commit -m \"fix: handle null response in API client (#123)\"\n ```\n\n8. **Push and create PR**\n ```bash\n git push -u origin fix/issue-<issue-number>\n gh pr create --title \"fix: <description>\" --body \"Fixes #<issue-number>\" --assignee @me\n ```\n\n## Commit Message Format\n- Use `fix:` prefix for bug fixes\n- Use `feat:` prefix for new features\n- Reference the issue: `(#123)` or in body: `Fixes #123`\n- Keep subject line under 50 characters\n\n## Notes\n- Always link the PR to the issue using \"Fixes #123\" in the PR body\n- The issue will automatically close when the PR is merged\n- If the issue is in a different repo, use full reference: \"Fixes owner/repo#123\"\n- Run all checks locally before pushing to avoid CI failures", "variables": [], "notes": "Analyze and fix a GitHub issue by its issue number Tools: Read, Write, Edit, Bash(gh:*), Bash(git:*), Glob, Grep.", "metadata": { "source": { "provider": "github-codex-prompts", "repository": "https://github.com/valbeat/dotfiles", "path": ".codex/prompts/fix-issue.md", "ref": "c70adeecaf7dc5b4a324e1a6ee96c904b9bbdec5", "url": "https://github.com/valbeat/dotfiles/blob/c70adeecaf7dc5b4a324e1a6ee96c904b9bbdec5/.codex/prompts/fix-issue.md", "key": "valbeat/dotfiles/.codex/prompts/fix-issue.md" } } }

fix-issue

About

Fix GitHub Issue

Context

Your task

Usage

Steps

Commit Message Format

Notes

Use it

Manifest

Reviews