by Pras
The pull-request lifecycle against a merge bar fixed when the PR opens. Open a PR whose body carries six fields (Claim, Scope, Known limits, Merge bar, Evidence, Closes); work it by sorting every reviewer finding as blocking or non-blocking against that bar, one push per round, with a stop at round 3 when the fixes are generating the findings, and non-blocking findings answered in the thread or recorded as known limits in the paired AI workspace's tech-debt ledger instead of filed as issues; and teach a repository's reviewers the bar through an AGENTS.md Code Review Rules section and, on public repositories, a .coderabbit.yaml. Three prose skills, three slash commands, no lib, no state.
CodexClaude Code3 Skills