commit

Generate Conventional Commits from git status, diffs, and branch metadata.

Updated Feb 13, 2026
One-click install
npx skills add https://github.com/pegasus-isi/claude-plugin-marketplace --skill commit-pegasus-isi
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: commit
Source: https://github.com/pegasus-isi/claude-plugin-marketplace/tree/main/plugins/pegasus-dev/skills/commit
Command: npx skills add https://github.com/pegasus-isi/claude-plugin-marketplace --skill commit-pegasus-isi

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This skill eliminates the friction of manual git commit formatting by automatically generating Conventional Commits that adhere to project standards and link directly to issue trackers.

Core Features & Use Cases

  • Conventional Commits: Automatically formats messages using the commitizen standard with proper types, scopes, and descriptions.
  • Issue Linking: Intelligently extracts issue numbers from branch names to append mandatory Refs or Closes footers.
  • Context Awareness: Inspects the current git status, diffs, and branch history to infer the most accurate commit type and scope.

Quick Start

Ask the assistant to commit the current changes using the commit skill to automatically generate a formatted message linked to the active branch issue.

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 commits from git diffs?

You can automatically generate conventional commits by analyzing git status, diffs, and branch metadata to infer the proper commit type, scope, and description. This approach eliminates manual formatting friction and ensures strict commit history hygiene.

How does AI parse branch names to link git commits to issue trackers?

AI parses branch names to intelligently extract issue numbers and inject them into commit footers. This automatically appends mandatory Refs or Closes footers to your conventional commit messages, linking them directly to your issue tracking systems.

Can I use automated conventional commits for projects requiring strict version control workflows?

Yes, automated conventional commits are designed for software development projects requiring strict version control workflows. The process formats messages using the commitizen standard to maintain consistent commit history.

What is the best way to standardize git commit messages without manual formatting?

The best way to standardize git commit messages is using AI to inspect your current git status, diffs, and branch history. This context awareness automatically infers the most accurate commit type and scope, ensuring adherence to project standards.

Do I need a specific issue tracking system to automatically inject issue references into commit footers?

No specific issue tracking system is strictly required because the process works by parsing branch names to extract issue numbers. It uses this branch metadata to append mandatory Refs or Closes footers to your conventional commits automatically.

Why does my automated commit message include a specific scope and type?

Your automated commit message includes a specific scope and type because the system inspects your git diffs and branch history. This context awareness allows it to infer the most accurate conventional commit format for your current changes.