Commit Summary
Commit Summary analyzes staged or unstaged git changes and generates properly formatted Conventional Commit messages with the right type, scope, and breaking-change markers. It groups unrelated changes into logical commits, detects unsafe files, and can stage and create commits after your approval.
Commit Summary generates Conventional Commit messages from your git changes with automatic type detection and breaking-change flagging.
AI-generated summary based on this skill's SKILL.md
Decision gist · record as of 2026-07-23
Commit Summary generates Conventional Commit messages from your git changes with automatic type detection and breaking-change flagging. Commit Summary analyzes staged or unstaged git changes and generates properly formatted Conventional Commit messages with the right type, scope, and breaking-change markers. It groups unrelated changes into logical commits, detects unsafe files, and can stage and create commits after your approval.
Use it when
- Yes.
- Commit Summary reads your git diffs and converts them into readable, structured descriptions.
Install
shipshitdev/skills/commit-summary · repository language: Python
generated, unverified - the skill's exact subdirectory could not be determined; check the repository on GitHub
Open directory. Skills are indexed for reading, not audited. Review a skill's body before installing it.
Frequently asked questions
AI-generated answers based on this skill's SKILL.md and metadata
What does Commit Summary do?
Commit Summary analyzes your staged or unstaged git changes and automatically generates properly formatted Conventional Commit messages. It detects the commit type, scope, and breaking-change markers, then groups unrelated changes into logical commits. After your approval, it can stage and create the commits for you.
Can Commit Summary auto generate commit messages from my code changes?
Yes. Commit Summary examines your git diff and staged changes, then generates clear, concise commit messages automatically. It reduces the time spent manually writing descriptions by analyzing what actually changed in your code.
How does Commit Summary summarize git diffs?
Commit Summary reads your git diffs and converts them into readable, structured descriptions. It identifies the nature of each change—whether it's a feature, fix, or breaking change—and formats the message according to Conventional Commit standards with proper type and scope markers.
Does Commit Summary detect unsafe files in commits?
Yes. Commit Summary includes safety detection for unsafe files, helping you avoid accidentally committing sensitive or problematic content. It flags these issues before you approve and create the commit.
What is a Conventional Commit message?
Commit Summary uses Conventional Commits, a standardized format that includes a type (like 'feat' or 'fix'), optional scope, and description. This format improves repository documentation and makes commit history more readable and machine-parseable for tools and automation.
Can I review changes before Commit Summary creates a commit?
Yes. Commit Summary generates the commit message and groups changes for your review and approval before staging or creating any commits. You maintain full control over what gets committed.
Let your AI agent find skills like this
Example. Real query, live index.
You found this page by searching. An agent finds it by wishing: SkillFed indexes 56,283 agent skills by what they can do, searchable in plain language.
wish › “Automatically generate clear, concise commit messages from code changes”
Give your agent the search over MCP, or paste the wish link into any chat. No install? Search from any chat →
Related skills
Dependency Audit scans your project's installed packages for known vulnerabilities, detects secrets about to be committed, and verifies lockfile integrity. Run it once to report findings, or wire it into CI as a merge gate that blocks risky dependencies from reaching production.
This skill analyzes your repository's commit history to detect its message style, then generates a subject line and optional body that fit the established pattern. It stages unstaged changes when needed, respects pre-commit hooks and signing requirements, and confirms the commit with a log preview.
Create Commit analyzes your staged changes and generates properly formatted conventional commits, automatically inferring commit type and scope from the diff. It detects breaking changes and flags potential secrets before committing, while enforcing pre-commit hooks to maintain code quality standards.
Commit automates version control by enforcing atomic commits—one logical change per commit—with built-in safeguards against committing to main/master branches. It guides you through branch creation, staged change review, and properly formatted commit messages to keep project history clear and reversions safe.
Clerk Validator audits your authentication implementation for modern Clerk patterns and deprecated code. It checks package versions, proxy.ts setup, ClerkProvider configuration, auth imports, and environment variables—catching issues before they reach production. Run it during setup, after AI-generated code, or in CI/CD pipelines.
Conventional Commits helps you write structured, semantic commit messages that enable automated versioning and changelog generation. It guides you through selecting commit types, adding optional scopes, and formatting descriptions in imperative mood, with support for breaking changes and footer tokens.
More skills smart-commit (MIT) · managing-git-workflows (MIT) · merge-prep (MIT) · commit-message (MIT) · Commit Message (unlicensed)