Menu
Prepares branches and PRs for clean, reviewable merges.
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
Flags risky shell commands and unsafe tree ops.
Detects high-confidence security risks in code.
Surfaces the dojo's non-negotiable prime directives.
Activates the dojo framework at the start of a session.
Plans multi-step work before writing code.
Captures lessons and promotes recurring patterns.
| name | pr-workflow |
| description | Prepares branches and PRs for clean, reviewable merges. |
| tier | practical |
| category | workflow |
| created_by | human |
| platforms | ["windows","macos","linux"] |
| tags | ["git","pr","review"] |
| author | Andreas Wasita (@andreaswasita) |
Takes a working branch from "the code works" to "this is ready for a human reviewer": pre-flight checks, clean commits, a real description, self-review, and disciplined handling of feedback. Does NOT create draft "WIP" PRs that sit open for days.
git configured with author identity.gh CLI authenticated for PR creation (or web access to the host).powershell tool to run git, the test suite, and scripts/verify.sh.1. Pre-flight: tests green, working tree clean, scope reviewed.
2. Clean up commits with interactive rebase if needed.
3. Push the branch.
4. Open the PR with a structured description.
5. Self-review the diff (use the `code-review` skill).
6. Address feedback in new commits — do not force-push during active review.
| Step | Command (run via powershell) | Notes |
|---|---|---|
| Pre-flight tests | npm test / pytest / go test ./... | Must exit 0 |
| Dojo gate | bash scripts/verify.sh --check | Must exit 0 |
| Clean tree | git status --porcelain | Empty |
| Review scope | git diff main --stat | Matches plan |
| Tidy history | git rebase -i main | Optional, before push |
| Push | git push -u origin <branch> | First push of branch |
| Open PR | gh pr create --fill then edit body | Or use the GitHub UI |
Run via the powershell tool:
bash scripts/verify.sh --check
git status --porcelain
git diff main --stat
If anything fails, fix it before proceeding. A PR opened on a red branch wastes reviewer time.
Interactive rebase if the history is noisy:
git rebase -i main
Squash fixups. Reword unclear messages. Aim for a sequence that reads like a story:
feat: add rate limiting middleware
test: cover rate limit burst traffic
docs: document rate limit configuration
Commit message format:
<type>: <short description>
<body — what and why, not how>
Types: feat, fix, refactor, test, docs, chore
## What
<Brief description.>
## Why
<Problem solved. Link the issue.>
## How
<High-level approach. Key design decisions.>
## Testing
<How was this tested? What should the reviewer verify?>
## Checklist
- [ ] Tests pass
- [ ] No regressions
- [ ] Docs updated (if applicable)
- [ ] `tasks/todo.md` reflects completion
Before requesting a human reviewer:
code-review skill on your own change.console.log, print(), TODO, commented-out code.receiving-code-review skill).scripts/verify.sh --check exits 0 locally before push.wip, no fix stuff).code-review skill before requesting human review.