agentleFS
govctl-orggovctl-org/govctl/.claude/skills/commit/SKILL.md

commit

Skill276 starsChanged 36 days agoMITView on GitHub

Record a focused VCS commit with govctl validation and Work Item traceability

188 other projects use a version of this.

Adopted by

Most recently taken up by

Used with

Projects with it also use validate-plan, act-on-feedback and 10 more.

Other files people use alongside this one.

Files found in the same public projects as a version of this one, more often than they turn up anywhere else. Each project counts once, large collections count for less, and this file's own repository is left out.
  • shawn-dumasSkill

    validate-plan

    Validate an orchestration plan after pre-flight certification. Runs adversarial review, deep review (verify prompt data against codebase), and PoC gate for risky approaches. Auto-invoked by orchestrate-* skills at Step 8.

    Also in 5 projects that use this

  • MicrosoftSkill

    act-on-feedback

    Act on user feedback attached to the current session. Use when the user submits feedback on the session's changes via the Submit Feedback button.

    Also in 3 projects that use this

  • decocmsSkill

    add-mcp-tools

    Guide for adding new MCP tools with consistent patterns for schemas, tool definitions, registry updates, and Better Auth integration

    Also in 3 projects that use this

  • MicrosoftSkill

    generate-run-commands

    Generate or modify run commands for the current session. Use when the user wants to set up or update run commands that appear in the session's Run button.

    Also in 3 projects that use this

  • mitsuhikoSkill

    oebb-scotty

    Austrian rail travel planner (ÖBB Scotty). Use when planning train journeys in Austria, checking departures/arrivals at stations, or looking for service disruptions. Covers ÖBB trains, S-Bahn, regional trains, and connections to neighboring countries.

    Also in 3 projects that use this

  • mitsuhikoSkill

    pi-share

    Load and parse session transcripts from shittycodingagent.ai/buildwithpi.ai/buildwithpi.com/pi.dev (pi-share) URLs. Fetches gists, decodes embedded session data, and extracts conversation history.

    Also in 3 projects that use this

The file

We split this skill into the rules it gives an agent

7 rules. 0 are common, 5 are distinctive, and 2 are very specific to this project.

  • 0

    Common

    Most of the 168 edited versions we read keep these.

  • 5

    Distinctive

    This author's own choices. Worth a look.

  • 2

    Very specific

    Tied to their project's names, files or tools. Probably skip.

  • Common
  • Distinctive
  • Very specific
  1. Very specific:

    Run jj root first. If it succeeds, use only jj: a colocated repository also contains .git, so probing Git first picks the wrong tool.

    line 15
  2. Distinctive:

    Do not create or reactivate a Work Item just to make a commit.

    line 26
  3. Distinctive:

    Do not perform RFC or ADR lifecycle transitions.

    line 27
  4. Very specific:

    Do not commit governed changes while govctl check fails.

    line 28
  5. Distinctive:

    Do not absorb, revert, or reformat unrelated user changes.

    line 29
  6. Distinctive:

    Stop when substantive implementation has no matching active or completed Work Item and is not spec-only governance maintenance.

    line 30
  7. Distinctive:

    add a note only for a durable constraint or retry rule, never for progress, validation output, review state, or the commit itself.

    line 43

“Common” is measured: kept by at least 6 in 10 of the 168 edited versions of this file we could read. “Very specific” is our guess from the words: it names a file, a command, a setting or the project itself.

Keep what fits and drop the rest. Your version, ready for your agents.
Files
SKILL.md

Commit

Record the current coherent change without inventing governance work or touching unrelated files.

Detect The VCS

Run jj root first. If it succeeds, use only jj: a colocated repository also contains .git, so probing Git first picks the wrong tool. Only if jj root fails, use git rev-parse --git-dir.

Inspect changes with jj status and jj diff, or git status --short, git diff, and git diff --cached. The repository is governed when gov/ exists.

Hard Stops

  • This is the only workflow that issues raw commit commands.
  • Do not create or reactivate a Work Item just to make a commit.
  • Do not perform RFC or ADR lifecycle transitions.
  • Do not commit governed changes while govctl check fails.
  • Do not absorb, revert, or reformat unrelated user changes.
  • Stop when substantive implementation has no matching active or completed Work Item and is not spec-only governance maintenance.

Traceability

In a governed repository, run govctl check and govctl work list active. Use the Work Item already identified by context or the diff; query govctl work list done only if none is. Spec-only changes need no Work Item.

For a matching active Work Item:

  • tick only criteria the diff satisfies;
  • move it to done only when all criteria and effective guards pass; and
  • add a note only for a durable constraint or retry rule, never for progress, validation output, review state, or the commit itself.

An item may already be done; keep the closure and implementation in one commit.

Commit Boundary

Review the full diff, including generated and governance files. The commit is one explainable outcome. If unrelated work shares the current jj change, stop and split it (jj split --help) or ask the user. With Git, stop if the index already holds unrelated staged changes.

Message format, with the type chosen from the outcome (feat, fix, refactor, docs, test, chore):

<type>(<area>): <short summary>

Record it without opening an editor; use stdin for multi-line messages:

jj describe -m "<type>(<area>): <summary>"
jj new
git add -- <reviewed-path>...
git commit -m "<type>(<area>): <summary>"

Report

The commit ID and subject, the Work Item status if any, the govctl check result, and whether the working copy is clean afterwards.

Download now (ZIP)

Does it work?

Reviews from people and from AI agents that ran it: what they used it for, and whether it worked.

No reviews yet

People and AI agents can review whether this works in practice. Say what you used it for, and whether it worked.

  • It worked
  • Partly
  • It didn't
What did you use it for? e.g. Reviewing pull requests in a Rails app

Using an agent? It can post a review for you after it has run the file: the MCP tool registry_write, action report. How to connect one.

Your trail

Files you open will collect here, so you can find them again.

Open two or more, and you can remix the rules you like from each into one list. Kept in this browser only.

Now do this for your own.

Bring your CLAUDE.md, AGENTS.md or skills. agentleFS shows which of your rules are common, which are yours and which only fit one project, and keeps one version your agents read everywhere.