What problem does it solve?
Managing a pull request end-to-end involves scattered judgment calls: verifying whether the PR actually solves the right problem, adjudicating reviewer and bot feedback against evidence, keeping CI and review state tied to the current head, and porting accepted changes across version lines. This Skill orchestrates that entire lifecycle with explicit human gates so nothing is merged, pushed, or claimed without evidence.
Core Features & Use Cases
- Evidence-based PR review: Reconstructs the PR's intent, identifies the canonical code owner, detects duplicate or split-brain logic, and produces a merge verdict (mergeable, mergeable after refinements, or not recommended).
- Feedback adjudication: Reproduces each review finding from current source, classifies it as confirmed, stale, invalid, or not applicable, and applies only confirmed corrections with TDD.
- Cross-version porting: Carries a 0.2-line PR and every accepted follow-up into the 0.3 line with preserved intent and per-commit co-author attribution.
- Use Case: A maintainer asks whether a contributor's PR is safe to merge; the Skill fetches the live head, audits the diff, posts refinements, monitors CodeRabbit and human reviewers, fixes confirmed findings, ports them to the 0.3 branch, and reports final SHAs and residual risk.
Quick Start
Use the happier-pr-steward skill to analyze pull request number 123 in the happier repository, propose evidence-backed refinements, and shepherd the approved changes through review.
