commit-guidelines

Inspect repository state and guide atomic Git commit creation.

106|5|Updated Mar 22, 2026
One-click install
npx skills add https://github.com/Firma-AI/openfirma --skill commit-guidelines-firma-ai
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: commit-guidelines
Source: https://github.com/Firma-AI/openfirma/tree/main/.skills/commit-guidelines
Command: npx skills add https://github.com/Firma-AI/openfirma --skill commit-guidelines-firma-ai

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This Skill helps maintain a clean and organized repository history by guiding you through the process of creating atomic, meaningful commits or changesets.

Core Features & Use Cases

  • Atomic Commits: Ensures that each commit has a single, clear intent.
  • Dirty Worktree Handling: Guides you on how to handle uncommitted changes before committing.
  • Code Reviews: Suggests practices for maintaining PR history and handling review comments.

Quick Start

Inspect your repository state and follow the commit guidelines for a clean and structured commit process.

Frequently Asked Questions about commit-guidelines

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

FAQPage Schema
How do I create atomic Git commits for a cleaner repository history?

Atomic Git commits ensure each commit has a single, clear intent. This Skill inspects your repository state and guides you through creating structured changesets, which keeps your repository history clean and organized for easier maintenance.

How do I handle uncommitted changes in a dirty Git worktree before committing?

Handling uncommitted changes in a dirty Git worktree requires careful staging. This Skill guides you through the process of reviewing and organizing your worktree before committing, ensuring your repository state is clean before creating new commits.

What is the best way to maintain PR history during code reviews?

The best way to maintain PR history during code reviews is to follow structured commit guidelines. This Skill suggests practices for handling review comments and keeping your pull request history clean through atomic, meaningful commits.

Do I need external dependencies to inspect my repository state for Git commits?

No external dependencies are required to inspect your repository state for Git commits. This Skill operates using local Git operations only, guiding you through the commit process without needing additional tools or external libraries.

Why should I use atomic commits for repository maintenance?

Atomic commits improve repository maintenance by ensuring each commit has a single, clear intent. This approach makes it easier to track changes, handle code reviews, and maintain a clean PR history throughout your project's development.