Assess whether this branch is ready to be submitted as a reviewable pull request.
Analysis Steps
- Identify the base branch (usually
main) and list all commits since diverging
- Review the full diff for:
- Incomplete work (half-implemented features, placeholder logic)
- Obvious bugs or unhandled edge cases
- Code quality issues that would block a reviewer
- Check commit history:
- Conventional commit compliance (
type(scope): description)
- Logical atomicity β each commit should represent one coherent change
- No WIP, fixup, or junk commits that should have been cleaned up
- Check branch name against naming conventions:
- Format:
<prefix>/<short-description> (lowercase, hyphens, imperative)
- Valid prefixes:
feat, fix, enhance, refactor, types, perf, styles, layout, docs, test, deps, config, build, agents, chore, ci, deploy, spike, experiment, wip, hotfix
- Breaking change branches should use
<prefix>/breaking-<description>
- Scan for anti-patterns:
- Debugging artefacts (
console.log, commented-out code)
- Unresolved conflict markers (
<<<<<<<, =======, >>>>>>>)
TODO / FIXME comments introduced in this branch- Diff size >500 lines (flag for possible split)
- Detect breaking changes:
- Removed or renamed exports, functions, types, or components
- Changed function signatures (required parameters added/reordered)
- Modified return types in a widening direction
- Database schema changes (columns removed/renamed, constraints changed)
- HTTP API changes (routes, methods, request/response shapes)
- New required environment variables
- Changed component props (removed, renamed, type-changed, newly required)
Output Format
Verdict
One of: Ready | Needs Work | Blocked
Branch Health
- Branch name compliance
- Commit message quality
- Commit atomicity
Code Quality Flags
Specific issues found, with file and line references where possible. Omit this section if none found.
Breaking Changes
Any detected breaking changes with context. Flag format:
β οΈ Breaking change β consider feat!: or BREAKING CHANGE: footer
Omit this section if none found.
Recommended Next Steps
Ordered list β blockers first, then improvements, then nice-to-haves.
If the verdict is Ready, offer to run /git:pull-request immediately.
1---2name: review-this-branch3description: {{ πππ }} Assess branch readiness for PR submission4---5
6Assess whether this branch is ready to be submitted as a reviewable pull request.
7
8## Analysis Steps
9
101. Identify the base branch (usually `main`) and list all commits since diverging
112. Review the full diff for:
12 - Incomplete work (half-implemented features, placeholder logic)
13 - Obvious bugs or unhandled edge cases
14 - Code quality issues that would block a reviewer
153. Check commit history:
16 - Conventional commit compliance (`type(scope): description`)
17 - Logical atomicity β each commit should represent one coherent change
18 - No WIP, fixup, or junk commits that should have been cleaned up
194. Check branch name against naming conventions:
20 - Format: `<prefix>/<short-description>` (lowercase, hyphens, imperative)
21 - Valid prefixes: `feat`, `fix`, `enhance`, `refactor`, `types`, `perf`, `styles`, `layout`, `docs`, `test`, `deps`, `config`, `build`, `agents`, `chore`, `ci`, `deploy`, `spike`, `experiment`, `wip`, `hotfix`
22 - Breaking change branches should use `<prefix>/breaking-<description>`
235. Scan for anti-patterns:
24 - Debugging artefacts (`console.log`, commented-out code)
25 - Unresolved conflict markers (`<<<<<<<`, `=======`, `>>>>>>>`)
26 - `TODO` / `FIXME` comments introduced in this branch
27 - Diff size >500 lines (flag for possible split)
286. Detect breaking changes:
29 - Removed or renamed exports, functions, types, or components
30 - Changed function signatures (required parameters added/reordered)
31 - Modified return types in a widening direction
32 - Database schema changes (columns removed/renamed, constraints changed)
33 - HTTP API changes (routes, methods, request/response shapes)
34 - New required environment variables
35 - Changed component props (removed, renamed, type-changed, newly required)
36
37## Output Format
38
39### Verdict
40One of: **Ready** | **Needs Work** | **Blocked**
41
42### Branch Health
43- Branch name compliance
44- Commit message quality
45- Commit atomicity
46
47### Code Quality Flags
48Specific issues found, with file and line references where possible. Omit this section if none found.
49
50### Breaking Changes
51Any detected breaking changes with context. Flag format:
52> β οΈ Breaking change β consider `feat!:` or `BREAKING CHANGE:` footer
53
54Omit this section if none found.
55
56### Recommended Next Steps
57Ordered list β blockers first, then improvements, then nice-to-haves.
58
59---
60
61If the verdict is **Ready**, offer to run `/git:pull-request` immediately.
majiayu000