Git and GitHub

Conventional Commits, Semantic Versioning and Keep a Changelog apply as published. This skill adds the committing discipline, the release conventions, and the live action-version check.

When the repo's AGENTS.md or CLAUDE.md sets its own rules for commits, branches, trailers or workflows, those rules win over every default below.

Committing

1. Stage by explicit path: git add -- <path>....
2. Review the staged set with git diff --cached --stat (git status --short shows the whole tree).
3. Commit once the staged set holds exactly the files this change touched.

Message: subject type(scope): subject - imperative, lowercase, no full stop, 72 characters or fewer. The body says what changed and why.

Branches: feature/, fix/, docs/ or refactor/ plus a short description, merged to the default branch through a pull request.

Releases