What problem does it solve? Teams and AI agents working on frontend repos often produce inconsistent branch names, unverifiable PR claims, silent multi-session git collisions, and changelogs that disagree with what actually shipped. This Skill defines one delivery workflow — from branch creation through merge, release, and rollback — so every change follows the same enforceable rules. ## Core Features & Use Cases - Branch and worktree model: Trunk-based branching with a decision table for when to use a git worktree, including the shared-HEAD hazard when two sessions share one checkout. - Commit and PR discipline: Conventional-commit format enforced by commitlint, merge-commit-only history, a four-section PR body template, and a pre-push gate (typecheck, lint, tests, build) that stops at the first failure. - Review, release, and rollback: Two parallel required reviews (conventions and correctness), Changesets-based versioning where the release job owns CHANGELOG.md, and revert commands named before merging. - Use Case: An agent starting a feature creates feat/AB-1420-inline-citations, opens a draft PR after the first commit, runs the gate, gets both reviews, and merges with a changeset — with every step verifiable. ## Quick Start Ask the agent to start a new feature following the frontend workflow, including branch naming, the pre-push gate, and a draft PR with the required body sections.
