git-commit

Create standardized git commits with Conventional Commits and AI attribution trailers.

3|1|Updated Nov 5, 2015
One-click install
npx skills add https://github.com/Flowm/dotfiles --skill git-commit-flowm
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: git-commit
Source: https://github.com/Flowm/dotfiles/tree/main/home/.agents/skills/git-commit
Command: npx skills add https://github.com/Flowm/dotfiles --skill git-commit-flowm

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This Skill eliminates the tedious, error-prone work of manually writing git commits that don't follow standard conventions, forget to disclose AI assistance, or lack clear context for future reviewers, saving you time and keeping your project history clean and auditable.

Core Features & Use Cases

  • Conventional Commits Compliance: Automatically formats commit messages to follow the Conventional Commits specification with correct type, optional scope, and concise description.
  • Intelligent Change Review: Inspects repository state, suggests appropriate file staging, and ensures each commit contains only one logical, independently reviewable change.
  • Transparent AI Attribution: Adds a standardized Assisted-by trailer to every commit to honestly disclose AI involvement, following open source best practices for auditability.
  • Use Case: If you just finished implementing a JWT refresh token feature, this Skill will stage the relevant authentication files, draft a properly formatted feat(auth): commit message with a clear body explaining the change, and add the correct AI attribution trailer.

Quick Start

Request that the AI commit your recent changes to the user authentication module, and it will automatically handle staging, message drafting, and AI attribution for you.

Frequently Asked Questions about git-commit

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

FAQPage Schema
How do I write conventional commits with AI attribution for my git workflow?

Conventional commits with AI attribution are generated by formatting commit messages with the correct type, scope, and description, while appending an Assisted-by trailer to transparently disclose AI involvement in the git workflow.

What is the best way to separate unrelated changes into distinct git commits?

Separating unrelated changes into distinct git commits requires inspecting the repository state and suggesting appropriate file staging so each commit contains only one logical, independently reviewable change.

How does AI attribution in git commit messages work for open source auditability?

AI attribution in git commit messages works by adding a standardized Assisted-by trailer to every commit, honestly disclosing AI involvement to follow open source best practices and satisfy auditable disclosure requirements.

Can I use conventional commits for feature development and bug fixes across any software project?

You can use conventional commits for feature development, bug fixes, refactoring, and maintenance tasks across any software engineering project to maintain a consistent and auditable project commit history.

Do I need to manually stage files before creating a conventional commit?

You do not need to manually stage files; the process inspects your repository state, suggests appropriate file staging for your logical change, and drafts the properly formatted conventional commit message automatically.