gate-commit

Name: gate-commit
Availability: InStock
Author: WAdvanced

Gate commits on mix consistency and group staged changes into conventional commit messages.

11|Updated Dec 28, 2024

Search Tags:#git #conventional commits #elixir #staged changes #workflow safety #commit gating #CI consistency

Ready to run

npx skills add https://github.com/wadvanced/aurora_uix --skill gate-commit

💬 Prompt for ChatGPT / Claude Chat▼

Please help me install this Agent Skill.
Skill: gate-commit
Source: https://github.com/wadvanced/aurora_uix/tree/main/.claude/skills/gate-commit
Command: npx skills add https://github.com/wadvanced/aurora_uix --skill gate-commit

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This Skill prevents breaking the workflow by blocking commits when repository consistency checks fail and by enforcing clean, conventional commit groupings.

Core Features & Use Cases

Consistency Gate: Refuses to commit unless mix consistency currently passes.
Conventional Commit Grouping: Groups staged changes into intent-based commit messages such as feat:, fix:, refactor:, docs:, test:, and chore:.
Strict Staging Safety: Stages exactly specific files per group and aborts instead of guessing when grouping is ambiguous, keeping history understandable.
Guardrails & No Retrying: Does not retry, does not amend, and does not commit while the gate is failing.

Quick Start

Run the gate-commit skill to group staged changes into conventional commits only after mix consistency passes.

Frequently Asked Questions about gate-commit

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

FAQPage Schema

How do I enforce conventional commit messages in an Elixir Phoenix repository?▼

To enforce conventional commit messages in an Elixir Phoenix repository, stage specific files and run a commit gating skill that groups changes into semantic prefixes like feat: or fix:, aborting if grouping is ambiguous.

Can I block git commits automatically when mix consistency fails?▼

Yes, you can block git commits automatically when mix consistency fails by using a commit gating workflow that refuses to commit, retry, or amend until the consistency check passes successfully.

How do I group staged git changes into separate conventional commits?▼

Group staged git changes into separate conventional commits by explicitly staging individual files per intent group; the workflow applies conventional-message semantics and stops if it cannot determine a clear grouping.

Does gate-commit work with standard git staged changes or does it require specific staging?▼

gate-commit requires strict staging safety, meaning it commits only via explicitly added individual files per group rather than committing all staged changes at once, ensuring history remains understandable.

What happens if the conventional commit grouping rules cannot be applied to my staged changes?▼

If conventional commit grouping rules cannot be applied to staged changes, the workflow aborts the commit instead of guessing, ensuring ambiguous diffs are not committed with incorrect intent-based messages.

Why should I use a commit gating workflow for Elixir projects instead of committing directly?▼

Use a commit gating workflow for Elixir projects to prevent breaking CI consistency and to enforce clean, intent-based conventional commit history without manually splitting diffs or amending failed commits.