pac-commit

Generates atomic, conventional git commit messages with emoji types and issue references.

2|1|Updated Mar 4, 2026

Search Tags:#git #commit #code-review #gitmoji #version-control #conventional-commits

Ready to run

npx skills add https://github.com/ladislas/mypac --skill pac-commit

💬 Prompt for ChatGPT / Claude Chat▼

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

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This Skill guides developers to create atomic, conventional git commits that align with a repository's workflow, reducing review overhead and confusion.

Core Features & Use Cases

Enforces a conventional commit style with emoji and types, ensuring clear intent for each change.
Provides guidance for splitting large changes into meaningful commits and for writing informative commit bodies.
Supports optional scopes and references to related issues to improve traceability across the project.

Quick Start

Tell me the task you completed and I will generate an atomic, conventional commit message ready for use.

Frequently Asked Questions about pac-commit

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

FAQPage Schema

How do I write conventional commits with gitmoji for my git repository?▼

Conventional commits with gitmoji are generated automatically by combining emoji-based types, optional scopes, commit bodies, and issue references. You provide the completed task description to receive a structured commit message ready for direct use in git.

What is an atomic commit and when do I need to split changes into meaningful units?▼

An atomic commit isolates a single logical change to keep version control history clear and reduce code review overhead. You split changes into meaningful units when a large update mixes unrelated features, bug fixes, or refactoring tasks together.

How do I split large code changes into meaningful commits for easier code review?▼

To split large code changes into meaningful commits, break mixed updates into atomic units with clear intent using conventional commit style. This process applies emoji-based types, optional scopes, and informative commit bodies to ensure each change is traceable and reviewable.

Can I include optional scopes and issue references in my conventional commit messages?▼

Yes, optional scopes and issue references are supported in conventional commit messages to improve traceability across your project. The generated commit format integrates these elements alongside emoji-based types and informative commit bodies.

Does this conventional commit workflow require any specific git hooks or dependencies?▼

No specific git hooks or dependencies are required to generate conventional commit messages. The workflow applies to standard git-based development tasks, requiring only your description of the completed task to produce an atomic, conventional commit message.