Writing Commits
Create an authorized git commit or draft its message, grounded in the intended diff and repository conventions. Message-only requests never commit; commit requests do not imply push or merge.
Install
/plugin marketplace add borkweb/skillsThe repo is a Claude Code plugin marketplace. Run /plugin afterwards to pick the plugin that includes this skill.
npx skills add borkweb/skills --skill writing-commitsgit clone --depth 1 https://github.com/borkweb/skills.git /tmp/skills
mkdir -p ~/.claude/skills
cp -r /tmp/skills/skills/core/writing-commits ~/.claude/skills/writing-commitsPersonal skills live in ~/.claude/skills. Use .claude/skills in a project folder to share a skill with your team.
From the SKILL.md
# Commit Message Writer You write succinct, accurate git commit messages in plain language. Help future developers understand the theme, outcome, and reason for a change without narrating the diff. ## How to analyze changes Run these in one call to understand what you're working with; the log format shows recent bodies, so no second `git log` or `git show` is needed for style: ```bash git status --short; git diff --staged; git diff; git log -5 --format='%h %s%n%b---' ``` Read the diff carefully. Understand the *intent* behind the changes — not just which lines moved, but what problem they solve or what capability they add. If the diff is large or touches unfamiliar code, use `Read` or `Grep` to look at surrounding context. Check `git log` output closely. If the repo uses a specific convention (emoji prefixes, Jira ticket format, lowercase subjects, Angular-style), match it. Repository convention wins over the defaults below, except the no-attribution rule, which applies even when earlier commits carry AI trailers. ## Write for understanding Summarize the change; do not replay it. A useful commit message tells the reader what is now possible, what no longer goes wrong, or why the code is easier to work with. - Lead with the outcome or shared theme. Group related edits into one idea instead of listing files, functions, or code actions.
Details
- Skill name
writing-commits- Repository
- borkweb/skills
- Path
skills/core/writing-commits/SKILL.md- License
- MIT
- Repo updated
- 18 November 2026
FAQ
What does the Writing Commits skill do?
Create an authorized git commit or draft its message, grounded in the intended diff and repository conventions. Message-only requests never commit; commit requests do not imply push or merge.
How do I install the Writing Commits skill?
Claude Code plugin: /plugin marketplace add borkweb/skills. Skills go in ~/.claude/skills (personal) or .claude/skills (project), and Claude loads them automatically when a task matches the description.
Is Writing Commits popular?
It lives in borkweb/skills, which has 9 GitHub stars and 0 forks.
Related skills
Prototype
9borkweb/skills
Build a throwaway prototype to flesh out a design before committing to it. Routes between two branches — a runnable terminal app for state/business-logic questions, or several radically different UI variations toggleable from one route. Use when the user wants to prototype, sanity-check a data model or state machine, mock up a UI, explore design options, or says "prototype this", "let me play with it", "try a few designs".
Agents Md Lint
9borkweb/skills
Audit and trim AI agent instruction files (AGENTS.md, CLAUDE.md, CONVENTIONS.md, .cursorrules, etc.) by testing which facts an AI agent can discover from code alone. Use when asked to lint, audit, optimize, prune, or trim any agent instruction file in a repository. Removes redundant documentation that wastes context tokens. Supports a dry-run mode that reports findings without modifying files.
Auto Scope
9borkweb/skills
Scopes a coding task before implementation — names the handful of files actually relevant (read/edit these), the areas to leave alone, and any open scope questions, so work doesn't start by reading the whole repo. Fires proactively at the start of substantive, multi-file, or unfamiliar-area work; stays silent on single-file edits, one-line fixes, questions, and continued work in an area already scoped this session. Use when beginning a feature, bug fix, or refactor that could plausibly touch several files or an area not yet seen this session.
Writing Plan Documents
9borkweb/skills
Use when writing any plan document or product spec — project plans, PRDs, product specs, proposals, implementation plans, or design docs. Applies ASD-STE100 Simplified Technical English as a writing style layer alongside other planning skills like superpowers:writing-plans.
Layman
9borkweb/skills
Restate existing content in plain English when asked for layman, plain language or no jargon. One-shot unless the user enables sticky mode; never edits files.
Adhx
9huytran1120/vietnam-agentic-skills
Fetch any X/Twitter post as clean LLM-friendly JSON. Converts x.com, twitter.com, or adhx.com links into structured data with full article content, author info, and engagement metrics. No scraping or browser required.
Browse the most popular Claude skills, all writing & content skills, or write your own with the skills generator.