القائمة
Use when asked to take a GitHub issue number, implement a fix, run builds/tests, commit with a closing message, and push. End-to-end workflow using gh CLI, local code changes, and git.
التثبيت باستخدام Codex أو Claude انسخ هذا Prompt والصقه في Codex أو Claude أو مساعد آخر ليراجع صفحة Skill ويثبّتها لك.
استنادا إلى تصنيف SOC المهني
Consult a stronger model mid-task for a second opinion before committing to an approach, when stuck, or before declaring a non-trivial task done — the fast-executor + strong-advisor pattern, implemented with the Agent and Workflow tools (Claude Code does not expose Anthropic's raw API advisor tool). Use when running on a cheaper/faster model for mechanical work and a hard design/architecture/risk decision needs a stronger check, or when authoring a Workflow script that should get expert review partway through instead of only at the end.
Use when the user says "caveman mode", "talk like caveman", "use caveman", "less tokens", or "be brief", invokes /caveman, or when token efficiency is requested. Switches responses to an ultra-compressed terse style (multiple intensity levels available, ~75% token reduction) while preserving full technical accuracy.
Use right after being corrected on something a CLAUDE.md file should already have told you, when explicitly asked to review CLAUDE.md, or periodically after a session with a lot of back-and-forth — reviews THIS conversation for friction and proposes a bounded CLAUDE.md edit. A lightweight, single-session complement to skill-tuning-loop (which mines many sessions and validates a proposal against held-out cases before surfacing it — reach for that instead when the ask is "make this systematic," not "check right now"). Own version of the dx plugin's `/dx:review-claudemd`.
Generate a solution, evaluate it against explicit pass/fail criteria, refine using the feedback, repeat until it passes or a round cap is hit. Use for tasks with a clear, checkable bar and demonstrable value from iteration — a bug fix that must pass a test suite, code that must satisfy a lint/style rubric, a document that must meet stated requirements. Distinct from advisor-checkpoint (one strategic consult before committing) — this is a convergence loop against a concrete standard.
Use when PR checks fail, CI is red, or GitHub Actions workflows break - systematically inspects failing checks via gh CLI, pulls logs, checks for flakiness and scopes the breaking commit, scopes external checks, then creates fix plan using existing plan skill
Write a structured handoff document before a session ends, before a context-heavy interruption (SSH/tmux disconnect, context running low, a worktree being handed to another worker or agent), or when explicitly asked for a handoff — captures progress, what worked/failed, and the exact next step so a fresh session can resume without re-deriving context. Own version of the dx plugin's `/dx:handoff`.
| name | github-issue-fix-flow |
| description | Use when asked to take a GitHub issue number, implement a fix, run builds/tests, commit with a closing message, and push. End-to-end workflow using gh CLI, local code changes, and git. |
Resolve a GitHub issue from intake through fix, validation, and push using gh CLI, local edits, and git.
Get full issue context:
gh issue view <id> --comments
If repo is unclear:
gh repo view --json nameWithOwner
Capture from the issue:
Search for relevant code:
# Find files related to the issue
rg -n "keyword from issue"
# Find function definitions
rg -n "func relevantFunction"
# Find type definitions
rg -n "struct|class|enum RelevantType"
Read relevant code paths and understand:
Guidelines:
For Swift/Xcode projects:
# Build
swift build
# or
xcodebuild -scheme MyApp -destination 'platform=macOS' build
# Test
swift test
# or
xcodebuild -scheme MyAppTests -destination 'platform=macOS' test
For other projects, use appropriate build/test commands.
Report warnings or failures - do not hide them.
Check for unrelated changes:
git status --short
git diff
Stage only the fix:
git add <specific files>
Commit with closing message:
git commit -m "Fix: <description>
Closes #<issue number>"
Push:
git push
Provide summary:
| Task | Command |
|---|---|
| View issue | gh issue view <id> --comments |
| List issues | gh issue list |
| View repo | gh repo view --json nameWithOwner |
| Create branch | git checkout -b fix/issue-<id> |
| Stage files | git add <files> |
| Commit | git commit -m "Fix: ... Closes #<id>" |
| Push | git push -u origin HEAD |
| Create PR | gh pr create --fill |
Fix: Brief description of the fix
More detailed explanation if needed.
- What was the problem
- How it was fixed
- Any notable changes
Closes #123
# Feature
git checkout -b feature/issue-123-add-feature
# Bug fix
git checkout -b fix/issue-123-fix-bug
# Refactor
git checkout -b refactor/issue-123-cleanup
If working on a branch for PR:
# Create branch
git checkout -b fix/issue-<id>
# Make changes, commit
git add .
git commit -m "Fix: description (closes #<id>)"
# Push and create PR
git push -u origin HEAD
gh pr create --fill
Closes #<id>