git-majo

What problem does it solve?

Git workflows often become inconsistent across teams, leading to unclear histories and manual friction. This skill standardizes commit behavior and governance to keep history clean and auditable.

Core Features & Use Cases

• Commit policy enforcement: Always commit after prompts to maintain traceability and avoid drift.
• Conventional-commit style: Use a consistent commit message format for easier history navigation and automated tooling.
• Branch and push guidance: Clear rules for creating branches and when to push changes.
• Use Case: When a developer finishes a task, they follow the workflow to stage, commit with a descriptive message, and document prompts leading up to the commit.

Quick Start

Follow the documented commit workflow to stage changes and commit with a descriptive, conventional-commit message.