Menu
Create a pull request with proper title, description, and test plan
Installer avec Codex ou Claude Copiez ce prompt, collez-le dans Codex, Claude ou un autre assistant, puis laissez-le vérifier la page du skill et l'installer pour vous.
Basé sur la classification professionnelle SOC
Add a new implementation of the primary protocol/interface (Alex Rivera's workflow)
Add a new API endpoint following all project standards
Plan and implement a complete feature end-to-end across all layers
Full codebase audit — dead code, layer violations, concurrency, observability, code quality
Set up or update GitHub Actions CI/CD pipeline (Marcus Chen's workflow)
Remove dead code, unused imports, stale files, and fix code quality issues found by /audit
| name | pr |
| description | Create a pull request with proper title, description, and test plan |
| disable-model-invocation | true |
Create a pull request for the current branch: $ARGUMENTS
Run the test and type-check commands (see project config). Both MUST pass. Never create a PR with failing tests or type errors.
git log main..HEAD --oneline
git diff main...HEAD --stat
Understand the full scope of changes since branching from main.
Use this structure:
## Summary
- Bullet point 1: what changed and why
- (1-3 bullets max)
## Changes
- List every file modified/created/deleted with brief reason
## Test Plan
- [ ] All existing tests pass
- [ ] Type checking passes
- [ ] New tests added for: <list new test coverage>
- [ ] Manual verification: <steps>
## Checklist
- [ ] Future annotations pattern followed (see stack concepts)
- [ ] Typed exceptions (no generic `Exception`)
- [ ] Typed schemas for all request/response shapes (see stack concepts)
- [ ] OpenAPI metadata on all new endpoints
- [ ] Project documentation updated (if new endpoints/config)
- [ ] Env example file updated (if new settings)
git push -u origin <branch-name>
gh pr create --title "<title>" --body "<body>"
Output the PR URL so it can be reviewed.