What problem does it solve? Teams often lose traceability of code changes, build logs, and deployment history because commits are batched, artifacts are discarded, and repositories are configured inconsistently. This Skill enforces a uniform set of GitHub development standards on every coding, debugging, and deployment task. ## Core Features & Use Cases - Conventional Commits Enforcement: Requires all code progression to be committed incrementally using structured Conventional Commits messages (feat, fix, docs, chore, refactor, ci, test) with feature branches and PRs linked to issues. - Artifact and Log Preservation: Mandates GitHub Actions artifact uploads with 90-day retention, semantic version release tagging, failure notifications, and optional backup of logs to external persistent storage. - GitHub Pro Feature Maximization: Standardizes private repository creation via the gh CLI, branch protection on main, Dependabot alerts, required status checks, and other Pro account capabilities. - Use Case: When starting a new project, the Skill guides creation of a private repository with branch protection and Dependabot enabled, then ensures every subsequent change is committed with Conventional Commits and every CI run preserves its build artifacts and logs. ## Quick Start Apply the GitHub development standards to this project by creating a private repository, committing my changes with Conventional Commits, and setting up a workflow with 90-day artifact retention.