pr-ready
Run a pre-PR readiness check and report READY or NOT READY.
SKILL.md.claude/skills/pr-ready/SKILL.md
GitHubCheck 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 the
validateexecutable viamcp__flow__execute(ref:validate). All steps must pass. Usemcp__flow__run_commandfor thegit/grepchecks below so they land in flow's history alongside it.No debug artifacts — grep for
fmt.Println,spew.Dumpincmd/,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-onlyshould not show changes totypes/**/*.go,docs/cli/*.md, ordocs/types/*.mdin 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.