commit

Analyze git diffs and generate Conventional Commits messages.

31|5|Updated Jan 14, 2026
One-click install
npx skills add https://github.com/NSEvteev/FullSpec --skill commit-nsevteev
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: commit
Source: https://github.com/NSEvteev/FullSpec/tree/main/.claude/skills/commit
Command: npx skills add https://github.com/NSEvteev/FullSpec --skill commit-nsevteev

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Manual git commits often lead to inconsistent message formats and missed hooks. This skill standardizes commit messages according to Conventional Commits and automates staging and pushing.

Core Features & Use Cases

  • Analyze diffs and generate Conventional Commit messages that follow the project's standards.
  • Stage changed files, run pre-commit and post-commit hooks, and push by default.
  • Use in feature branches, bug fixes, and maintenance tasks to maintain a clean and searchable Git history.

Quick Start

Run the /commit command to automatically generate a conventional commit, stage changes, and push unless you specify --no-push.

Frequently Asked Questions about commit

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

FAQPage Schema
How do I automate conventional commits for feature branches and bug fixes?

This skill automates conventional commits by analyzing git diffs to generate standardized commit messages, staging changes, and running hooks automatically. It handles the workflow for feature branches and bug fixes, ensuring a consistent history without manual message formatting.

What is the best way to generate conventional commit messages from git diffs?

Generating conventional commit messages from git diffs is handled automatically by analyzing your staged and unstaged changes. The tool formats the output according to Conventional Commits standards, applying consistent types and scopes based on the diff content for a clean and searchable Git history.

Does this commit automation tool run pre-commit and post-commit hooks?

Yes, this commit automation tool runs pre-commit and post-commit hooks during the staging process. It integrates your existing git hooks into the automated workflow, ensuring all validation and checks execute before the changes are committed and pushed to your repository.

Can I stage changes and push automatically without running git commands manually?

You can stage changes and push automatically by running the commit command, which handles staging, hook execution, and pushing by default. If you want to commit locally without pushing, you can provide the --no-push flag to skip the remote update step.

Why should I use automated commit formatting instead of manual git commits?

Automated commit formatting prevents the inconsistent message formats and missed hooks common with manual git commits. It standardizes messages according to Conventional Commits and automates staging and pushing, maintaining a clean and searchable Git history across maintenance tasks.

Do I need any external dependencies to automate staging and pushing git changes?

No external dependencies are required to automate staging and pushing git changes with this skill. It operates across local git workflows natively, analyzing diffs and applying conventional commit formats without needing additional packages or components installed.