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.
Writes Git commit messages. An agent skill from dancinlab/void.
Install Writing Commit Messages
$ npx skills add dancinlab/void --skill writing-commit-messages -a claude-codeProject install by default; add -g for ~/.claude/skills/.
$ gh skill install dancinlab/void writing-commit-messages --agent claude-codeProject scope by default; add --scope user for a personal install. Needs GitHub CLI 2.90.0 or later (public preview).
$ git clone --depth 1 https://github.com/dancinlab/void.git skills-src && mkdir -p .claude/skills && cp -r skills-src/.agents/skills/writing-commit-messages .claude/skills/writing-commit-messages && rm -rf skills-srcUse ~/.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/
Install the "writing-commit-messages" agent skill from https://github.com/dancinlab/void/tree/void%2Fmain/.agents/skills/writing-commit-messages into .claude/skills/writing-commit-messages/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "writing-commit-messages", then confirm the skill loads.Claude Code copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
$skill-installer install https://github.com/dancinlab/void/tree/void%2Fmain/.agents/skills/writing-commit-messagesType this inside Codex. $skill-installer <name> installs a curated skill from openai/skills. The installer writes to $CODEX_HOME/skills (default ~/.codex/skills). Restart Codex if the skill does not show up.
$ npx skills add dancinlab/void --skill writing-commit-messages -a codexProject install goes to .agents/skills/; add -g for ~/.codex/skills/.
$ gh skill install dancinlab/void writing-commit-messages --agent codexProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/dancinlab/void.git skills-src && mkdir -p .agents/skills && cp -r skills-src/.agents/skills/writing-commit-messages .agents/skills/writing-commit-messages && rm -rf skills-srcUse ~/.agents/skills/ instead of .agents/skills for a personal install.
Codex skills documentation · loads skills from .agents/skills/
Install the "writing-commit-messages" agent skill from https://github.com/dancinlab/void/tree/void%2Fmain/.agents/skills/writing-commit-messages into .agents/skills/writing-commit-messages/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "writing-commit-messages", then confirm the skill loads.Codex copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
$ npx skills add dancinlab/void --skill writing-commit-messages -a cursorProject install goes to .agents/skills/; add -g for ~/.cursor/skills/.
$ gh skill install dancinlab/void writing-commit-messages --agent cursorProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/dancinlab/void.git skills-src && mkdir -p .cursor/skills && cp -r skills-src/.agents/skills/writing-commit-messages .cursor/skills/writing-commit-messages && rm -rf skills-srcUse ~/.cursor/skills/ instead of .cursor/skills for a personal install.
Cursor skills documentation · loads skills from .cursor/skills/, .agents/skills/, .claude/skills/, .codex/skills/
Install the "writing-commit-messages" agent skill from https://github.com/dancinlab/void/tree/void%2Fmain/.agents/skills/writing-commit-messages into .cursor/skills/writing-commit-messages/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "writing-commit-messages", then confirm the skill loads.Cursor copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
$ gemini skills install https://github.com/dancinlab/void.git --path .agents/skills/writing-commit-messages--scope user (default) or --scope workspace; --path is the subfolder of the repo that holds the skill; --consent skips the security confirmation prompt.
$ npx skills add dancinlab/void --skill writing-commit-messages -a gemini-cliProject install goes to .agents/skills/; add -g for ~/.gemini/skills/.
$ gh skill install dancinlab/void writing-commit-messages --agent gemini-cliProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/dancinlab/void.git skills-src && mkdir -p .gemini/skills && cp -r skills-src/.agents/skills/writing-commit-messages .gemini/skills/writing-commit-messages && rm -rf skills-srcUse ~/.gemini/skills/ instead of .gemini/skills for a personal install, then run /skills reload.
Gemini CLI skills documentation · loads skills from .gemini/skills/, .agents/skills/
Install the "writing-commit-messages" agent skill from https://github.com/dancinlab/void/tree/void%2Fmain/.agents/skills/writing-commit-messages into .gemini/skills/writing-commit-messages/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "writing-commit-messages", then confirm the skill loads.Gemini CLI copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
$ gh skill install dancinlab/void writing-commit-messagesInstalls for Copilot at project scope by default; add --scope user for a personal install. Preview a skill first with gh skill preview. Needs GitHub CLI 2.90.0 or later (public preview).
$ npx skills add dancinlab/void --skill writing-commit-messages -a github-copilotProject install goes to .agents/skills/; add -g for ~/.copilot/skills/.
$ git clone --depth 1 https://github.com/dancinlab/void.git skills-src && mkdir -p .github/skills && cp -r skills-src/.agents/skills/writing-commit-messages .github/skills/writing-commit-messages && rm -rf skills-srcUse ~/.copilot/skills/ instead of .github/skills for a personal install. Commit .github/skills so cloud agent and code review can use it.
GitHub Copilot skills documentation · loads skills from .github/skills/, .claude/skills/, .agents/skills/
Install the "writing-commit-messages" agent skill from https://github.com/dancinlab/void/tree/void%2Fmain/.agents/skills/writing-commit-messages into .github/skills/writing-commit-messages/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "writing-commit-messages", then confirm the skill loads.GitHub Copilot copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
$ npx skills add dancinlab/void --skill writing-commit-messages -a opencodeOpenCode documents no install command of its own. Project install goes to .agents/skills/; add -g for ~/.config/opencode/skills/.
$ gh skill install dancinlab/void writing-commit-messages --agent opencodeProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/dancinlab/void.git skills-src && mkdir -p .opencode/skills && cp -r skills-src/.agents/skills/writing-commit-messages .opencode/skills/writing-commit-messages && rm -rf skills-srcUse ~/.config/opencode/skills/ instead of .opencode/skills for a personal install.
OpenCode skills documentation · loads skills from .opencode/skills/, .claude/skills/, .agents/skills/
Install the "writing-commit-messages" agent skill from https://github.com/dancinlab/void/tree/void%2Fmain/.agents/skills/writing-commit-messages into .opencode/skills/writing-commit-messages/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "writing-commit-messages", then confirm the skill loads.OpenCode copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
Facts
- Skill name
writing-commit-messages- GitHub stars
- 117
- Token cost
- ~503 tokens
- SKILL.md length
- 264 words
- Files
- 1
- Skills in repo
- 1
- Repo updated
- First seen
- Licence
- MIT
At a glance
Writes Git commit messages. An agent skill from dancinlab/void.
- Asks to write a commit message
- SKILL.md covers Format, Rules and Workflow
- Instructions only: no scripts, shell commands, URLs or credentials in SKILL.md
- Draft a commit message
What it does
Writing Commit Messages is an agent skill from dancinlab/void. Writes Git commit messages. Activates when the user asks to write a commit message, draft a commit message, or similar.
Its SKILL.md is about 500 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: 🕳️ VOID — Terminal emulator written in hexa-lang. The licence is MIT.
When your agent uses it
- Asks to write a commit message
- Draft a commit message
Example prompts
- “Use the writing-commit-messages skill to write Git commit messages. An agent skill from dancinlab/void”
- “/writing-commit-messages”
What it can do on your machine
Read from SKILL.md and the folder at commit 59b0bee. 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
No scripts in the folder and no shell commands in SKILL.md.
From the folder's file list and the shell code blocks in SKILL.md.
Network
No URLs in SKILL.md.
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
Writing Commit Messages loads about 503 tokens when it runs. Until then it costs about 36 tokens; SKILL.md has 264 words of instructions outside code blocks.
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 dancinlab/void at commit 59b0bee, republished under its MIT licence (© dancinlab). 264 words, ~503 tokens.
Download SKILL.mdSave it as
.claude/skills/writing-commit-messages/SKILL.md (or your agent's skills folder).- name
- writing-commit-messages
- description
- Writes Git commit messages. Activates when the user asks to write a commit message, draft a commit message, or similar.
Writing Commit Messages
Write commit messages that follow commit style guidelines for the project.
Format
<subsystem>: <summary>
<reference issues/PRs/etc.>
<long form description>Rules
Subject line
- Subsystem prefix: Use a short, lowercase identifier for the
area of code changed (e.g.,
terminal,vt,lib,config,font). Determine this from the file paths in the diff. If changes span the macOS app, usemacos. For GTK, usegtk. For build system, usebuild. Use nested subsystems with/when helpful and exclusive (e.g.,terminal/osc). - Summary: Lowercase start (not capitalized), imperative mood, no trailing period. Keep it concise—ideally under 60 characters total for the whole subject line.
References
- If the change relates to a GitHub issue, PR, or discussion, list
the relevant numbers on their own lines after the subject, separated
by a blank line. E.g.
#1234 - If there are no references, omit this section entirely (no blank line).
Long form description
- Describe what changed, what the previous behavior was, and how the new behavior works at a high level.
- Use plain prose, not bullet points. Wrap lines at ~72 characters.
- Focus on the why and how rather than restating the diff.
- Keep the tone direct and technical without no filler phrases.
- Don't exceed a handful of paragraphs; less is more.
Workflow
- If
.jjis present, usejjinstead ofgitfor all commands. - Run a diff to see what changes are present since the last commit.
- Identify the subsystem from the changed file paths.
- Identify any referenced issues/PRs from the diff context or branch name.
- Draft the commit message following the format above.
- Apply the commit
- Don't push the commit; leave that to the user.
© dancinlab, 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 .agents/skills/writing-commit-messages of dancinlab/void.
Open the folder on GitHubat commit 59b0bee
Compare with similar skills
Writing Commit Messages 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.
| Skill | Stars | Used in | Tokens | Auto-check | Licence | Repo updated |
|---|---|---|---|---|---|---|
| Writing Commit Messages this skilldancinlab/void | 117 | — | ~503 | Automated safety check: Pass | MIT | |
| Contextual Commit Messagesyamadashy/repomix | 29k | 1 repos | ~2.7k | Automated safety check: Pass | MIT | |
| React Router Release Notes Prepremix-run/react-router | 57k | — | ~1.1k | Automated safety check: Pass | MIT | |
| Caveman Commitvishiri/fantasia-archive | 409 | 13 repos | ~642 | Automated safety check: Pass | GPL-3.0 | |
| PR Finalize Reviewmicrosoft/garnet | 12k | — | ~3.1k | Automated safety check: Pass | MIT | |
| ToolJet Multi-Repo CommitToolJet/ToolJet | 41k | — | ~1.3k | Automated safety check: Pass | AGPL-3.0 |
Similar skills
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.
Caveman Commit
vishiri/fantasia-archive
Ultra-compressed commit message generator. An agent skill from vishiri/fantasia-archive.
- Official
PR Finalize Review
microsoft/garnet
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.
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.
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.
Related
Categories
Questions about Writing Commit Messages
What does Writing Commit Messages do?
Writes Git commit messages. An agent skill from dancinlab/void. Writing Commit Messages is an agent skill from dancinlab/void. Writes Git commit messages.
When should I use Writing Commit Messages?
Writing Commit Messages fits situations like: asks to write a commit message; draft a commit message.
How do I install Writing Commit Messages in Claude Code?
Run `npx skills add dancinlab/void --skill writing-commit-messages -a claude-code`. Or copy the skill folder (.agents/skills/writing-commit-messages in dancinlab/void) into .claude/skills/writing-commit-messages in your project. Claude Code loads it when a task matches its description.
How do I install Writing Commit Messages in Codex?
Run `npx skills add dancinlab/void --skill writing-commit-messages -a codex`. Or copy the skill folder (.agents/skills/writing-commit-messages in dancinlab/void) into .agents/skills/writing-commit-messages in your project. Codex loads it when a task matches its description.
Can I use Writing Commit Messages 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 dancinlab/void --skill writing-commit-messages -a cursor` (or -a gemini-cli, github-copilot or opencode for the others). To copy it by hand, put the folder in .cursor/skills/writing-commit-messages, .gemini/skills/writing-commit-messages, .github/skills/writing-commit-messages and .opencode/skills/writing-commit-messages in your project.
What does Writing Commit Messages need to run?
SKILL.md names no scripts, command-line tools or credentials: Writing Commit Messages is instructions for the agent only.
Does Writing Commit Messages access the network?
SKILL.md contains no URLs. Any network use would come from the scripts or tools the agent runs. This is read from the text; nothing was executed.
Is Writing Commit Messages 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 Writing Commit Messages use?
Writing Commit Messages is published under the MIT licence (the repository's licence). It allows redistribution, so the full SKILL.md is shown on this page.
How many tokens does Writing Commit Messages use?
About 503 tokens (SKILL.md is roughly 2k 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 Writing Commit Messages?
Skills that share tags, products or a category with Writing Commit Messages: Contextual Commit Messages (yamadashy/repomix, 29k stars), React Router Release Notes Prep (remix-run/react-router, 57k stars), Caveman Commit (vishiri/fantasia-archive, 409 stars) and PR Finalize Review (microsoft/garnet, 12k stars). The comparison table on this page puts their stars, adoption, token cost, safety result and licence side by side.
Who maintains Writing Commit Messages?
dancinlab (a GitHub organization) maintains it in dancinlab/void, which has 117 GitHub stars. The repository was last updated on July 31, 2026.
Source: dancinlab/void on GitHub. Facts on this page come from the repository at the commit we read; the author's words are quoted as theirs.