kata-pr-prepare

What problem does it solve?

It solves the coordination gap between code changes and a fully traceable, policy-compliant GitHub Pull Request by automating branch creation, pushes, PR composition, and required QA/ADR/issue state transitions.

Core Features & Use Cases

• Branch + PR orchestration: Creates a correctly named branch and PR, pushes all modified files with Conventional Commit messages, and links the PR to the originating issue.
• Structured PR body with traceability: Generates a consistent PR body referencing the Gate 2 quality report, architecture/requirements artifacts, and session trace data.
• Quality guardrails before review: Enforces an inviolable Gate 2 “go/no-go” prerequisite, runs up to three Argos pre-flight review cycles (with explicit user confirmation), handles P0/P1 findings, and supports CHANGES_REQUESTED resets.
• Human review escalation loop: Schedules up to three timed nudges with Slack notifications (or supports manual/remote scheduling) and reacts to APPROVED vs CHANGES_REQUESTED outcomes.
• ADR lifecycle + checkpoint updates: Transitions ADRs from proposed to accepted and updates the final workflow checkpoint with PR URL, branch, and completion status.

Quick Start

Use kata-pr-prepare to prepare and open a GitHub PR for a given issue after a Gate 2 quality report returns go, ensuring the PR body references the corresponding .ahrena artifacts and that ADR/checkpoint states are updated.