commit

Creates conventional git commits with staged file review and co-author attribution.

4|Updated Jul 30, 2026
One-click install
npx skills add https://github.com/gabriellst/codm --skill commit-gabriellst
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: commit
Source: https://github.com/gabriellst/codm/tree/main/.claude/skills/commit
Command: npx skills add https://github.com/gabriellst/codm --skill commit-gabriellst

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve? Writing consistent, well-formatted git commit messages is easy to get wrong: vague subjects, missing context, accidentally staged secrets, and inconsistent conventions. This Skill standardizes the entire commit workflow so every commit follows conventional commit formatting with proper staging hygiene and co-author attribution. ## Core Features & Use Cases - Conventional Commit Formatting: Enforces type prefixes (feat, fix, refactor, docs, style, test, chore), imperative mood subjects under 50 characters, and body wrapping at 72 characters. - Smart Staging Guidance: Stages specific files or directories while avoiding git add . to prevent committing secrets, node_modules, or build artifacts. - Co-Author Attribution: Automatically appends the Co-Authored-By trailer to every commit message. - Use Case: After implementing a new API controller across several files, use this Skill to review the diff, stage only the relevant source files, run pre-commit checks (type check, lint, tests), and produce a verified conventional commit. ## Quick Start Ask the agent to commit the current changes using the commit skill with a conventional commit message and co-author tag.

Frequently Asked Questions about commit

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I write a conventional commit message in git?

Use the format type: subject, where type is one of feat, fix, refactor, docs, style, test, or chore. Keep the subject under 50 characters in imperative mood with no trailing period, and add a body explaining why when needed.

How do I stage only specific files before committing?

Run git add followed by explicit file paths or a specific directory, such as git add packages/api/typescript/src/product/. Avoid git add . or git add -A, which can stage secrets, node_modules, or build artifacts.

When should I amend a git commit?

Amend only when the commit was just created and not pushed, to add forgotten files or fix a message typo using git commit --amend. Never amend commits that have been pushed or pulled by others.

What files should never be committed to git?

Never commit .env files containing secrets, node_modules directories, or build artifacts. Generated files should also be excluded unless committing them is intentional.

Should refactoring and new features be in the same commit?

No, separate refactoring from new features into distinct commits. Combine only related changes that make sense together, such as a feature with its tests or a controller with its error registration.