Commit
- 287 installs
- 11 repo stars
- Updated August 4, 2026
- casper-studios/casper-marketplace
commit is a Claude Code agent skill that drafts Conventional Commits v1.0.0 messages from staged git diffs and runs git commit for developers who want standardized messages without writing them manually.
About
Generates commit messages following the Conventional Commits spec and commits only staged changes. A developer uses it to produce consistent commit messages while keeping control over what gets staged.
- Follows Conventional Commits v1.0.0 for staged changes only
- Never runs git add or adds ads/footers
Commit by the numbers
- 287 all-time installs (skills.sh)
- Ranked #143 of 733 Git & Pull Requests skills by installs in the Skillselion catalog
- Data as of Aug 5, 2026 (Skillselion catalog sync)
npx skills add https://github.com/casper-studios/casper-marketplace --skill commitAdd your badge
Show developers this skill is listed on Skillselion. Paste this into your README.
| Installs | 287 |
|---|---|
| repo stars | ★ 11 |
| Last updated | August 4, 2026 |
| Repository | casper-studios/casper-marketplace ↗ |
How do you write conventional commit messages from staged diffs?
Generates a Conventional Commits message for staged changes and commits them, without staging files or adding footers.
Who is it for?
Developers who stage changes deliberately and want agent-generated Conventional Commits messages plus an executed git commit in one step.
Skip if: Developers who need git add, multi-commit rebases, pull request creation, or commit messages for unstaged or unstaged-plus-staged mixed working trees.
When should I use this skill?
Staged git changes exist and the developer asks to commit, generate a commit message, or invokes /commit.
What you get
A git commit on staged files with a Conventional Commits v1.0.0 message (type, optional scope, title, and body).
- git commit with Conventional Commits formatted message
By the numbers
- Follows Conventional Commits v1.0.0 specification
- User-invocable via /commit command
Files
Commit
Generate a commit message and commit staged changes using git.
Based on the Conventional Commits v1.0.0 specification.
Guidelines
- Only generate the message for staged files/changes
- Don't add any files using
git add- user decides what to add - DO NOT add any ads or footers
Format
<type>(<scope>): <message title>
<bullet points summarizing what was updated>Rules
- Title: lowercase, no period, max 50 characters
- Scope: optional, feature affected
- Body: explain _why_, not just _what_
- Bullet points: concise and high-level
Allowed Types
| Type | Description |
|---|---|
| feat | New feature |
| fix | Bug fix |
| chore | Maintenance (tooling, deps) |
| docs | Documentation changes |
| refactor | Code restructure (no behavior change) |
| test | Adding or refactoring tests |
| style | Code formatting (no logic change) |
| perf | Performance improvements |
Examples
feat(auth): add JWT login flow
- Implemented JWT token validation logic
- Added documentation for the validation componentfix(ui): handle null pointer in sidebarrefactor(api): split user controller logic
- Extracted validation into separate module
- Simplified error handling flowFooter (optional)
- Reference issues:
Closes #123 - Breaking changes: Start with
BREAKING CHANGE:
Avoid
- Vague titles: "update", "fix stuff"
- Overly long or unfocused titles
- Excessive detail in bullet points
Related skills
Caveman CommitGenerate terse, Conventional Commits messages that preserve intent without fluff or AI attribution.272k94k
Resolving Merge ConflictsQuickly understand, resolve, and commit merge conflicts without losing work or breaking their flow.183k193kGit Guardrails Claude CodePrevent Claude Code from accidentally running destructive git commands like force push, hard reset, or clean.175k193k
Using Git WorktreesGuarantee every new feature or implementation task runs inside a clean, isolated workspace without polluting the main branch or current working directory.149k263k
Git CommitGenerate accurate conventional commit messages and intelligently stage files directly from natural language requests.40.6k37.2k
Resolve Merge ConflictsQuickly understand and resolve Git merge conflicts without losing context or breaking changes.16.5k148How it compares
Pick commit when you only need message generation plus git commit on an already-staged index; use a broader git or PR skill when you also need staging, branching, or pull request steps.
FAQ
Does commit run git add before committing?
commit does not run git add. The commit skill only reads staged changes and commits what is already in the index, so developers choose exactly which files enter each commit.
What commit message format does commit use?
commit follows the Conventional Commits v1.0.0 specification, producing messages with a type, optional scope, title, and body such as feat(api): add endpoint before running git commit.
How do you invoke the commit skill?
commit is user-invocable in agent sessions: run /commit or ask the agent to create a commit after staging files with git add. The skill drafts the message and executes git commit.