commit

Saves code changes through jj-first, git-compatible routing with integrity verification and history-rewrite safeguards.

4|1|Updated Jul 31, 2025
One-click install
npx skills add https://github.com/alvis/.agents --skill commit-alvis
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: commit
Source: https://github.com/alvis/.agents/tree/main/plugins/coding/skills/commit
Command: npx skills add https://github.com/alvis/.agents --skill commit-alvis

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes scripts (resource) and references (resource) components.

What problem does it solve? Saving code changes safely is hard when work mixes multiple concerns, targets already-merged history, or must preserve unrelated dirty files. This Skill provides a single entrypoint for all commit and local-history operations, routing automatically based on working-copy state while enforcing repository history policy. ## Core Features & Use Cases - Auto-routed saves: Detects working-copy state and routes to the correct procedure — default save, split, edit, parallel workspace, empty change, divergent change, or merged-target handling — without manual flag selection. - History rewriting with integrity proofs: Supports retrospective blame fixups, reordering, and editing prior changes, with automatic backup checkpoints and post-rewrite verification comparing Git tree and content hashes. - Manifest-scoped lifecycle saves: Saves an exact checksum-bound set of paths while proving byte-for-byte preservation of all unrelated dirty work. - Use Case: You have a mixed working copy containing a feature and an unrelated typo fix. Invoke the skill and it detects multiple concerns, proposes a split plan, creates self-contained conventional commits, and verifies each change compiles and passes tests in isolation. ## Quick Start Ask the assistant to save the current working-copy changes as clean conventional commits using the commit skill.

Frequently Asked Questions about commit

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

FAQPage Schema
How do I split a mixed working copy into separate commits?▼

Invoke the skill with no flags; it auto-detects multiple concerns on the current change and routes to the split procedure. It proposes an ordered plan of domain-coherent, self-contained commits before mutating anything.

How do I edit a commit that is already in my history?▼

Ask to edit the specific change; the skill resolves it, confirms it is mutable and unmerged, runs a backup checkpoint, then applies the edit and re-verifies integrity. Merged-on-origin targets route to a corrective-PR flow instead.

Does this skill work with plain Git or only Jujutsu?▼

It is jj-first but git-compatible. It works in a plain Git repository, a jj-colocated repository, or a registered jj workspace backed by Git, selecting the appropriate mechanism per route.

What happens if a history rewrite corrupts the working tree?▼

A pre-rewrite backup captures the Git tree SHA and content hash, and a post-rewrite hook compares them. On mismatch the skill stops, shows the diff, and restores the captured jj operation or backup state.

Can this skill create or update pull requests?▼

No. It never opens, updates, or polls PRs. The --create-pr flag only hands the resolved change or stack off to the separate coding:pr create action, which owns publication and CI convergence.

When should I not use this commit skill?▼

Do not use it for composing PR titles or bodies, general remote publication, per-commit QA of an unpushed stack, or diagnosing code failures. Those belong to the PR, finalize-commits, and fix skills respectively.