commit

Creates validated conventional commit messages while checking staged diffs for secrets.

Updated Jul 18, 2025

Search Tags:#git #conventional commits #staging #quality gates #commit message #secret scanning #ci validation

Ready to run

npx skills add https://github.com/dougborg/stocktrim-openapi-client --skill commit-dougborg

💬 Prompt for ChatGPT / Claude Chat▼

Please help me install this Agent Skill.
Skill: commit
Source: https://github.com/dougborg/stocktrim-openapi-client/tree/main/.claude/skills/commit
Command: npx skills add https://github.com/dougborg/stocktrim-openapi-client --skill commit-dougborg

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Prevents broken CI, inconsistent history, and accidental credential leaks by enforcing conventional commit formatting and running required quality gates before creating a commit.

Core Features & Use Cases

Quality-Gated Conventional Commits: Ensures commit messages follow type(scope): description and that validation checks pass before committing.
Secret-Safety Guardrails: Reduces the risk of committing secrets by requiring a staged-diff review of what is about to be committed.
Intentional Staging for Clean History: Promotes staging specific files (and optionally hunks) to avoid mixing unrelated changes and accidental inclusions.

Quick Start

Use the commit skill to stage specific changes, run the project verification command, and create a conventional commit message in the format type(scope): description.

Frequently Asked Questions about commit

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

FAQPage Schema

How do I create conventional commit messages that pass CI validation?▼

To create conventional commit messages that pass CI validation, stage specific file changes, run the repository's discoverable verification command, and format the message as type(scope): description before committing.

How can I prevent committing secrets and API keys to my git history?▼

Prevent committing secrets to git history by reviewing staged diffs before finalizing the commit, which reduces the risk of accidental credential leaks by checking exactly what is about to be committed.

Why should I stage specific files instead of committing all changes at once?▼

Staging specific files instead of committing all changes at once promotes intentional staging for a clean history, avoiding mixing unrelated changes and preventing accidental inclusions in your commit.

Does this git commit workflow require any external dependencies or modules?▼

This git commit workflow does not require external dependencies or modules to function, relying solely on your staged diffs, the repository's discoverable verification command, and standard git commands.

What is the correct format for a conventional commit message?▼

The correct format for a conventional commit message is type(scope): description, which ensures consistent history and prevents broken CI by enforcing conventional commit formatting rules.