mcpField
C
commit

commit

github.com/nweiiDevelopment1050 installsUpdated 1w ago
Repository

About commit

A skill for creating Git commits that follow Conventional Commits. It guides developers through reviewing changes, choosing a type and scope, and writing concise subjects and explanatory bodies.

Key features

  1. 01Conventional Commit types and format
  2. 02Subject and body writing guidelines
  3. 03Optional scope and breaking-change notation
  4. 04Staged-change review workflow

Use cases

  1. 01Formatting a feature or bug-fix commit
  2. 02Describing a breaking change in a commit
  3. 03Reviewing staged files before committing

Install

Copy the command and run it in a terminal.

$npx skills add https://github.com/nweii/agent-stuff --skill commit

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

Details

From the project README

Commit

Create well-formatted git commits following Conventional Commits.

Format

<type>[optional scope]: <description>

[optional body]

[optional footer(s)]
Types
  • feat: New feature
  • fix: Bug fix
  • docs: Documentation only
  • style: Formatting, missing semi-colons, etc. (no code change)
  • refactor: Code change that neither fixes a bug nor adds a feature
  • perf: Performance improvement
  • test: Adding missing tests
  • chore: Maintenance tasks (build process, dependencies, etc.)
Guidelines
  • Subject line: Imperative mood ("add", not "added"); aim for ≤50 characters.
  • Body: Wrap at 72; explain what and why, not how.
  • Scope: Optional, indicates section of codebase (e.g., feat(auth):).
  • Breaking changes: Add ! after type/scope (e.g., feat!:) and explain in footer.

Process

  1. Review staged changes (git diff --staged) and outstanding git status.
  2. Stage files explicitly when there's any chance git add -A would sweep in secrets or unrelated work.
  3. Pick the type and scope that fit.
  4. Write a concise subject; add a body when the change isn't self-explanatory.

Examples

feat(auth): add OAuth2 login support

Implements Google and GitHub OAuth providers.
Closes #123

fix: resolve race condition in data fetcher

The previous implementation could return stale data
when multiple requests were in flight.

chore: update dependencies to latest versions

Comments

Markdown supported