commit

Create Git commits with conventional messages and automated file triage.

Updated Feb 22, 2026
One-click install
npx skills add https://github.com/rahulrajaram/rahulskills --skill commit-rahulrajaram
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: commit
Source: https://github.com/rahulrajaram/rahulskills/tree/main/skills/commit
Command: npx skills add https://github.com/rahulrajaram/rahulskills --skill commit-rahulrajaram

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This Skill automates the process of creating well-formed Git commits by intelligently triaging changed files, filtering out unwanted artifacts, and ensuring adherence to conventional commit standards.

Core Features & Use Cases

  • Automated File Triage: Classifies files into COMMIT, ALLOWED, SKIP, or REVIEW categories based on predefined rules and an override file.
  • Artifact Filtering: Automatically identifies and skips common AI planning artifacts, agent state files, build outputs, and secrets.
  • Conventional Commits: Generates commit messages following the conventional commit format, including optional scope and body.
  • Safety Checks: Prevents accidental commits of secrets and sensitive data, and routes history rewriting to a dedicated skill.

Quick Start

Use the commit skill to create a commit with the message 'feat: implement user authentication'.

Frequently Asked Questions about commit

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

FAQPage Schema
How do I automatically filter out secrets and planning artifacts when creating a Git commit?

To automate Git commit hygiene, this skill triages changed files and automatically skips secrets, build outputs, and AI agent state files. It presents an assessment table classifying files into COMMIT, ALLOWED, SKIP, or REVIEW categories before staging.

Can I enforce conventional commit message formatting across staged, unstaged, and untracked files?

Yes, you can enforce conventional commit formatting across staged, unstaged, and untracked files. The skill generates commit messages following the conventional commit standard, including optional scope and body, after triaging the changes.

What is the best way to prevent accidental commits of sensitive data in version control?

Preventing accidental commits of sensitive data is handled via built-in safety checks that identify secrets and route history rewriting away from the standard flow. The skill filters sensitive files during its automated triage process.

Does this Git commit assistant support manual overrides for file staging decisions?

Yes, manual overrides are supported via a `.githooks/commit-allow` file. This human-controlled mechanism lets you explicitly allow specific files to bypass the automated SKIP filtering rules during the commit triage.

How do I handle Git history rewriting when cleaning up accidentally committed artifacts?

For Git history rewriting, this skill routes the process to a dedicated history rewriting skill rather than handling it internally. This prevents unsafe operations during standard commit generation and maintains workflow safety.