How do I install the Ape Commit skill?

Run npx skillmds@latest add arpitbbhayani/ape-commit in your terminal (requires Node.js), paste this page's agent-chat prompt into Claude, Cursor, or any MCP-connected agent, or download the SKILL.md file and copy it into your agent's skills directory.

Is Ape Commit safe to use?

This skill has not completed SkillMD's automated safety review yet. SkillMD never runs a skill's scripts for you; review the SKILL.md before installing.

Which AI agents work with Ape Commit?

This skill is tagged as working with Claude Code, Claude.ai, OpenAI Codex. SKILL.md is an open format, so most agents that read a skills directory can load it too.

Is Ape Commit free to use?

Yes. Installing skills from SkillMD is free, and the skill stays under its author's original license.

Who published Ape Commit?

arpitbbhayani (@arpitbbhayani) published this skill. Their other Agent Skills are listed on their SkillMD profile.

Ape Commit by arpitbbhayani — Agent Skill

Name: Ape Commit
Author: arpitbbhayani

Ape Commit

Defines how to write and format git commit messages. Use this skill whenever the user asks you to write, draft, suggest, or format a git commit message, summarize changes into a commit, or help stage and describe code changes. Trigger even for casual requests like "write me a commit for this" or "what should my commit say".

File contents

Commit Message Style

Format

<short summary line>

- <change>
- <change>
- <change>

Rules

Summary line (first line)

One line only
Short and crisp -- aim for under 72 characters
Use the imperative mood: "Add feature" not "Added feature" or "Adds feature"
No trailing period
Describe what the commit does, not how

Blank lines

Always exactly one blank line between the summary line and the bullet list (never omit it)
No blank lines between bullet list items -- the list must be tight and contiguous (single newline after each item, never an empty/blank line)
No trailing blank lines at the end of the commit message

Bullet points

Each bullet describes a single, specific change
Short and crisp -- one line per bullet
Keep bullet items contiguous with no blank lines between them
Start each bullet with a verb in the imperative mood (Add, Fix, Remove, Update, Rename, Move, Extract, etc.)
No trailing periods
No fluff or filler words

Never include

Blank lines between bullet list items (loose lists)
Co-author lines (no Co-authored-by: trailer)
Generated by Claude or any AI attribution
Redundant context already obvious from the diff

Examples

Good:

Add user authentication middleware

- Add JWT validation to protected routes
- Return 401 on missing or expired token
- Extract auth logic into separate middleware file
- Add unit tests for token validation

Fix null pointer crash on empty cart checkout

- Guard against null items array before totalling
- Add early return when cart has no items
- Log warning when checkout attempted on empty cart

Bad (do not do this):

Updated some stuff and fixed a few things that were broken and also added
some new features to the codebase

- I made some changes to the auth file because it was crashing

- Also fixed the cart thing
- Co-authored-by: Claude <noreply@anthropic.com>

---name: ape-commitdescription: Defines how to write and format git commit messages. Use this skill whenever the user asks you to write, draft, suggest, or format a git commit message, summarize changes into a commit, or help stage and describe code changes. Trigger even for casual requests like "write me a commit for this" or "what should my commit say".---# Commit Message Style## Format```<short summary line>- <change>- <change>- <change>```## Rules### Summary line (first line)- One line only- Short and crisp -- aim for under 72 characters- Use the imperative mood: "Add feature" not "Added feature" or "Adds feature"- No trailing period- Describe *what* the commit does, not *how*### Blank lines- Always exactly one blank line between the summary line and the bullet list (never omit it)- No blank lines between bullet list items -- the list must be tight and contiguous (single newline after each item, never an empty/blank line)- No trailing blank lines at the end of the commit message### Bullet points- Each bullet describes a single, specific change- Short and crisp -- one line per bullet- Keep bullet items contiguous with no blank lines between them- Start each bullet with a verb in the imperative mood (Add, Fix, Remove, Update, Rename, Move, Extract, etc.)- No trailing periods- No fluff or filler words### Never include- Blank lines between bullet list items (loose lists)- Co-author lines (no `Co-authored-by:` trailer)- `Generated by Claude` or any AI attribution- Redundant context already obvious from the diff## Examples**Good:**```Add user authentication middleware- Add JWT validation to protected routes- Return 401 on missing or expired token- Extract auth logic into separate middleware file- Add unit tests for token validation``````Fix null pointer crash on empty cart checkout- Guard against null items array before totalling- Add early return when cart has no items- Log warning when checkout attempted on empty cart```**Bad (do not do this):**```Updated some stuff and fixed a few things that were broken and also addedsome new features to the codebase- I made some changes to the auth file because it was crashing- Also fixed the cart thing- Co-authored-by: Claude <noreply@anthropic.com>```

Frequently asked questions