pr-workflow

PR Workflow Skill

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.

When to Use

• Preparing a feature branch for review.
• Opening a pull request.
• Writing or rewriting a PR description.
• Restructuring commits before review.
• The user says "submit this" or "get this ready for review".

Prerequisites

• git configured with author identity.
• gh CLI authenticated for PR creation (or web access to the host).
• The powershell tool to run git, the test suite, and scripts/verify.sh.
• A green test suite on the branch.

How to Run

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.

Quick Reference

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

Procedure

Step 1: Pre-Flight

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.

Step 2: Clean Up Commits

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: