commit

Group uncommitted Git changes into logical conventional-format commits.

1|Updated Feb 15, 2026
One-click install
npx skills add https://github.com/n0rvyn/indie-toolkit --skill commit-n0rvyn
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: commit
Source: https://github.com/n0rvyn/indie-toolkit/tree/main/dev-workflow/skills/commit
Command: npx skills add https://github.com/n0rvyn/indie-toolkit --skill commit-n0rvyn

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This Skill automates saving progress in a Git repository by analyzing uncommitted changes, grouping related modifications, and creating commits that follow conventional formatting.

Core Features & Use Cases

  • Automatically detect and categorize uncommitted changes into logical groups (features, fixes, docs).
  • Create conventional-commit messages per group and apply them in separate commits.
  • Perform a pre-commit audit to catch secrets, debug traces, and unusually large files before committing.

Quick Start

Group uncommitted changes into logical commits and apply conventional messages.

Frequently Asked Questions about commit

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

FAQPage Schema
How do I group uncommitted git changes into logical commits?

This Skill groups uncommitted git changes by analyzing your working directory, categorizing related modifications into logical groups, and applying separate commits to each group automatically.

Can I automatically generate conventional commit messages for my changes?

Yes, you can automatically generate conventional commit messages. The Skill analyzes grouped changes and creates standardized conventional-format messages for each logical commit.

How do I scan git diffs for secrets and debug traces before committing?

You scan git diffs for secrets and debug traces using the Skill's pre-commit audit, which automatically detects sensitive data, debug residues, and large files before applying any commits.

What is the best way to organize mixed changes in a software project using Git?

The best way to organize mixed changes in a Git project is to automate grouping by analyzing diffs, categorizing modifications into features or fixes, and creating separate conventional commits.

Does this pre-commit audit catch large files and debug residues in git?

Yes, the pre-commit audit catches large files and debug residues in git. It scans uncommitted diffs to ensure safe commits by preventing sensitive data and large files from being committed.