commit

Orchestrate quality-gated Git commits with secret scanning and automated releases.

Updated Feb 26, 2026
One-click install
npx skills add https://github.com/wilsto/claude-code-starter-kit --skill commit-wilsto
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: commit
Source: https://github.com/wilsto/claude-code-starter-kit/tree/main/.claude/skills/commit
Command: npx skills add https://github.com/wilsto/claude-code-starter-kit --skill commit-wilsto

SYSTEM DOCUMENTATION & REQUIREMENTS

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

What problem does it solve?

This Skill automates a comprehensive quality-gated commit workflow, preventing secrets from being committed, ensuring code quality, and automating release processes.

Core Features & Use Cases

  • Secret Scanning: Blocks commits containing sensitive information like API keys or passwords.
  • Code Quality Checks: Integrates tests, formatting, and optional code reviews.
  • Automated Documentation: Updates changelogs and documentation based on commit content.
  • Conventional Commits: Enforces a standardized commit message format.
  • Automated Release: Handles tagging, version bumping, and GitHub releases.
  • Use Case: Developers can use /commit instead of raw git commit to ensure every change pushed to the repository meets high standards for security, quality, and documentation.

Quick Start

Use the commit skill to stage, review, and commit your changes with automated quality gates.

Frequently Asked Questions about commit

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

FAQPage Schema
How do I automate a secure git commit workflow with secret scanning and code review?

Automating a secure git commit workflow manages secret scanning, code review, formatting, and testing before pushing changes. This process blocks sensitive information like API keys and ensures quality standards are met before integration.

How do I prevent API keys and passwords from being committed to git?

Preventing API keys and passwords from being committed to git requires a secret scanning quality gate. This automated check detects sensitive information in staged changes and blocks the commit process if any secrets are found.

How do I generate changelogs and update documentation based on conventional commits?

Generating changelogs and updating documentation based on conventional commits requires parsing standardized commit messages. This automated process extracts commit content to update changelog files and maintain accurate project documentation.

How do I automate semantic versioning and GitHub release tagging?

Automating semantic versioning and GitHub release tagging involves bumping version numbers based on commit history and applying Git tags. This automated release process integrates with GitHub CLI to create robust, standardized releases.

Does the automated commit workflow support integration with GitHub CLI?

Yes, the automated commit workflow integrates with Git and GitHub CLI. This integration enables robust automated pushing, semantic versioning, and release tagging directly through the command line interface.

What is the best way to enforce code quality checks before pushing code?

The best way to enforce code quality checks before pushing code is a multi-step, quality-gated commit process. This approach integrates tests, formatting, and optional code reviews to ensure high standards for security and quality.