Repo conventions

If tests are not changed in the diff, explicitly say "Not shown in diff."

tools-only Updated 7 repo stars

File contents

Repo conventions

Branch naming

We use different branch prefixes depending on change type:

  • Features: feat/
  • Bug fixes: bug/-
  • Chores: chore/

Notes:

  • must be lowercase (e.g., cal-204)
  • must be lowercase ASCII, digits allowed, hyphens only (no underscores)

Commit messages

Also differs by change type:

  • Bug fixes: []
    • must preserve original casing (e.g., CAL-204)
    • Summary must be short, Title Case, no trailing period
  • Features/chores: Conventional Commits subject line, e.g. "feat: add X", "chore: bump Y"

PR description

If tests are not changed in the diff, explicitly say "Not shown in diff."

tools-only/X-Skills/tree/main/development/testing/1298-006-agents_84b8c53a commit 45223d73de

Frequently asked questions

npx skillmds@latest add tools-only/repo-conventions