What problem does it solve? Software teams often lose traceability between requirements and shipped code, producing anonymous branches, vague commit messages, and pull requests that reviewers cannot map back to approved work. This Skill enforces a Jira-anchored Git workflow so every branch, commit, and PR links back to a ticket. ## Core Features & Use Cases - Jira-Gated Git Outputs: Refuses to generate branch names, commit messages, or workflow recommendations until a valid Jira task ID is provided. - Branch and Commit Standards: Applies patterns like feature/JIRA-214-add-sso-login and ✨ JIRA-214: add SSO login flow, with a decision matrix covering features, bugfixes, hotfixes, refactors, docs, tests, config, and dependencies. - Validation and Templates: Provides a Bash commit-msg validation hook, a pull request template with risk and security review sections, and a delivery planning template. - Use Case: A developer starting a production-critical auth fix asks for guidance; the Skill requires the Jira ID, then produces a hotfix/JIRA-411-patch-auth-bypass branch from main, atomic Gitmoji commits, and a PR with rollback notes. ## Quick Start Ask the agent to plan the branch, commits, and pull request for Jira ticket JIRA-315 fixing a token refresh race condition.
