| name | pre-merge-checklist |
| description | Final merge-readiness check after gates pass. Confirms verification is green, changed files are clean, and obvious release blockers are gone before merge. |
| owner | any |
| trigger | pr_ready |
| version | 2 |
Pre-Merge Checklist
Use this when a task is ready to merge.
Checklist
- Confirm the required gates passed for the task.
- Rerun the relevant verification stack or confirm a fresh passing run exists.
2a. If the repo uses a type system, confirm the latest typecheck/compile gate passes, and verify any new or changed imports, type aliases, and symbol references resolve against the current exports; check for renamed or removed symbols, duplicate declarations, and stale local aliases in shared modules/types/models.
2b. If shared modules/types/models were touched, verify all downstream consumers still compile against the current exported names and definitions.
2c. If changes touch shared type or model contracts, confirm there are no stale local aliases, missing symbols, or duplicate declarations before merge.
- Review changed files for:
TODO / FIXME left behind unintentionally- debug logging or temporary prints
- commented-out code that should be removed
- stale docs when public behavior changed
- Confirm the branch is still mergeable against the target branch.
- Report either:
READY TO MERGE- or the remaining blockers
Notes
- Do not invent extra type-system rituals that are repo- or language-specific unless the repo already requires them.
- Keep this as a final hygiene and readiness pass, not a second full architecture review.
