Organizes pending changes into clean, scoped Conventional Commits.

Install

mkdir -p .claude/skills/commit-this-is-npc && curl -L -o skill.zip "https://agentskills.codes/api/skills/download/13028" && unzip -o skill.zip -d .claude/skills/commit-this-is-npc && rm skill.zip

Installs to .claude/skills/commit-this-is-npc

Activation

This is the description your AI agent reads to decide when to run this skill — the better it matches your request, the more reliably it fires.

Create commits for all pending repository changes by strictly following CONTRIBUTING.md commit rules. Use when the user asks to commit changes, organize commits by scope, avoid oversized commits, or enforce Conventional Commits messages in English.
248 chars✓ has a “when” trigger
Intermediate

Key capabilities

  • Read `CONTRIBUTING.md` for project standards
  • Inspect pending changes using Git commands
  • Group files by a single intent for each commit
  • Separate changes into scope-specific commits
  • Stage and commit files/hunks for one scope at a time
  • Ensure commit messages are in English and concise

How it works

The skill reads project commit standards, inspects pending changes, and groups them by intent. It then creates atomic, scope-specific commits following Conventional Commit message format.

Inputs & outputs

You give it
User request to commit changes, organize commits by scope, or enforce Conventional Commits
You get back
Multiple small, scoped Git commits adhering to `CONTRIBUTING.md` standards

When to use commit

  • Committing pending work
  • Grouping changes by scope
  • Enforcing Conventional Commit messages

About this skill

Commit

Overview

Create small, scoped commits from the current working tree. Follow CONTRIBUTING.md exactly for commit standards and message format.

Additional context (optional): $ARGUMENTS

Workflow

  1. Read CONTRIBUTING.md for project standards, template paths, and tool configuration.
  2. Inspect pending changes with git status --short and git diff --name-only.
  3. Group files by a single intent per commit (feat, fix, docs, refactor, chore, test, build, ci, perf).
  4. When one file contains multiple scopes, separate changes into scope-specific commits using non-interactive staging/editing.
  5. Stage only the files/hunks for one scope and commit.
  6. Repeat until all pending changes are committed.

Co-authorship

  • Never add Co-Authored-By or any co-author trailer to commit messages.
  • Only include co-author information when the user explicitly requests it in the current conversation.

Execution Checklist

  1. Confirm grouping is by scope, not by file count only.
  2. Confirm commit message type matches the real change intent.
  3. Confirm message is English and concise.
  4. Confirm no unrelated file is staged.
  5. Confirm no Co-Authored-By trailer is present (unless explicitly requested).
  6. Confirm working tree is clean after final commit.

When not to use it

  • When `CONTRIBUTING.md` rules are not to be followed
  • When co-author information is not explicitly requested
  • When a single commit for all changes is desired

Limitations

  • Does not add `Co-Authored-By` unless explicitly requested
  • Does not stage unrelated files
  • Requires `CONTRIBUTING.md` to be present and followed

How it compares

This workflow enforces strict adherence to project-specific commit standards and creates granular commits, contrasting with generic or oversized commits.

Compared to similar skills

commit side by side with the closest alternatives in the catalog.

SkillInstallsUpdatedSafetyDifficulty
commit (this skill)04moNo flagsIntermediate
resolve-conflicts818moReviewIntermediate
openspec-onboard106moReviewBeginner
codex-cli-bridge99moReviewIntermediate

Try saying

Example prompts that trigger this skill in your AI assistant.

Search skills

Search the agent skills registry