Open or update a draft PR for the current branch. Use when: create PR, open PR, draft PR, pull request, prepare for review.
Open or update a draft PR for the current branch. Use when: create PR, open PR, draft PR, pull request, prepare for review.
npx skills add https://github.com/leandronsp/aspirina --skill prこのコマンドをClaude Codeにコピー＆ペーストしてスキルをインストール
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.
Implementer - fetches a GitHub issue, builds an implementation plan, then implements using TDD. Use when: implement, build this, code this, add this feature, TDD, test first, red green refactor, pick a task, next task, dev.
Product Owner - scans codebase and creates or amends GitHub issues with PRD. Use when: PRD, feature, issue, create issue, amend issue, what should we build, plan feature, design feature, scope, requirements.
Deep code review - Rust idioms, ownership, safety, tech debt. 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.
| 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/ — documentationAfter 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 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 /dev <issue> workflow, you already have the issue number in context. Otherwise, check the branch name or commit messages for issue references.
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
- [ ] `cargo test` passes
- [ ] `cargo clippy` clean
- [ ] `cargo fmt --check` clean
Omit the Closes #... line if there is no source issue.
/dev <issue> -> /review -> /commit -> /pr -> merge