Menu
Run a pre-PR readiness check and report READY or NOT READY.
Install with Codex or Claude Copy this prompt, paste it into Codex, Claude, or another assistant, and let it review the skill page and install it for you.
Based on SOC occupation classification
This project uses flow for automation. When asked to build, test, run, deploy, lint, generate, or perform any dev task, check for a flow executable before falling back to raw shell commands.
Scaffold a new Cobra CLI command following the project's patterns.
Add a new executable type to the flow runner (a new kind of automation block users can define in .flow files).
Run flow validate and fix any failures. Invoke after completing a feature or bug fix to confirm the codebase is clean before committing.
| name | pr-ready |
| description | Run a pre-PR readiness check and report READY or NOT READY. |
| disable-model-invocation | true |
| allowed-tools | Bash(git *) Bash(flow validate:*) Bash(flow generate:*) Bash(go test:*) Read |
Check whether the current branch is ready to open a PR. Work through each item and report PASS or FAIL:
No focus markers — grep -rn "FDescribe\|FIt\|FEntry\|FContext\|FWhen" --include="*.go" .
Any match is a FAIL — these silently exclude all other tests in the suite.
Validation passes — run flow validate. All steps must pass.
No debug artifacts — grep for fmt.Println, spew.Dump in cmd/, internal/, pkg/.
Flag anything that looks like leftover debug output (not legitimate logging).
Commit message format — git log main..HEAD --oneline.
Each commit should be: imperative, lowercase, ≤72 chars (fix: ..., feat: ..., refactor: ...).
No direct edits to generated files — git diff main...HEAD --name-only should not show changes to types/**/*.go, docs/cli/*.md, or docs/types/*.md in isolation (without a corresponding schema change).
After all checks: report overall READY or NOT READY with a concise summary of what needs fixing. Do not open a PR automatically — let the user decide.
