What problem does it solve? Teams working on the Portal Centralizado de Datos Financieros need consistent Git discipline across epics and user stories: uniform branch names, scoped Conventional Commits, PRs targeting develop, and traceable user story closure. This Skill removes ambiguity and prevents mistakes like committing directly to main or opening PRs without a clean check. ## Core Features & Use Cases - Branch and commit conventions: Enforces feature/E{epic}-US-XXX-{slug} branch names and Conventional Commits with epic scopes (UX, E0–E5), with no AI co-author trailers or emojis. - PR and merge workflow: Guides the full cycle from branching off develop, running make check before opening a PR with gh, squash merging, and releasing to main which triggers Cloud Run deployment. - User story closure: Verifies acceptance criteria against the project plan and references absorbed user stories for backlog traceability. - Use Case: A developer finishing a JWT authentication user story creates branch feature/E2-US-XXX-jwt-rbac, commits with feat(E2) scopes, runs make check, and opens a PR to develop with verified acceptance criteria. ## Quick Start Ask the assistant to create a new feature branch and commit your changes for user story US-XXX following the portal Git workflow conventions.
