mcpField
C
commit

commit

github.com/casper-studiosDevelopment15301 installsUpdated 4d ago
Repository

About commit

A skill that generates a Conventional Commits-style message and commits staged changes with git. It is intended for developers who want commit messages based only on changes they have staged.

Key features

  1. 01Conventional Commits formatting
  2. 02Message based on staged changes
  3. 03Optional scope and explanatory body
  4. 04Does not stage files

Use cases

  1. 01Committing a bug fix
  2. 02Recording a new feature
  3. 03Documenting a refactor or maintenance change

MCP support

This skill does not describe MCP integration.

Install

Copy the command and run it in a terminal.

$npx skills add https://github.com/casper-studios/casper-marketplace --skill commit

After installing, type/commitin Claude Code to confirm it loaded.

Details

From the project README

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

TypeDescription
featNew feature
fixBug fix
choreMaintenance (tooling, deps)
docsDocumentation changes
refactorCode restructure (no behavior change)
testAdding or refactoring tests
styleCode formatting (no logic change)
perfPerformance improvements

Examples

feat(auth): add JWT login flow

- Implemented JWT token validation logic
- Added documentation for the validation component

fix(ui): handle null pointer in sidebar

refactor(api): split user controller logic

- Extracted validation into separate module
- Simplified error handling flow

Footer (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

Comments

Markdown supported