commit

Stage files and generate Conventional Commits-compliant messages.

1|Updated Apr 17, 2025
One-click install
npx skills add https://github.com/carrot-foundation/schemas --skill commit-carrot-foundation
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: commit
Source: https://github.com/carrot-foundation/schemas/tree/main/.cursor/skills/commit
Command: npx skills add https://github.com/carrot-foundation/schemas --skill commit-carrot-foundation

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Stage and commit code changes with Conventional Commits format to ensure consistent history, clearer reviews, and improved traceability across teams.

Core Features & Use Cases

  • Group changes by concern into logical commits to reflect intent.
  • Stage specific files explicitly to avoid accidental changes.
  • Generate Conventional Commits-compliant messages with appropriate scope and type for each commit.

Quick Start

Stage the intended files and commit with a conventional message describing the change.

Frequently Asked Questions about commit

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

FAQPage Schema
How do I write conventional commit messages for grouped changes?

To write conventional commit messages for grouped changes, stage specific files explicitly by concern and generate a commit with an appropriate type and scope. This ensures consistent history and clearer traceability across teams.

What is the conventional commits format used for in version control?

The conventional commits format is used in version control to standardize commit messages, improving traceability and code reviews. It enforces structured headers with specific types and scopes to maintain a disciplined project history.

How do I stage specific files to avoid accidental changes in git?

To avoid accidental changes in git, stage specific files explicitly before committing. This selective staging allows you to group changes by logical concern and commit only the intended modifications.

Does this workflow support scoped conventional commits for better traceability?

Yes, this workflow supports scoped conventional commits to enhance traceability. It enforces the conventional commits format, allowing you to apply appropriate scopes and maintain header length discipline for each commit.

What is the best way to maintain header length discipline in commit messages?

The best way to maintain header length discipline is to use a workflow that enforces Conventional Commits formatting rules. This standardizes commit messages, ensuring headers remain concise while grouping changes by their intent.