← ClaudeAtlas

pr-lifecyclelisted

Reference document describing PR lifecycle: pre-flight gates (4 conditions), verification gate (5 conditions), body structure (7 sections), reviewer-suggestion algorithm (CODEOWNERS → file expertise → recent activity → workload balance), and finding-ledger merge prerequisite. Reference only (policy document; consumed by `/flow:pr` and `/flow:merge`).
synaptiai/synapti-marketplace · ★ 5 · AI & Automation · score 70
Install: claude install-skill synaptiai/synapti-marketplace
# PR Lifecycle Reference document for the PR creation and pre-merge policy. The executable bash lives in `plugins/flow/commands/pr.md` (full creation flow) and `plugins/flow/commands/merge.md` (finding-ledger check). This skill describes **what those commands enforce and why**, so reviewers can audit the policy without reading shell. ## Iron Law **NO PR WITHOUT VERIFICATION. Every PR must have proof that quality checks pass. "I think it works" is not a PR description.** If you can't show test results, lint output, or verification evidence in the PR body, the PR is not ready. ## Pre-Flight Gate Before any PR is created, four conditions are verified: | # | Condition | Failure handling | |---|-----------|------------------| | 1 | Not on the default branch | Hard error — PRs are made from feature branches, never from `main` | | 2 | At least one commit ahead of the default branch | Hard error — empty PRs are noise | | 3 | No uncommitted changes | Warning — offer to commit first via `/flow:commit` | | 4 | No existing open PR for this branch | Hard error — update the existing PR instead of creating a duplicate | The runnable checks are in `plugins/flow/commands/pr.md` Phase 1 (EXPLORE). The command is the single source of truth. ## Verification Gate Before the PR is created, every one of the following must hold. If any fail, stop: 1. All quality commands (lint, test, typecheck) pass — output captured for the PR body 2. Self-review completed against the `code-quality-princ