commit

Create standardized Git commits with validated type: description messages.

Updated Mar 5, 2026
One-click install
npx skills add https://github.com/Astrumon/Spovishun --skill commit-astrumon
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: commit
Source: https://github.com/Astrumon/Spovishun/tree/main/.claude/skills/commit
Command: npx skills add https://github.com/Astrumon/Spovishun --skill commit-astrumon

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This Skill helps produce consistent, safe Git commits that adhere to the project's CLAUDE.md conventions, preventing poorly formatted messages, accidental inclusion of secrets, and improper staging workflows.

Core Features & Use Cases

  • Change analysis: summarize staged, unstaged, and untracked changes to determine commit scope.
  • Message generation & validation: pick the appropriate commit type and produce a concise subject line in the required type: short description format, adding a body when needed.
  • Safe staging and commit: stage files individually, avoid sensitive files, use a HEREDOC commit message, handle pre-commit failures, and avoid amending or pushing unless requested.
  • Use case: a developer finishing a bugfix asks the assistant to create a validated commit that stages only relevant files and follows repository conventions.

Quick Start

Ask the assistant to create a validated commit by running /commit -m "fix: shorten database migration name" or run /commit to auto-generate a convention-compliant message from the current diff.

Frequently Asked Questions about commit

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

FAQPage Schema
How do I create a git commit that follows project conventions automatically?

To create a convention-compliant git commit, you can run the /commit command to auto-generate a validated commit message from your current diff, ensuring the format matches your project's CLAUDE.md guidelines.

How do I stage files individually and avoid committing secrets in git?

To stage files individually and avoid committing secrets, this workflow analyzes your untracked and unstaged changes, staging only relevant files while explicitly avoiding sensitive files before creating the commit.

How do I use a HEREDOC commit message to handle pre-commit failures?

Using a HEREDOC commit message allows you to pass multi-line commit messages safely to git commit, and if pre-commit hooks fail, the workflow handles the failure without amending or pushing the repository state.

What is the correct git commit message format for type and short description?

The correct git commit message format is type: short description, where the workflow picks the appropriate commit type based on your summarized changes and generates a concise subject line with an optional body.

Can I auto-generate a commit message from staged and unstaged changes without pushing?

Yes, you can auto-generate a commit message by analyzing staged, unstaged, and untracked changes to determine the scope, and the process will strictly avoid amending or pushing unless explicitly requested.

What should I do when pre-commit hooks fail during a git commit?

When pre-commit hooks fail during a git commit, the workflow handles the failure gracefully by stopping the process, ensuring your repository is not improperly amended or pushed until issues are resolved.