commit

Split a dirty working tree into grouped, buildable git commits with pre-flight checks.

121|2|Updated Apr 24, 2026
One-click install
npx skills add https://github.com/AgentSystemLabs/core --skill commit-agentsystemlabs
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: commit
Source: https://github.com/AgentSystemLabs/core/tree/main/plugins/agentsystem-core/skills/commit
Command: npx skills add https://github.com/AgentSystemLabs/core --skill commit-agentsystemlabs

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This Skill prevents messy history by splitting a dirty working tree into logically grouped, buildable commits with a strict pre-flight quality gate.

Core Features & Use Cases

  • Grouped commit composition: Splits changes into 1–N commits ordered so each commit builds on the previous one (schema/migrations → backend → frontend → tests/docs).
  • Production-grade pre-flight checks: Runs a secrets scan, residue sweep, and mode-based typecheck/lint or full check-pr-readiness verification.
  • Safe commit creation: Stages explicit paths per commit (never git add . / git add -A), never amends, never pushes, and stops on failing gates unless the user explicitly forces.
  • Message style detection: Detects conventional-commits (or other house styles) from recent history and drafts subjects accordingly.
  • User-approved plan: Proposes commit groups and asks the user to approve before creating any commits.

Quick Start

Use the commit skill to split your changes into production-ready commits by running: npx @agentsystemlabs/core init (then use the tool by asking the agent to commit your changes with mode=production).

Frequently Asked Questions about commit

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

FAQPage Schema
How do I split my git changes into logically grouped commits?

Git commit grouping separates a dirty working tree into ordered, buildable commits, typically sequencing schema, backend, frontend, and tests. This prevents messy history by ensuring each commit builds on the previous one.

How do I prevent committing secrets and debug residue before pushing?

Preventing secrets and residue commits requires a pre-flight quality gate that scans diffs for sensitive data and leftover debug code. This blocks compromised code from being staged, ensuring clean, production-ready commits.

Can I enforce conventional commits and typecheck before creating a commit?

Yes, enforcing conventional commits and typecheck is possible using a production mode quality gate. The system detects house styles from recent history, drafts compliant messages, and runs mode-dependent lint and typechecks before staging.

Does this commit tool automatically push changes after staging them?

No, this commit tool does not automatically push changes. It creates new, non-amended commits with explicit per-group staging and stops on failing gates, leaving the push operation to be handled separately by a delegate.

What is the best way to ensure my commits are production-ready?

The best way to ensure production-ready commits is running a full pre-flight check-pr-readiness verification. This process scans secrets, checks residue, and validates linting before approving any commit group staging.