commit

Generate conventional commit messages from staged git changes and commit after confirmation.

282|23|Updated Jan 3, 2026
One-click install
npx skills add https://github.com/team-attention/stanford-cs146s-kr --skill commit-team-attention
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: commit
Source: https://github.com/team-attention/stanford-cs146s-kr/tree/main/.claude/skills/commit
Command: npx skills add https://github.com/team-attention/stanford-cs146s-kr --skill commit-team-attention

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This skill automates the creation and verification of conventional commit messages for staged changes, ensuring consistent history and reducing manual drafting time.

Core Features & Use Cases

  • Automated commit message generation: Analyze the current changes and propose a conventional commit message.
  • User confirmation: Prompt for review and confirmation before executing the commit.
  • Workflow compatibility: Integrates with common Git workflows to enforce standardized messaging across a project.

Quick Start

To use this skill, run /commit to generate a message for your staged changes, review it, and confirm to commit. You can also run /commit --all to stage all changes and commit, or /commit --message "feat: add feature" to specify a message directly.

Frequently Asked Questions about commit

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

FAQPage Schema
How do I automatically generate conventional commit messages for staged git changes?

You can automatically generate conventional commit messages by analyzing git status and diffs to propose a type-based message, which is then committed after your confirmation.

What is the best way to enforce standardized commit history across a Git development workflow?

The best way to enforce standardized commit history is to automate type-based message generation for staged changes, ensuring consistent conventional commits across teammates.

Can I commit all unstaged changes at once using conventional commit formats?

Yes, you can stage all changes and commit them automatically by running the command with the all flag, which analyzes the changes to generate the conventional commit message.

Does this commit automation tool require an existing git repository to function?

Yes, this commit automation requires a Git-based development workflow environment because it analyzes staged git changes and diffs to generate the commit message.

How do I manually specify a conventional commit message while using an automated workflow?

You can manually specify a conventional commit message by passing your desired text directly within the command, overriding the automated generation for that specific commit.