Fix issue

GitHub sorununu numarasına göre düzeltin: sorunu okuyun, bir şube oluşturun, düzeltmeyi uygulayın ve bir PR açın.

yazan kuscubasiece·8 Eylül 2026

Kaynak: rohitg00/awesome-claude-code-toolkit · Apache-2.0

Kurulum

mkdir -p .claude/commands && curl -sL https://www.antrophiclove.com/api/kaynak/fix-issue-cc-toolkit/raw -o .claude/commands/fix-issue-cc-toolkit.md

Hedef dosya: .claude/commands/fix-issue-cc-toolkit.md

Önizleme Ham metin ⑂ Kendi sürümünü oluştur

Fix a GitHub issue by number: read the issue, create a branch, implement the fix, and open a PR.

Steps

Fetch the issue details using gh issue view <number> --json title,body,labels,assignees.
Parse the issue body to understand the problem, expected behavior, and reproduction steps.
Create a feature branch: git checkout -b fix/<number>-<slug> where slug is derived from the title.
Analyze the codebase to locate relevant files mentioned in or related to the issue.
Implement the fix:
- Make minimal, focused changes that address only the reported problem.
- Add or update tests that cover the fixed behavior.
Run the project test suite to verify the fix does not introduce regressions.
Commit changes with fix: <title> (closes #<number>).
Push the branch and create a PR: gh pr create --title "Fix #<number>: <title>" --body "Closes #<number>".

Format

Issue #<number>: <title>
Status: <Open/Closed>
Labels: <label1>, <label2>

Analysis:
- Root cause: <description>
- Files affected: <list>

Changes made:
- <file>: <what changed>

Tests: <pass/fail summary>
PR: <url>

Rules

Always read the full issue including comments before starting.
Never modify files unrelated to the issue.
If the issue is unclear or lacks reproduction steps, ask for clarification before proceeding.
Reference the issue number in commit messages and PR description.