git-commit

Generate conventional commit messages by analyzing git diffs.

8|5|Updated Oct 15, 2024
One-click install
npx skills add https://github.com/TruvetaPublic/OpenToken --skill git-commit-truvetapublic
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: git-commit
Source: https://github.com/TruvetaPublic/OpenToken/tree/main/.github/skills/git-commit
Command: npx skills add https://github.com/TruvetaPublic/OpenToken --skill git-commit-truvetapublic

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Execute git commit with conventional commits by analyzing diffs, auto-detecting type and scope, and staging changes intelligently to improve collaboration.

Core Features & Use Cases

  • Auto-detecting type and scope from changes: Infers the appropriate Conventional Commit type and scope from the diff.
  • Message generation from diff: Produces standardized commit messages that follow the Conventional Commits spec.
  • Interactive commit workflow: Allows overrides for type, scope, and description as needed.
  • Intelligent staging: Groups related changes for coherent commits.

Quick Start

Tell me what changed and I will automatically stage relevant files and generate a conventional commit message.

Frequently Asked Questions about git-commit

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

FAQPage Schema
How do I generate conventional commit messages from git diffs?

You can generate conventional commit messages from git diffs by analyzing the changes to automatically infer the type and scope, producing a standardized message without manual formatting. This Skill automates that workflow directly from your staged or unstaged changes.

Can I automatically stage related files together for a coherent git commit?

Yes, intelligent staging groups related changes together to ensure a coherent git commit. This automated staging process analyzes your diffs and organizes files logically before generating the final conventional commit message.

Does this conventional commit generator require external tools beyond standard Git?

No, this conventional commit generator requires no external tools beyond standard Git. It handles types, scopes, bodies, and breaking-change footers internally by analyzing your diffs directly within your existing development environment.

How do I override the auto-detected type and scope in an interactive commit workflow?

You can override the auto-detected type and scope during the interactive commit workflow. This allows you to manually adjust the inferred type, scope, and description as needed before finalizing the conventional commit message generation.

What is the best way to automate git commit workflows for features and fixes?

The best way to automate git commit workflows for features and fixes is to analyze diffs and generate conventional commit messages automatically. This ensures standardized documentation across various scopes with optional interactive overrides and intelligent staging.

How does intelligent staging handle breaking changes in conventional commits?

Intelligent staging handles breaking changes by analyzing the diff and applying the appropriate breaking-change footers per the Conventional Commits specification. It groups related changes to ensure the commit accurately reflects the impact of the code modifications.