plan / code-pr

What problem does it solve?

It prevents failed or off-convention pull requests by forcing a disciplined, repo-aware planning process before code changes are proposed.

Core Features & Use Cases

• Repo-first context loading: Reads the action trail, signals, and walks context references, then requires a one-time clone-and-skim of the target repository’s README.md and CONTRIBUTING.md when the repo hasn’t been visited before.
• Approach-discipline enforcement: Ensures the plan includes required clone/branch steps and a specific gh pr create command, selecting exactly one approach at each decision point (no “or” alternatives).
• Bound test planning: Requires the test assertions to match the exact values or behavior committed to in the Approach, so downstream verification is consistent.
• Scope control: Forces explicit out-of-scope boundaries to avoid scope creep.

Quick Start

Ask your agent to generate a code-pr playbook plan that clones the target repo, follows its contribution conventions for branching, and prepares an auditable gh pr create command with a deterministic approach and aligned test expectations.