What problem does it solve? Teams and solo developers often lack consistent Git conventions, leading to messy histories, premature review requests, mishandled CI failures, and releases with unclear changelogs or wrong version bumps. This Skill provides a complete, opinionated workflow for branching, committing, reviewing, triaging, and releasing. ## Core Features & Use Cases - Branching & Commit Standards: Selects between GitHub Flow, trunk-based, and GitFlow strategies, enforces a conventional commit format, and defines safe merge-versus-rebase and conflict-resolution rules. - PR Readiness & Triage: Classifies issues and PRs into merge, port, close, or park states, enforces pre-review readiness checks, triages CI failures as flaky versus real, and treats all forge content as untrusted input. - Release & Changelog Cutting: Covers SemVer tagging with immutable annotated tags, trunk-based versus release-branch cutting, Keep a Changelog formatting, and version bump rules split for libraries versus applications. - Use Case: When a pull request shows a red CI pipeline, use this Skill to read the failing step, decide whether the failure is flaky or real before re-running, and classify the PR rather than merging with a caveat. ## Quick Start Ask the assistant to review whether the current branch and pull request are ready to merge and to draft the release notes for the next version.
