Committing code

Skill oryanmoshe/agent-skills/skills/committing-code

Battle-tested skills for disciplined AI-assisted development. Task tracking, code review, parallel exploration, and more.

Install

npx -y skills add oryanmoshe/agent-skills --skill committing-code

Assembled from the repository path, not quoted from the project. Check it against their README if it does not work.

2 things to look at

no licenseNo license file was found in the repository. Code published without one is not open source by default, so using it at work is a question for whoever answers licensing questions where you are.
2 stars2 stars. Stars are a popularity signal and not a quality one, but at this level it is likely that nobody has read this closely except its author, and you would be relying on your own review.

What its author says it does

Copied from the file, not written here

Writes git commit messages using conventional commits format with gitmoji. Use when creating git commits, preparing commit messages, or when the user asks to commit changes. Triggers on "commit", "git commit", "save changes", or any request to record changes to version control.

SKILL.md

3.7 KB, 885 tokens by cl100k_base, as published. Nobody here has run it

Committing Code

Overview

Every commit message uses conventional commits with gitmoji. The format is consistent, scannable, and conveys intent at a glance.

Format

<emoji> <type>: <short description>

<body — what changed and why>

Co-Authored-By: Claude <agent> <[email protected]>

The short description is imperative mood, lowercase, no period. The body uses bullet points for multiple changes.

Gitmoji Reference

Emoji	Type	When to use
🎉	`feat`	Initial commit / first commit in a repo
✨	`feat`	New feature or capability
🐛	`fix`	Bug fix
♻️	`refactor`	Code restructuring without behavior change
📝	`docs`	Documentation only
🔧	`chore`	Config, tooling, non-code changes
✅	`test`	Adding or updating tests
🚀	`perf`	Performance improvement
🔥	`chore`	Removing code or files
🏗️	`refactor`	Architectural change
💄	`style`	UI/cosmetic change
🔒	`security`	Security fix
⬆️	`chore`	Dependency upgrade
🚚	`refactor`	Moving or renaming files

Examples

Good:

✨ feat: add user authentication with JWT

- Add login/logout endpoints in auth.controller.ts
- Add JWT middleware for protected routes
- Add refresh token rotation
- Add auth integration tests

Co-Authored-By: Claude Opus 4.5 <[email protected]>

🐛 fix: prevent race condition in websocket reconnect

The reconnect logic was firing multiple times when the connection
dropped during a message send, causing duplicate subscriptions.
Added a mutex guard around the reconnect path.

Co-Authored-By: Claude Opus 4.5 <[email protected]>

♻️ refactor: rename getUserById to fetchUser across codebase

Aligns with the fetch* naming convention for async data access.
Updated all call sites, tests, and type definitions.

Co-Authored-By: Claude Opus 4.5 <[email protected]>

Bad:

updated stuff          # No type, no emoji, vague
feat: Add Feature      # No emoji, capitalized
✨ feat: add feature.  # Trailing period
🐛✨ fix/feat: stuff   # Multiple types

Rules

One type per commit. If changes span multiple types, split into multiple commits.
Body explains WHY, not just WHAT. The diff shows what changed — the message explains the reasoning.
Use bullet points in the body when listing multiple changes.
Always include Co-Authored-By when the commit was AI-assisted.

Use HEREDOC for multi-line messages to preserve formatting:

git commit -m "$(cat <<'EOF'
✨ feat: add new feature

Body text here.

Co-Authored-By: Claude Opus 4.5 <[email protected]>
EOF
)"

Commit Frequency

Commit early and often:

After each logical unit of work (one feature, one fix, one refactor)
After adding a new file or skill
After updating documentation alongside code changes
Never batch unrelated changes into a single commit

Pre-Commit Checklist

Before committing, verify:

README.md is updated if the change affects user-facing documentation (new features, skills, APIs, installation steps)
AGENTS.md is updated if the change affects project structure, conventions, or available skills
Documentation changes are part of the same commit as the code they describe — not a separate "docs" commit after the fact