메뉴
Open or update a draft PR for the current branch. Use when: create PR, open PR, draft PR, pull request, prepare for review.
Codex 또는 Claude로 설치 이 Prompt를 복사해 Codex, Claude 또는 다른 어시스턴트에 붙여 넣으면 Skill 페이지를 검토하고 설치를 진행할 수 있습니다.
SOC 직업 분류 기준
Bug hunter. Reproduces bugs with failing tests (RED), then fixes with TDD. Accepts a prompt, issue URL, or bug description. Use when: bugfix, fix bug, debug, broken, regression, failing, doesn't work, fix this.
Interactive pair review of a PR. Fetches the diff, scouts for context, then walks through each changed file one at a time. Collects review comments in a bag with conventional comment prefixes, previews them, and posts only after explicit approval. Trigger on: pair review, let's review together, walk me through the PR, review with me.
TDD pair programming with mode switching. Claude can be driver (writes code) or navigator (watches, questions, provokes). Supports GitHub issues, file watching, or arbitrary prompts. Scientific TDD, baby steps, one test at a time. Trigger on: pair, let's pair, tdd, you drive, I'll drive, dojo.
Orchestrator - spawns an autonomous orchestrator agent that decomposes a task into subtasks and drives multiple Claude agents to completion. Use when: overmind, orchestrate, multi-agent, delegate, spawn agents, break down task, run agents.
Deep code review - Elixir idioms, OTP patterns, tech debt, safety. Launches 3 parallel reviewers + plan-reviewer gate. Use when: review, review this, code review, check this code, review my changes, is this good, what do you think, techdebt, tech debt, code smells.
Create a git commit following project conventions. Use when: commit, commit this, make a commit, commit changes, git commit, save changes, commit my work, stage and commit, detailed commit.
| name | pr |
| description | Open or update a draft PR for the current branch. Use when: create PR, open PR, draft PR, pull request, prepare for review. |
Creates or updates a draft pull request for the current branch.
/pr - Create draft PR for current branch (or update if one exists)/pr <url> - Update existing PR descriptionNEVER commit to main unless the user explicitly requests it.
git branch --show-current
git status
If on main, create and switch to a feature branch before doing anything else:
git checkout -b <type>/<short-name>
Branch naming follows the PR type prefix:
feat/ — new featuresfix/ — bug fixesrefactor/ — refactoringtest/ — test additionschore/ — maintenancedocs/ — documentationDerive the branch name from the commit history or changes (e.g., feat/spawn-and-observe).
After ensuring you're on a feature branch, check for uncommitted changes. If there are staged or unstaged changes, commit them using conventional commit format:
git add <relevant files>
git commit -m "<type>: <description>"
Only proceed to the next step once all changes are committed on a feature branch.
git log main..HEAD --oneline
git diff main...HEAD --stat
If the PR was created from a /tdd <issue> workflow, you already have the issue number in context. Otherwise, check the branch name or commit messages for issue references.
If an issue is identified, it will be linked in the PR body using a GitHub closing keyword (see template below). When the PR is merged, GitHub automatically closes the linked issue and marks it as "completed".
gh pr view --json number,title,body 2>/dev/null
Use the template below. Keep it concise and natural.
gh pr create --draft --title "<title>" --body "$(cat <<'EOF'
<body>
EOF
)"
gh pr edit --title "<title>" --body "$(cat <<'EOF'
<updated body>
EOF
)"
Report the PR URL to the user when done.
<type>: <short description>
Types: feat:, fix:, refactor:, test:, chore:, docs:
Rules:
Closes #<issue_number>
## Summary
1-2 paragraphs explaining what this does and why.
## Changes
- Highlight 1
- Highlight 2
- Highlight 3
## Testing
- [ ] `mix test` passes
- [ ] `mix dialyzer` passes
- [ ] `mix smoke` passes
Omit the Closes #... line if there is no source issue.
/tdd <issue_url> -> /review-pr -> /pr -> merge