commit-helper

Generate semantic Git commit messages and run pre-commit quality gates.

Updated Dec 15, 2025
One-click install
npx skills add https://github.com/unfazed-dev/nexus_store --skill commit-helper-unfazed-dev
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: commit-helper
Source: https://github.com/unfazed-dev/nexus_store/tree/main/.claude/skills/commit-helper
Command: npx skills add https://github.com/unfazed-dev/nexus_store --skill commit-helper-unfazed-dev

SYSTEM DOCUMENTATION & REQUIREMENTS

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

What problem does it solve?

This Skill streamlines the process of creating well-formatted, semantic Git commit messages and enforces code quality before commits are finalized.

Core Features & Use Cases

  • Semantic Commit Generation: Assists in crafting commit messages that follow conventional commit standards (type: description).
  • Pre-Commit Quality Gates: Integrates automated checks for code formatting, analysis, and invariant rules.
  • Attribution Stripping: Automatically removes AI-generated attribution from commit messages.
  • Use Case: Before committing code changes, this Skill will prompt you to select or write a semantic commit message and will automatically run dart format, flutter analyze, and custom invariants to ensure code quality.

Quick Start

Run the pre-commit check script to validate your changes before committing.

Frequently Asked Questions about commit-helper

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

FAQPage Schema
How do I generate semantic git commit messages automatically?

Semantic git commit messages are generated automatically by analyzing staged changes and crafting conventional commit formats (type: description). This ensures single-line commit messages follow standard conventions without manual formatting effort.

How do I enforce pre-commit hooks for code formatting and static analysis?

Pre-commit hooks enforce code quality by automatically running dart format, flutter analyze, and custom invariant checks before finalizing commits. This integration blocks commits that fail formatting or static analysis validation.

What are conventional commit standards and when do I need them?

Conventional commit standards use a type: description format to categorize changes like features or fixes. You need them when maintaining structured commit history for semantic versioning, changelog generation, or team collaboration clarity.

Can I use pre-commit quality gates with Dart and Flutter projects?

Yes, pre-commit quality gates integrate directly with Dart and Flutter projects by running dart format for code formatting and flutter analyze for static analysis. Custom invariants provide additional project-specific validation rules.

How do I remove AI-generated attribution from commit messages?

AI-generated attribution is stripped automatically from commit messages through integrated Git hooks. This ensures clean commit histories without AI tool signatures while preserving the semantic message structure.

How do I format migration commits using semantic conventions?

Migration commits use semantic conventions by applying a specific migration type prefix within the single-line commit message format. This categorizes structural changes distinctly from regular features or bug fixes.