github-standards

Enforces GitHub repository conventions for commits, PRs, branches, secrets scanning, and CI configuration.

Updated Jan 1, 2026
One-click install
npx skills add https://github.com/sarkarshivaditya-lab/WellMate --skill github-standards-sarkarshivaditya-lab
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: github-standards
Source: https://github.com/sarkarshivaditya-lab/WellMate/tree/main/.engineering-skills/0xMassi-claude-skills/github-standards
Command: npx skills add https://github.com/sarkarshivaditya-lab/WellMate --skill github-standards-sarkarshivaditya-lab

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve? Teams and solo developers often ship inconsistent commit messages, leaky secrets, missing READMEs, and ad-hoc CI setups across repositories. This Skill codifies repository and workflow conventions distilled from 22+ production repos so every project follows the same enforceable standards. ## Core Features & Use Cases - Secrets Pre-Commit Scanning: Provides grep patterns and remediation steps to catch API keys, tokens, and private keys before they enter git history. - Commit, PR, and Branch Conventions: Defines Conventional Commits message structure, a PR body template with test plan checklist, and kebab-case branch naming rules. - Repo Setup Baselines: Supplies required-file checklists, .gitignore baselines per language, README structure, semantic release tagging, CI/CD workflow templates, and supply-chain hardening (SHA-pinned actions, permissions blocks, Dependabot, CODEOWNERS). - Use Case: When creating a new repository or opening a pull request, invoke this Skill to generate a compliant README, .gitignore, PR description, and CI workflow in one pass. ## Quick Start Ask the assistant to set up a new GitHub repository following the github-standards conventions, including README, .gitignore, branch naming, and CI baseline.

Frequently Asked Questions about github-standards

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

FAQPage Schema
How do I write a conventional commit message for GitHub?▼

Use the format type(scope): subject in imperative mood under 72 characters, with types like feat, fix, docs, chore, refactor, ci, style, test, or perf. The body explains why the change was needed, what changed, and what problem it solves, wrapped at 72 characters.

How do I prevent committing secrets and API keys to git?▼

Run a grep scan over staged files before every commit to catch patterns like API keys, tokens, and private keys. Keep secrets in gitignored .env files, commit only an .env.example template, and rotate any exposed secret immediately since git history retains it.

What files should every new GitHub repository include?▼

Every repo should start with a README.md covering setup and architecture, a .gitignore with OS, IDE, secrets, and build-artifact patterns, a CLAUDE.md for AI context, and a LICENSE for public repos. Add .env.example once the first environment variable is introduced.

How do I secure GitHub Actions workflows against supply chain attacks?▼

Pin every third-party action to a full commit SHA instead of a mutable tag, and declare an explicit permissions block defaulting to contents: read. Add Dependabot for github-actions updates and use CODEOWNERS with branch protection to require review of workflow changes.

What should a pull request template include?▼

A PR template should include a summary, linked issue, description of changes, and a test plan checklist covering type checks, linting, existing tests, and manual verification. Keep PRs under 400 lines, one concern per PR, and use squash merging for linear history.