commit

Generate Conventional Commits and validate staged git changes for secrets and large files.

161|21|Updated Mar 26, 2026
One-click install
npx skills add https://github.com/softspark/ai-toolkit --skill commit-softspark
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: commit
Source: https://github.com/softspark/ai-toolkit/tree/main/app/skills/commit
Command: npx skills add https://github.com/softspark/ai-toolkit --skill commit-softspark

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes scripts (resource) components.

What problem does it solve?

Produces well-structured Conventional Commit messages and prevents unsafe or low-quality commits by validating staged changes, detecting secrets, and flagging large files before they are committed.

Core Features & Use Cases

  • Conventional Commit Generation: Guides and enforces Conventional Commits format for consistent changelogs and automated releases.
  • Pre-commit Validation: Runs a bundled pre-commit-check.py script to detect secrets, large files, and suggest commit type and scope based on staged file paths.
  • Developer Workflow Integration: Ideal for individual developers and CI pipelines to ensure linting, testing, and safety checks are considered prior to committing.

Quick Start

Create a Conventional Commit message for the current staged changes and run the pre-commit validation script to check for secrets, large files, and suggested commit type and scope.

Frequently Asked Questions about commit

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

FAQPage Schema
How do I generate conventional commit messages for staged git changes?

To generate conventional commit messages, the Skill analyzes your staged git changes to suggest an appropriate commit type and scope. It then formats the final commit message according to Conventional Commits standards for consistent changelogs.

Can I check for secrets and large files in a git pre-commit hook?

Yes, you can detect secrets and flag large files before committing by running the bundled pre-commit-check.py script. This validation ensures unsafe or low-quality changes are caught prior to pushing to the repository.

What do I need to run pre-commit validation on my staged files?

To run pre-commit validation, you need a git repository with staged changes, access to the git CLI, and Python installed. These prerequisites allow the validation script to analyze your staged file paths and check for issues.

How does automated commit type and scope suggestion work for git changes?

Automated commit type and scope suggestion works by evaluating the file paths of your staged git changes. The pre-commit validation script uses this path data to infer the appropriate conventional commit category and affected scope.

Is there a way to automate conventional commits in a CI pipeline?

You can automate conventional commits in a CI pipeline by integrating this Skill into your developer workflows. It enforces commit message structure and runs safety checks, ensuring linting and testing standards are met prior to committing.