github-dev-standards

Enforces GitHub commit, artifact retention, and repository management standards on development tasks.

Updated Sep 16, 2026
One-click install
npx skills add https://github.com/Military-Veteran-Team-LPT-Realty/mvt-manus-public-skills --skill github-dev-standards-military-veteran-team-lpt-realty
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: github-dev-standards
Source: https://github.com/Military-Veteran-Team-LPT-Realty/mvt-manus-public-skills/tree/main/skills/github-dev-standards
Command: npx skills add https://github.com/Military-Veteran-Team-LPT-Realty/mvt-manus-public-skills --skill github-dev-standards-military-veteran-team-lpt-realty

SYSTEM DOCUMENTATION & REQUIREMENTS

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.

Frequently Asked Questions about github-dev-standards

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I enforce Conventional Commits in a GitHub workflow?

Conventional Commits use a structured format of type, optional scope, and description, such as feat(auth): implement OAuth2 login. Commit at every logical unit of progress using types like feat, fix, docs, chore, refactor, ci, and test so the full development history stays traceable.

How do I preserve GitHub Actions build artifacts and logs?

Use actions/upload-artifact@v4 in your workflow with retention-days set to 90 for both build outputs and logs. Add an if: always() condition on log uploads and an if: failure() notification step so artifacts persist even when builds fail.

How do I create a private GitHub repository with the gh CLI?

Run gh repo create <name> --private --description "<desc>" to create a private repository from the command line. The standards require the --private flag by default and initializing with a README, .gitignore, and LICENSE where applicable.

How do I enable branch protection on main using the GitHub API?

Use gh api repos/<account>/<repo>/branches/main/protection with the PUT method, passing required_status_checks, required_pull_request_reviews with one approving review, and enforce_admins settings. This blocks direct pushes and requires reviewed PRs before merging.

When should I back up GitHub Actions logs to external storage?

Back up logs to an external persistent store such as Google Drive, a dedicated logs repository, or a cloud logging service when they are long-term or business-critical. The 90-day GitHub artifact retention covers standard needs, but critical audit trails may outlive that window.