New: 97,000+ skills indexed from GitHub repos with 100+ stars · every skill safety-checkedBrowse top skillsTop skills
Esc to closeBrowse all skills
Submit a skillBrowse skills
Submit a skillBrowse skills

Agent skill

Create Commit

by TwiTech-LAB in TwiTech-LAB/devchain

Create a git commit whose message records why the change exists, not just what changed.

MITAuto-check passedDevelopment

Install Create Commit

skills CLI
$ npx skills add TwiTech-LAB/devchain --skill create-commit -a claude-code

Project install by default; add -g for ~/.claude/skills/.

GitHub CLI
$ gh skill install TwiTech-LAB/devchain create-commit --agent claude-code

Project scope by default; add --scope user for a personal install. Needs GitHub CLI 2.90.0 or later (public preview).

Manual copy
$ git clone --depth 1 https://github.com/TwiTech-LAB/devchain.git skills-src && mkdir -p .claude/skills && cp -r skills-src/apps/local-app/skills/create-commit .claude/skills/create-commit && rm -rf skills-src

Use ~/.claude/skills/ instead of .claude/skills for a personal install. The folder must contain SKILL.md.

Claude Code skills documentation · loads skills from .claude/skills/

Facts

Skill name
create-commit
GitHub stars
101
Token cost
~1.2k tokens
SKILL.md length
680 words
Files
1
Skills in repo
6
Repo updated
First seen
Licence
MIT

At a glance

Create a git commit whose message records why the change exists, not just what changed.

  • Works in 5 steps: What was wrong before. State the old… → Why the obvious fix doesn't work. If you… → Non-obvious constraints that shaped the… → …
  • Asked to commit work
  • SKILL.md covers One logical change per commit, Subject line, Body — spend your context here and Never, plus 2 more sections
  • Calls git

What it does

Create Commit is an agent skill from TwiTech-LAB/devchain. Create a git commit whose message records why the change exists, not just what changed. Keeps one logical change per commit, stages only the files that belong to it, matches the repo's existing commit style, keeps the body to decisions and traps rather than implementation, and shows the message and staged files for user approval before committing. Use when asked to commit work or write a commit message. Triggers: create a commit, commit this, commit the changes, write a commit message.

Its SKILL.md is about 1.2k tokens, which your agent loads only when the skill is triggered. It is a single SKILL.md file with no bundled scripts.

It sits in Development, covering Commit messages. The repository describes itself as: Run a team of AI coding agents. On your machine. Local-first orchestration for Claude Code, Codex, OpenCode, Antigravity, and Copilot. The licence is MIT.

When your agent uses it

  • Asked to commit work
  • Write a commit message

Example prompts

  • “/create-commit”

Workflow steps

5 steps, taken from the first numbered list in SKILL.md.

  1. What was wrong before. State the old behaviour concretely, with the values or
  2. Why the obvious fix doesn't work. If you hit a trap that cost you time, record
  3. Non-obvious constraints that shaped the approach — a platform limit, an
  4. Misleading diffs. If a file's line count overstates the real change
  5. Collateral fixes and why they were needed — e.g. a test that was stale for an

What it can do on your machine

Read from SKILL.md and the folder at commit 172b47c. It shows what the files ask for, not the result of running them.

  • Tool permissions

    Pre-approves nothing: there is no allowed-tools line, so your agent's usual permission prompts apply.

    From allowed-tools in the SKILL.md frontmatter.

  • Runs code

    Shell commands in SKILL.md call:

    • git

    From the folder's file list and the shell code blocks in SKILL.md.

  • Network

    No URLs in SKILL.md. Its commands use git, which can reach the network depending on how they are called.

    From URLs in SKILL.md, links to its own repository left out.

  • Credentials

    Names no API keys, tokens, secrets or passwords.

    From names ending in _API_KEY, _TOKEN, _SECRET, _KEY or _PASSWORD in SKILL.md.

Context cost

Create Commit loads about 1.2k tokens when it runs. Until then it costs about 126 tokens; SKILL.md has 680 words of instructions outside code blocks.

Always · name and description, kept in context so the agent knows when to use it
~126
When it runs · the whole SKILL.md, loaded when a task matches
~1.2k

Estimates: characters ÷ 4, the usual rule of thumb; real counts depend on the model's tokenizer. Scripts and assets cost tokens only if the agent reads them.

Safety

Auto-check passed

The automated check found no risky patterns in SKILL.md.

Automated static check — not a guarantee. Review scripts before installing. It scans the text of SKILL.md for risky patterns (piping downloads into a shell, reading credential files, hidden Unicode, destructive commands); files beside SKILL.md are not scanned.

SKILL.md

The full file from TwiTech-LAB/devchain at commit 172b47c, republished under its MIT licence (© TwiTech-LAB). 680 words, ~1,193 tokens.

Download SKILL.mdSave it as .claude/skills/create-commit/SKILL.md (or your agent's skills folder).
name
create-commit
description
Create a git commit whose message records why the change exists, not just what changed. Keeps one logical change per commit, stages only the files that belong to it, matches the repo's existing commit style, keeps the body to decisions and traps rather than implementation, and shows the message and staged files for user approval before committing. Use when asked to commit work or write a commit message. Triggers: create a commit, commit this, commit the changes, write a commit message.
displayName
Create Commit
version
0.2.0
license
MIT

Create Commit

Create a commit for the work done. Your commit message is the only durable record of why this change exists. The diff already says what changed. If you only restate the diff, the reasoning dies with your session.

One logical change per commit

  • A commit contains one change a reviewer can accept or revert as a unit. If the working tree holds two independent changes (a feature and an unrelated fix, code and a skill edit), make two commits.
  • A feature and the cleanup pass that reshaped it before anyone saw it are one change. A cleanup of code that already landed is its own commit.
  • Use git add -p when one file mixes both.

Subject line

  • Conventional prefix + scope, matching this repo's existing style — run git log --oneline -15 and match what you see, don't impose a new convention.
  • Imperative mood, 50 characters as the target, 72 as the hard limit, no trailing period.
  • Describe the change in the reader's terms, not the file's: "render event pulses as glowing dots", not "update AgentEventBus.tsx".
  • A change that breaks an existing contract (API, schema, stored format, CLI flag) adds ! after the scope and a BREAKING CHANGE: footer that says what breaks and what to do about it.

Body — spend your context here

Wrap at 72 chars. Blank line after the subject. Cover, in rough priority order:

  1. What was wrong before. State the old behaviour concretely, with the values or paths that made it wrong.
  2. Why the obvious fix doesn't work. If you hit a trap that cost you time, record it. The next person will otherwise hit it too. This is the highest value content in the message.
  3. Non-obvious constraints that shaped the approach — a platform limit, an invariant, a rule you had to work around.
  4. Misleading diffs. If a file's line count overstates the real change (autoformatting, reindentation, generated output), say so and say what the real change is. This saves a reviewer from hunting.
  5. Collateral fixes and why they were needed — e.g. a test that was stale for an unrelated reason you discovered while working.
Length
  • A paragraph earns its place only if it records a decision the diff cannot show, or a trap. A paragraph that describes what the code now does is the diff in prose; delete it.
  • Most bodies fit in three to twelve lines. A body past twenty lines usually contains implementation narration; re-read it against the rule above.
  • A trivial change (a version bump, a typo, a renamed constant) needs no body. The subject alone is the message: chore(templates): bump version.
  • The plan, the epic, and the review already hold the full design. The commit records what a reader of git log cannot get elsewhere.
Show full SKILL.md (222 more words)Show less

Never

  • Never invent rationale. If you did not do the work and cannot recover the "why" from the diff, prior commits, code comments, or the linked task, then either ask, or write only what you can verify. Plausible-sounding invented reasoning is worse than none.
  • Never claim verification you didn't run. Don't write "all tests pass" unless you ran them and saw them pass.
  • No marketing language, no adjectives like "robust" / "improved" / "comprehensive". State the mechanism, let the reader judge.
  • No process narration. "First I tried X, then Y" belongs nowhere. State the resulting facts.
  • No filler trailers unless this repo actually uses them.

Scope discipline

  • Commit only files belonging to this change. If the working tree contains unrelated work (common in shared worktrees), stage selectively, leave the rest, and say in your report what you left and why.
  • Before staging a file with a suspiciously large diff, check git diff -w to confirm what's actually semantic.
  • Don't push unless asked.
  • Never use --no-verify or skip hooks.

Before committing

  • Re-read your own message and delete every sentence that only restates the diff. What remains is the message.
  • Show the user the final message and the list of files you staged, then stop and wait. Commit only after the user approves. If the user asks for changes, update the message and show it again.

© TwiTech-LAB, MIT. Rendered from Markdown: HTML in the file is shown as text, images as links, and headings moved down two levels. Raw file

Files

Just SKILL.md in apps/local-app/skills/create-commit of TwiTech-LAB/devchain.

Open the folder on GitHubat commit 172b47c

Compare with similar skills

Create Commit next to the 5 skills that share the most tags, products or categories with it. Stars are the repository's; “used in” counts other GitHub owners with a copy.

Create Commit compared with similar skills
SkillStarsUsed inTokensAuto-checkLicenceRepo updated
Create Commit this skillTwiTech-LAB/devchain101—~1.2kAutomated safety check: PassMIT
Contextual Commit Messagesyamadashy/repomix29k1 repos~2.7kAutomated safety check: PassMIT
React Router Release Notes Prepremix-run/react-router57k—~1.1kAutomated safety check: PassMIT
PR Finalize Reviewmicrosoft/garnet12k—~3.1kAutomated safety check: PassMIT
Caveman Commitvishiri/fantasia-archive40913 repos~642Automated safety check: PassGPL-3.0
ToolJet Multi-Repo CommitToolJet/ToolJet41k—~1.3kAutomated safety check: PassAGPL-3.0

Similar skills

  • Contextual Commit Messages

    yamadashy/repomix

    Writes Conventional Commits whose bodies carry action lines recording the intent, decisions and constraints behind a change, not only what changed.

    29k GitHub starsUsed in 1 repo~2.7k tokens
    DevelopmentAuto-check passed

  • React Router Release Notes Prep

    remix-run/react-router

    Polishes pending React Router change files before the versioning scripts run, and decides whether a long-form What's Changed section is warranted.

    57k GitHub stars~1.1k tokensUpdated yesterday
    DevelopmentAuto-check passed

  • PR Finalize Review

    microsoft/garnet

    Official

    Checks that a pull request's title and description match its implementation and reviews the code for Garnet best practices, reporting findings without posting them.

    12k GitHub stars~3.1k tokensUpdated today
    DevelopmentAuto-check passed

  • Caveman Commit

    vishiri/fantasia-archive

    Ultra-compressed commit message generator. An agent skill from vishiri/fantasia-archive.

    409 GitHub starsUsed in 13 repos~642 tokens
    DevelopmentAuto-check passed

  • ToolJet Multi-Repo Commit

    ToolJet/ToolJet

    Commits changes across ToolJet's root repo and its server/ee and frontend/ee submodules, writing messages from the diffs and updating submodule pointers in order.

    41k GitHub stars~1.3k tokensUpdated today
    DevelopmentAuto-check passed

  • Git Workflow and Versioning

    addyosmani/agent-skills

    Sets git habits for every change: short-lived branches, atomic commits with descriptive messages, clean pull requests, plus versioning, tagging and changelogs for releases.

    102k GitHub starsUsed in 2 repos~3.5k tokens
    DevelopmentAuto-check: notes

More from TwiTech-LAB/devchain

  • Asd Ste100 Skill

    TwiTech-LAB/devchain

    Write or rewrite English with ASD-STE100 Simplified Technical English rules: one meaning per word, active voice, simple tenses, one instruction per sentence.

    101 GitHub stars~1.2k tokensUpdated today
    Auto-check passed

  • Vm Provisioning

    TwiTech-LAB/devchain

    Prepare a DevChain remote VM for development of a project. An agent skill from TwiTech-LAB/devchain.

    101 GitHub stars~1.8k tokensUpdated today
    Auto-check: notes

  • Code Simplifier

    TwiTech-LAB/devchain

    Review a change set for reuse, simplification, efficiency, and altitude problems, then apply the fixes while preserving exact behavior.

    101 GitHub stars~2k tokensUpdated today
    Auto-check passed

  • Improve Codebase Architecture

    TwiTech-LAB/devchain

    Plan architecture improvements and refactoring for a codebase: scan for deepening opportunities (shallow modules, leaky seams, low-leverage interfaces), present candidates as a markdown report with…

    101 GitHub stars~3k tokensUpdated today
    Auto-check passed

  • Project Skill Review

    TwiTech-LAB/devchain

    Review the skills stored for a project. An agent skill from TwiTech-LAB/devchain.

    101 GitHub stars~2k tokensUpdated today
    Auto-check passed

Categories

Questions about Create Commit

What does Create Commit do?

Create a git commit whose message records why the change exists, not just what changed. Create Commit is an agent skill from TwiTech-LAB/devchain. Create a git commit whose message records why the change exists, not just what changed.

When should I use Create Commit?

Create Commit fits situations like: asked to commit work; write a commit message.

How do I install Create Commit in Claude Code?

Run `npx skills add TwiTech-LAB/devchain --skill create-commit -a claude-code`. Or copy the skill folder (apps/local-app/skills/create-commit in TwiTech-LAB/devchain) into .claude/skills/create-commit in your project. Claude Code loads it when a task matches its description.

How do I install Create Commit in Codex?

Run `npx skills add TwiTech-LAB/devchain --skill create-commit -a codex`. Or copy the skill folder (apps/local-app/skills/create-commit in TwiTech-LAB/devchain) into .agents/skills/create-commit in your project. Codex loads it when a task matches its description.

Can I use Create Commit in Cursor, Gemini CLI or GitHub Copilot?

Cursor, Gemini CLI, GitHub Copilot and OpenCode also load SKILL.md folders. With the skills CLI, run `npx skills add TwiTech-LAB/devchain --skill create-commit -a cursor` (or -a gemini-cli, github-copilot or opencode for the others). To copy it by hand, put the folder in .cursor/skills/create-commit, .gemini/skills/create-commit, .github/skills/create-commit and .opencode/skills/create-commit in your project.

What does Create Commit need to run?

Going by SKILL.md and its folder, Create Commit needs the command-line tools its instructions call (git).

Does Create Commit access the network?

SKILL.md contains no URLs. Its commands use git, which can reach the network depending on how they are called. This is read from the text; nothing was executed.

Is Create Commit safe to install?

Our automated static check of SKILL.md found no risky patterns, such as piping downloads into a shell, reading credential files or hidden Unicode. It is not a guarantee. Review the folder before installing.

What licence does Create Commit use?

Create Commit is published under the MIT licence (declared in SKILL.md). It allows redistribution, so the full SKILL.md is shown on this page.

How many tokens does Create Commit use?

About 1.2k tokens (SKILL.md is roughly 4.8k characters). Agents keep only the skill's name and description in context until a task matches; then they load SKILL.md in full.

What are the alternatives to Create Commit?

Skills that share tags, products or a category with Create Commit: Contextual Commit Messages (yamadashy/repomix, 29k stars), React Router Release Notes Prep (remix-run/react-router, 57k stars), PR Finalize Review (microsoft/garnet, 12k stars) and Caveman Commit (vishiri/fantasia-archive, 409 stars). The comparison table on this page puts their stars, adoption, token cost, safety result and licence side by side.

Who maintains Create Commit?

TwiTech-LAB (a GitHub organization) maintains it in TwiTech-LAB/devchain, which has 101 GitHub stars. The repository holds 6 skills in this directory. The repository was last updated on October 7, 2026.

Source: TwiTech-LAB/devchain on GitHub. Facts on this page come from the repository at the commit we read; the author's words are quoted as theirs.