Skip to content

Unique-AG/ai / .claude/skills/git-conventional-commits

git-conventional-commits

Verified

Guide branch creation, commit messages, and titles so the repo’s semantic workflow is enforced

When to use

  • When the user authors commits
  • When the user asks about conventional commits

Use Instead [if available]

  • Use pr-create for end-to-end PR title/body drafting and Jira-linking workflow.
  • Use github-pull-request-handling for resolving and replying to existing PR review conversations.

Standard

Apply the Conventional Commits 1.0.0 specification for commit messages and PR titles.

Allowed types

Use exactly one of these types in PR titles and commits:

TypePurpose
choreMaintenance, tooling, config changes
ciCI/CD pipeline changes
deployDeployment-related changes
docsDocumentation only
featNew feature
fixBug fix
improvementGeneral improvement (non-feature, non-fix)
perfPerformance improvement
buildBuild system/dependency changes
refactorCode refactoring, no behavior change
styleFormatting only, no behavior change
testAdding or updating tests

Format

<type>[(scope)]: <description>

[optional body]

[optional footer(s)]
  • Scope (optional): Must match [a-z:_-]+ (lowercase letters, digits, underscores, colons, hyphens). Examples: sdk, api, my_component.
  • Description: Short, imperative summary. No period at the end.

Breaking changes

For breaking changes, append ! after type/scope and include a BREAKING CHANGE: footer when relevant.

Example:

feat(api)!: switch auth token format

BREAKING CHANGE: clients must re-authenticate with the new token format

Body and footers

  • Body is optional and should explain motivation ("why"), not only implementation details.
  • Separate body from subject with one blank line.
  • Use explicit footers for traceability, such as:
    • BREAKING CHANGE: <description>
    • Refs: UN-12345 or Refs: #123
    • Reviewed-by: <name>

Commit Summary

  • feat(toolkit): add streaming support
  • feat(sdk): update message endpoint
  • ci: add semantic PR validation

Branch & commit workflow

  1. Check current branch

    • Run git branch --show-current; do not commit directly to master/main
    • If you are still on the base branch, create a feature branch following this pattern: fix/<scope>/<short-slug> or feat/<scope>/<short-slug>
    • Keep branch names short but descriptive (e.g., fix/payment/null-check)
  2. Review & stage

    • Inspect your diff (git diff for unstaged, git diff --cached for staged)
    • Stage with git add -A once you understand all changes
    • Optionally include Refs: <ticket> block in the commit body to link Jira/Ticket numbers (the repo tooling can pick this up)
  3. Write the commit

    • Use the <type>(<scope>): <description> format
    • Keep the subject ≤ 72 characters without trailing period
    • Add a blank line and optional body for context, explaining why the change is necessary
  4. Examples

    • fix(api): handle missing authorization header
    • feat(payments): add refund webhook handler
    • chore(deps): upgrade pytest to 9.0

Branch/commit rules

  • Always branch before committing (avoid master/main)
  • Use imperative language and don’t end with punctuation
  • Keep commits focused on a single concern
  • Reference tickets/issue IDs in the Refs: section when relevant

Quick checklist

Before finalizing a commit message or PR title:

  • Starts with a valid type
  • Scope is specific and relevant
  • Description is imperative and has no trailing period
  • First line is under 72 characters
  • Breaking changes use ! and/or a BREAKING CHANGE: footer
  • Body explains motivation for non-trivial changes
planning-and-task-breakdownaddyosmani/agent-skillsBreaks work into ordered tasks. Use when you have a spec or clear requirements and need to break work into implementable tasks. Use when a task feels too large to start, when you need to estimate scope, or when parallel work is possible.Stars: 118kUpdated Claude CodeCodexVerifiedInstall
screenpipethedotmack/claude-memSearch screen and audio history recorded by Screenpipe and optionally save selected context into claude-mem. Use when the user asks to recall desktop activity, a meeting, or something seen in another app through Screenpipe.Stars: 117kUpdated Claude CodeCodexVerifiedInstall
contact-widgetnexu-io/open-designSelf-contained floating chat widget with welcome screen, social links, meeting button, and message input. Single HTML file, zero dependencies.Stars: 108kUpdated Claude CodeCodexVerifiedInstall
meeting-notesnexu-io/open-designMeeting notes page — title bar with attendees, agenda checklist, decisions block, action items table with owners + dates, and a "next meeting" footer. Use when the brief mentions "meeting notes", "minutes", "1:1 notes", "all-hands recap", or "会议纪要".Stars: 108kUpdated Claude CodeCodexVerifiedInstall