git-commit

Validate Git repository state and stage changes with safety gates before Angular-style commit messaging.

29|5|Updated Mar 13, 2026
One-click install
npx skills add https://github.com/johnqtcg/awesome-skills --skill git-commit-johnqtcg
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: git-commit
Source: https://github.com/johnqtcg/awesome-skills/tree/main/skills/git-commit
Command: npx skills add https://github.com/johnqtcg/awesome-skills --skill git-commit-johnqtcg

SYSTEM DOCUMENTATION & REQUIREMENTS

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

What problem does it solve?

Solve unsafe Git commits by validating repository state, staging changes with safety gates, and generating a conventional Angular-style message.

Core Features & Use Cases

  • Preflight gates ensure repository state is clean, no unresolved conflicts, and no sensitive data is staged.
  • Staging and grouping logic prevents mixing multiple logical changes in a single commit and supports targeted commits.
  • Commit message generation uses Angular/Conventional Commits style to produce concise, standard messages.
  • Use Case: a developer wants to commit a small fix with a clean message without exposing secrets or breaking history.

Quick Start

In your project, run the git-commit skill to stage changes with safety gates and generate a concise Angular-style commit message.

Frequently Asked Questions about git-commit

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

FAQPage Schema
How do I prevent committing secrets and unresolved conflicts in Git?▼

To prevent leaking credentials in Git, use preflight gates that validate repository state and scan staged changes for sensitive data before finalizing the commit message.

How do I generate a conventional Angular-style commit message automatically?▼

You can generate a conventional Angular-style commit message by analyzing staged changes to automatically produce concise, standard messages that follow the Angular commit convention.

What is the best way to separate unrelated changes before making a Git commit?▼

The best way to separate unrelated changes is by using staging and grouping logic that prevents mixing multiple logical updates, enabling targeted commits and maintaining a clean project history.

Does this Git commit workflow check for unresolved merge conflicts?▼

Yes, this Git commit workflow enforces preflight gates that validate repository state and explicitly check for unresolved merge conflicts before allowing any changes to be staged.

Why should I use safety gates for staging changes in Git?▼

You should use safety gates for staging changes to guard against breaking history by validating the repository state, blocking sensitive data, and preventing the mixing of unrelated logical changes.