What problem does it solve? Writing pull request descriptions and managing the PR lifecycle manually is error-prone: bodies recap what the diff already shows, branches end up misnamed, evidence screenshots get committed or lost, and PRs go ready before their evidence is verified. This Skill standardizes the entire send-for-review workflow from branch naming to readiness gating. ## Core Features & Use Cases - Conventional branch and title management: Moves work onto a <type>/<short-kebab-description> branch without losing commits, and writes Conventional Commit titles under 70 characters. - Necessity-tested PR bodies: Writes descriptions that lead with why the change exists, surface non-obvious decisions with safety resolutions, and cut anything the diff already explains. - Evidence workflow with readiness gating: Assesses screenshots, recordings, or before/after CLI text on every PR, delegates media capture to the before-and-after skill, verifies rendered results, and only marks the PR ready when evidence is verified or intentionally skipped. - Use Case: You finished a CLI bug fix on the default branch. The Skill moves the commits to a fix/count-output branch, drafts a concise PR body with labeled before/after command output, creates a draft PR via gh, verifies the evidence renders, and marks it ready. ## Quick Start Send my current work for review as a pull request with appropriate evidence.
