ze-commit

Generate a scoped commit script from git status and diffs.

50|2|Updated Mar 27, 2026
One-click install
npx skills add https://github.com/ze-software/ze --skill ze-commit
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: ze-commit
Source: https://github.com/ze-software/ze/tree/main/.codex/skills/ze-commit
Command: npx skills add https://github.com/ze-software/ze --skill ze-commit

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This skill helps teams prepare safe, scoped commits in the Ze repository by validating scope, running pre-commit checks, and generating a commit script instead of directly staging or committing changes.

Core Features & Use Cases

  • Validate scope by inspecting git status and diffs to ensure changes belong to the intended task.
  • Run optional pre-commit checks when Go or Claude files are involved to catch issues before commit.
  • Generate a ready-to-run tmp/commit-<session>.sh script that performs git add and git commit, avoiding direct commits.

Quick Start

Inspect the current working tree and generate a safe commit script for the planned changes.

Frequently Asked Questions about ze-commit

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

FAQPage Schema
How do I prepare a scoped git commit without directly staging files?

A safe commit workflow validates scope by inspecting git status and diffs, runs pre-commit checks, and generates a temporary commit script instead of directly staging or committing your changes.

How does a pre-commit check workflow validate scoped changes in a repository?

Scoped change validation inspects git status and diffs to ensure modifications belong to the intended task, then runs optional Go or Claude checks to catch issues before generating a commit script.

What's the best way to generate a commit script for repository changes?

The best way to generate a commit script is to inspect git status, validate scope, draft a concise message, and output a ready-to-run tmp/commit-<session>.sh script that performs git add and git commit.

Can I run pre-commit checks for Go and Claude files before generating a commit script?

Yes, you can run optional pre-commit checks when Go or Claude files are involved, verifying code quality before generating the final commit script and avoiding direct commits.

Why does generating a temporary commit script prevent unsafe direct commits?

Generating a temporary commit script prevents unsafe direct commits by creating a tmp/commit-<session>.sh file for git add and git commit, letting you review staging actions before execution.

When should I avoid using an automated scoped commit workflow?

You should avoid an automated scoped commit workflow when changes span multiple unrelated tasks, as validation inspects git diffs to ensure all modifications belong to a single intended scope.