conventionslisted

Defines the commit message, branch naming, pull request, and release note conventions for the ai-agent-skills repository. Make sure to load this skill whenever writing a commit message, naming a branch, drafting a PR title or body, or writing CHANGELOG entries in this repo. Use when the user asks "how should I format this commit", "what's the branch naming convention", "how do I write the PR", "what commit type should I use", or before any git commit, PR creation, release note, or CHANGELOG task in this project.
psenger/catholic-ai-skills · ★ 1 · Code & Development · score 68

Install: claude install-skill psenger/catholic-ai-skills

# Conventions — ai-agent-skills --- ## Commit Messages Format: `type(scope): subject` - **Subject:** imperative mood, lowercase, no trailing period, ≤72 characters - **Scope:** the skill name (`vault-scribe`, `handoff`) or a repo area (`release`, `ci`, `readme`) - **Body:** optional — explain *why*, not *what*; wrap at 72 chars - **Footer:** `Closes #N` or `Fixes #N` for GitHub issues; `BREAKING CHANGE: <desc>` for breaking changes ### Types | Type | When | |------------|---------------------------------------------------------| | `feat` | New skill or new capability in an existing skill | | `fix` | Bug fix in a skill's behaviour or instructions | | `chore` | Release commits, tooling, config — no production change | | `docs` | README, CHANGELOG, CONTRIBUTING only | | `refactor` | Skill restructure with no behaviour change | | `test` | Eval additions or changes | ### Release commit — always exactly: ``` chore(release): cut vX.Y.Z release ``` ### Examples ``` feat(handoff): add RESUME workflow and proactive suggestion trigger ``` ``` fix(vault-scribe): prevent incompatible TOC directives Closes #1 ``` --- ## Branch Names Pattern: `type/issue-number-short-description` ``` feature/14-add-handoff-skill fix/23-vault-scribe-toc chore/release-v1-1-0 ``` - `feature/` for new skills or new capabilities - `fix/` for bug fixes - `chore/` for release and tooling work - Alw