git-commit

Analyze git diffs to generate conventional commit messages with type and scope.

Updated Mar 19, 2026
One-click install
npx skills add https://github.com/stabilefrisur/panmetis --skill git-commit-stabilefrisur
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: git-commit
Source: https://github.com/stabilefrisur/panmetis/tree/main/src/panmetis/skills/git-commit
Command: npx skills add https://github.com/stabilefrisur/panmetis --skill git-commit-stabilefrisur

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Git changes often lack standardized messaging; this skill analyzes diffs and helps craft conventional commits that reflect the change meaningfully, improving traceability and review.

Core Features & Use Cases

  • Analyze diff to determine type, scope, and description for the commit.
  • Support staged or working-tree diffs with optional interactive staging.
  • Generate conventional commits that conform to the Conventional Commits specification.
  • Warn against committing secrets and offer safe defaults to protect sensitive data.

Quick Start

Commit your latest changes with a conventional message by letting the tool analyze the diff and suggest a type and scope.

Frequently Asked Questions about git-commit

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

FAQPage Schema
How do I generate a conventional commit message from a git diff?

You can generate a conventional commit by analyzing your staged or working-tree diffs to automatically determine the appropriate type, scope, and description for your changes.

What is the best way to ensure my git workflow follows conventional commits?

The best way to follow conventional commits is to analyze diffs across your repository to determine type and scope, enforcing standardized messaging that improves traceability and review.

Can I analyze unstaged working-tree diffs before finalizing my commit?

Yes, you can analyze unstaged working-tree diffs and use optional interactive staging to select specific changes before generating the final conventional commit message.

Does this conventional commit generator warn against committing secrets?

Yes, the generator enforces safety by warning against committing secrets and offering safe defaults to protect sensitive data from accidental exposure in your repository.

Why do my git changes lack standardized messaging and how do I fix it?

Git changes lack standardized messaging when diffs are not analyzed for meaning; you fix this by applying conventional commits that conform to specification and accurately reflect the change.