commit

Format changed files and create one-line git commit messages.

Updated Mar 18, 2026

Search Tags:#git #workflow #commit #formatting #code-quality #version-control #one-line-message

Ready to run

npx skills add https://github.com/abogoyavlensky/agents --skill commit-abogoyavlensky

💬 Prompt for ChatGPT / Claude Chat▼

Please help me install this Agent Skill.
Skill: commit
Source: https://github.com/abogoyavlensky/agents/tree/main/skills/commit
Command: npx skills add https://github.com/abogoyavlensky/agents --skill commit-abogoyavlensky

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This Skill enforces a disciplined commit workflow by formatting code before commit and requiring concise, one-line messages that explain the rationale.

Core Features & Use Cases

Auto-format changed code using a formatter (e.g., bb fmt) before creating a commit.
Create a git commit that includes all current changed files with a single, purpose-driven message.
Prevent attribution in commit messages to maintain a clean history.

Quick Start

Format the code and commit your current changes with a one-line message explaining why.

Frequently Asked Questions about commit

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

FAQPage Schema

How do I auto-format code and write a concise git commit message in one step?▼

You can auto-format code and write a concise git commit message in one step by running a workflow that applies a local formatter to changed files before committing them with a single, rationale-driven one-line message.

Why should git commit messages explain the rationale without attribution?▼

Git commit messages should explain the rationale without attribution to maintain a clean project history, ensuring the commit log focuses on why changes were made rather than who made them.

Do I need a local formatter installed to automate pre-commit code formatting?▼

Yes, you need a local formatter installed to automate pre-commit code formatting, as the workflow requires a formatter like bb fmt to be available to format changed files before creating a commit.

What is the best way to enforce a one-line commit message format in version control?▼

The best way to enforce a one-line commit message format in version control is to use a pre-commit discipline workflow that prevents multi-line messages and requires a single, purpose-driven statement explaining the change.

How does a pre-commit workflow handle formatting all current changed files before committing?▼

A pre-commit workflow handles formatting all current changed files by automatically applying a code formatter to the modified files, ensuring code quality is verified before finalizing the version control commit.

Can I prevent attribution lines in my git commit history automatically?▼

Yes, you can prevent attribution lines in your git commit history automatically by using a commit workflow that enforces concise messages and actively strips generated attribution from the final commit text.