commit
commit creates a coherent, single-outcome VCS change while enforcing governance rules and linking to active work items. It detects your repository type (Jujutsu or Git), validates against govctl policies, and ensures unrelated changes stay separate. The skill handles traceability, commit message formatting, and post-commit verification in one workflow.
commit records a focused VCS commit with governance validation and work item traceability.
AI-generated summary based on this skill's SKILL.md
Install
govctl-org/govctl/commit · repository language: Rust
git clone https://github.com/govctl-org/govctl
cp -r govctl/.claude/skills/commit ~/.claude/skills/commitnpx skillfed install govctl-org/govctl/commitFrequently asked questions
AI-generated answers based on this skill's SKILL.md and metadata
How do I commit changes with governance validation?
commit enforces governance rules during your VCS operation. The skill detects whether you're using Jujutsu or Git, validates your changes against govctl policies, and prevents commits that violate compliance rules. Your commit is recorded only after passing all governance checks, ensuring your repository stays compliant.
How does commit link implementation to work items?
commit creates traceability by linking your VCS change to active or completed work items. When you record a focused change, the skill captures the work item reference in your commit metadata, establishing a clear chain from implementation back to the original task or requirement.
What VCS systems does commit support?
commit detects your repository type automatically and commits using either Jujutsu or Git as appropriate. The skill adapts its workflow to whichever system you're using, so you get consistent governance validation and work item linkage regardless of your VCS choice.
Can commit help me establish coherent change boundaries?
Yes. commit ensures unrelated changes stay separate by validating that each recorded change forms a single, focused outcome. Before recording, the skill helps you establish clear boundaries so your commit captures one logical unit of work rather than mixing unrelated modifications.
How do I commit to a governed repository safely?
commit validates your changes against govctl policies before recording them. The skill checks compliance rules, verifies work item linkage, formats your commit message correctly, and performs post-commit verification. This multi-step approach prevents governance violations and keeps your repository in a safe, compliant state.
What happens during a commit workflow with commit?
commit detects your VCS type, validates changes against governance rules, links to work items, ensures coherent change boundaries, formats your commit message, and verifies the result. The entire workflow runs in one operation, giving you a focused, traceable, compliant change record.
SKILL.md
rendered from the published skill — quoted content, verbatim
Commit
Record the current coherent change without inventing governance work or rewriting unrelated files.
Operational Baseline
Discovery
Detect Jujutsu first:
jj root
If it succeeds, use only jj. A colocated repository also contains .git, so
probing Git would select the wrong VCS. Only when jj root fails, use
git rev-parse --git-dir.
Treat the repository as governed when gov/config.toml or gov/ exists. In the
govctl repository itself, use cargo run --quiet -- for governance commands.
Inspect current changes with jj status and jj diff, or with the corresponding
Git commands after Git has been selected:
git status --short
git diff
git diff --cached
Use the selected VCS --help when additional syntax is needed.
Hard Stops
- This skill is the only workflow that issues raw commit commands.
- Do not create or reactivate a Work Item solely to make a commit.
- Do not perform RFC or ADR lifecycle
(truncated - see the full file via the links below)
Read as markdown · JSON record · Browse the source repository
File tree — 1 file
.claude/skills/commit/SKILL.md