commit

Enforce standardized Git commit messages with type, scope, subject, body, and footer.

4|2|Updated Dec 28, 2025
One-click install
npx skills add https://github.com/lazygophers/ccplugin --skill commit-lazygophers
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: commit
Source: https://github.com/lazygophers/ccplugin/tree/main/plugins/tools/git/skills/commit
Command: npx skills add https://github.com/lazygophers/ccplugin --skill commit-lazygophers

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes scripts (resource) and references (resource) components.

What problem does it solve?

This Skill enforces a consistent and informative Git commit message format, improving code history readability and maintainability.

Core Features & Use Cases

  • Structured Commit Messages: Guides users to create commits with type, scope, subject, body, and footer.
  • Pre-commit Checks: Provides a checklist for ensuring code quality, linting, and avoiding problematic file types before committing.
  • Use Case: Ensure all team members follow the Conventional Commits specification for a cleaner, more understandable project history.

Quick Start

Follow the provided template and checklists to craft a standardized Git commit message.

Frequently Asked Questions about commit

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

FAQPage Schema
How do I standardize my Git commit messages for better version control?

Standardize Git commit messages by enforcing a structured format including type, scope, subject, body, and footer. This improves code history clarity and maintainability in collaborative development environments.

What is the conventional commits format and how does it structure code review history?

The conventional commits format structures code review history by requiring specific message components: type, scope, subject, body, and footer. This ensures an auditable and understandable project history for all team members.

How do I add pre-commit checks for code quality and linting before a commit?

Add pre-commit checks for code quality and linting by using a provided checklist that validates file types and ensures code standards before finalizing the commit. This prevents problematic files from entering the repository.

Can I use this structured commit workflow for collaborative software development?

Yes, you can use this structured commit workflow for collaborative software development. It enforces a consistent Git commit message format across the team, ensuring an auditable and maintainable version control history.

What is the best way to ensure my team follows conventional commits specification?

The best way to ensure your team follows the conventional commits specification is to enforce a standardized template with type, scope, subject, body, and footer. This creates a cleaner, more understandable project history.