Skip to content
OpenAgentSkill
Browsing is open · Catalog captured 2026-11-21 · Automatic updates and account services are paused.
Development

generate-commit-message

Derive one Conventional Commits v1.0.0 message from the staged diff and create the signed commit directly. Trigger only on explicit intent to commit: "commit this", "commit these changes", "/commit", "go ahead and commit", "make the commit", "git commit", or a confirmation like "yes, commit it". Enforces the type enum, 72-char subject, 100-char body/footer lines, and a required AI-attribution trailer, so the result passes commitlint on the first try. Do NOT trigger on message-only questions ("write a commit message", "what should the commit message be") — this skill's only output path is a real commit, and answering those with one records work the user merely asked to preview.

anchildress1 · Static checks on file

Installation

Read the source and dependencies before running a command. Copying does not install or execute anything.

npx skills add anchildress1/awesome-github-copilot --skill generate-commit-message

About this skill


status: check name: generate-commit-message description: > Derive one Conventional Commits v1.0.0 message from the staged diff and create the signed commit directly. Trigger only on explicit intent to commit: "commit this", "commit these changes", "/commit", "go ahead and commit", "make the commit", "git commit", or a confirmation like "yes, commit it". Enforces the type enum, 72-char subject, 100-char body/footer lines, and a required AI-attribution trailer, so the result passes commitlint on the first try. Do NOT trigger on message-only questions ("write a commit message", "what should the commit message be") — this skill's only output path is a real commit, and answering those with one records work the user merely asked to preview. argument-hint: "optional: JIRA-123 or issue key/scope hint" allowed-tools: Bash, Read disable-model-invocation: false user-invocable: true

Produce exactly one Conventional Commits v1.0.0 message from the diff, then commit it signed. The commit is the deliverable — no draft file, no staging, no push.

Boundaries

The only repo-mutating command permitted is git commit -S. Everything else is off-limits:

NeverWhy
git add / stage anythingCommit scope is the user's decision, already expressed by what's staged
git push, rebase, reset, commit --amendHistory mutation isn't this skill's job
--no-verify, --no-gpg-signHooks and signing must run
Edit source, docs, or configNo formatters, lint fixes, refactors, or test runs
Commit on main/masterUnless the user directed it this turn
Omit the AI-attribution trailerA message without it is a failed message

Abort conditions

Stop and report; do not work around:

  • No staged diff → nothing staged. Do not stage on the user's behalf.
  • On main/master without explicit authorization this turn.
  • Diff changed between derivation and commit (see step 5).

1. Resolve scope

Precedence, first match wins. Jira key regex [A-Z][A-Z0-9]+-\d+, matched case-insensitively, emitted uppercase:

  1. User-provided key (request or argument-hint)
  2. Branch name — git --no-pager rev-parse --abbrev-ref HEAD
  3. None — omit the scope

Never invent a keyword scope (core, api, docs) when no issue key exists. An absent scope is correct; a made-up one is noise. The diff informs type and subject, never scope.

2. Acquire diff

git --no-pager diff --cached

Empty → abort. There is no working-tree fallback: git commit records the index, so a message derived from unstaged edits would describe changes the commit doesn't contain — and the commit would fail anyway with nothing staged.

Derive everything from hunks only: chat history, prior commits, and memory are not evidence of what this diff changes.

3. Pick type

First match wins:

SignalType
Public API removed, signature changed, config key droppedbreaking — add ! and/or BREAKING CHANGE:
New user-visible capabilityfeat
Defect repair, no new surfacefix
Faster, same behaviorperf
Restructure, same behaviorrefactor
Whitespace, formatting, semicolonsstyle
Tests onlytest
Docs, comments, JSDoc/KDoc onlydocs
.github/workflows, .circleci, CI configci
Build system, deps, packagingbuild
Reverts a prior commitrevert
Maintenance, no production impactchore

4. Pick attribution tier

Exactly one, from diff hunks + this session:

AI share of the workTrailer
MajorityGenerated-by
Roughly halfCo-authored-by
Minor assistAssisted-by
Only wrote this messageCommit-generated-by

Uncertain → pick the tier that credits the human more.

Co-authored-by is the one tier GitHub actually parses and renders on the commit, which is the point of it — don't substitute a variant spelling. The other three are custom trailers that git carries verbatim.

5. Compose and validate

<type>[(<scope>)][!]: <subject>

- <single-line bullet>
- <single-line bullet>

<footers>

Format constraints — every one maps to a commitlint rule, so a violation is a hook failure, not a style opinion:

  • Subject ≤ 72 chars, no trailing period, imperative present tense. Not Title Case, sentence-case, PascalCase, or UPPER — but real identifiers keep their casing (OAuth2, JSDoc, API)
  • Type lowercase, from the enum in step 3
  • Body and footer lines ≤ 100 chars; bullets never wrap
  • Exactly one blank line after the subject, exactly one before the footers, none elsewhere
  • Group changes and say what and why. File-by-file listings and how are wasted lines. Quantify where it helps ("add 3 fixtures", "drop 412 LOC").

Footer order, when present:

  1. Refs: PROJ-123 / Closes #42
  2. BREAKING CHANGE: <incompatibility and required action> — only when the ! alone doesn't tell the user what to do. Both forms together are valid.
  3. AI attribution — required, exactly one, from step 4.

Trailers use - for spaces (Reviewed-by); BREAKING CHANGE is the spec's one exemption. A footer too long to fit in 100 chars folds onto a continuation line with a leading space.

Match the repo before emitting. Read commitlint.config.js (or .commitlintrc*) if present and honor overrides — scope-case, stricter lengths, a narrowed type enum. Then check git --no-pager log -3 for trailers this repo actually uses (Signed-off-by, Refs) and mirror them. A message that passes the generic spec but trips this repo's hook is still a failure.

Then verify before committing:

  • Header matches ^(build|chore|ci|docs|feat|fix|perf|refactor|revert|style|test)(\([^)]+\))?!?: .+$
  • No line over its limit; exactly one attribution trailer present

Failing any check → regenerate. Never emit a non-conformant message.

6. Re-check the diff

Re-run the step 2 command immediately before committing. If it changed, the message desc

Read the complete source ↗