git-commit

Create conventional git commits with type, scope, and description.

10.9k|1.3k|Updated Jan 14, 2026
One-click install
npx skills add https://github.com/accomplish-ai/accomplish --skill git-commit-accomplish-ai
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: git-commit
Source: https://github.com/accomplish-ai/accomplish/tree/main/apps/desktop/bundled-skills/git-commit
Command: npx skills add https://github.com/accomplish-ai/accomplish --skill git-commit-accomplish-ai

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This skill helps developers create clean, consistent git commits that follow a conventional format, improving history readability and collaboration.

Core Features & Use Cases

  • Enforces conventional commits with a clear type, scope, and description.
  • Guides staging decisions to ensure only relevant changes are included.
  • Provides templates and examples for common scenarios (feat, fix, docs, refactor).

Quick Start

Use the git-commit helper after staging changes to generate a well-structured commit message that adheres to the project’s conventions.

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 git commits that follow best practices?

Conventional commits follow a structured format with type, scope, and description—like 'feat(auth): add login validation'. This format improves readability, enables automation, and maintains clean history across teams.

What changes should I stage before committing?

Stage only related changes that address a single concern—one feature, fix, or refactor per commit. Staging selectively prevents mixing unrelated work and keeps commits atomic and reviewable.

What are the different commit types in conventional commits?

Conventional commits use types like feat (new feature), fix (bug fix), docs (documentation), refactor (code restructuring), and others. Each type signals intent and helps organize version history.

Can I use conventional commits across different project types?

Yes, conventional commits work with any repository—web apps, libraries, documentation sites, or monorepos. The format is language and framework agnostic, making it universal across development workflows.

Why should my team use consistent commit messages?

Consistent commit messages enable searchable history, automated changelog generation, and clearer collaboration. They reduce friction during code review and help new team members understand project evolution.