git-commit

Generates Conventional Commits messages by analyzing git diff and staging changes.

Updated Aug 23, 2026
One-click install
npx skills add https://github.com/living-relation/tailormade --skill git-commit-living-relation
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: git-commit
Source: https://github.com/living-relation/tailormade/tree/main/.agents/skills/git-commit
Command: npx skills add https://github.com/living-relation/tailormade --skill git-commit-living-relation

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes scripts (resource) components.

What problem does it solve?

It removes the friction of writing consistent, Conventional Commits messages by analyzing your actual changes and guiding you through staging and message creation.

Core Features & Use Cases

  • Auto-detect commit type and scope from the diff and/or your staged changes, reducing manual guesswork.
  • Generate Conventional Commits messages that summarize what changed using an imperative, standardized format.
  • Interactive commit flow with optional overrides for type, scope, and description, plus intelligent file staging for logically grouped commits.

Quick Start

Use this skill to commit your current changes with a Conventional Commit message by asking: create a git commit for my staged changes using conventional commits.

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 my staged changes?

To generate a Conventional Commit message, the skill analyzes your git diff to infer the commit type and scope, then produces a standardized summary. It supports an interactive flow allowing you to override the generated type, scope, and description before committing.

How does intelligent file staging work for logically grouped commits?

Intelligent file staging analyzes your working tree changes to group related files together. This logic ensures that your commits are logically organized, guiding you through the staging process to create clean, isolated conventional commits without manual guesswork.

Can I override the auto-detected commit type and scope during the interactive flow?

Yes, you can override the auto-detected commit type and scope. The interactive commit flow allows you to manually adjust the type, scope, and description, ensuring the final Conventional Commit message accurately reflects your repository maintenance intent.

Does this skill analyze both staged and working tree diffs?

Yes, the skill analyzes the appropriate git diff, whether from your staged changes or the working tree. It applies safe staging logic to evaluate the commit context and generate an accurate Conventional Commits message for your repository maintenance workflow.

What guardrails exist against destructive git actions when creating commits?

The skill includes built-in guardrails against destructive or unsafe git actions. By applying safe staging logic during the commit message generation and file staging process, it prevents operations that could negatively impact your repository maintenance workflow.

Why use Conventional Commits for repository maintenance workflows?

Conventional Commits standardize your commit messages into an imperative format using auto-detected types and scopes. This removes manual friction, ensures reliable repository maintenance, and generates clean diffs that summarize what changed across your project.