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
- daledesilva/obsidian_inktheir own version, first seen Nov 9, 2026
- thoughtbot/rails-consultanttheir own version, first seen Nov 8, 2026
- pedrohcgs/claude-code-my-workflowtheir own version, first seen Nov 8, 2026
- jisuzzzz/haechitheir own version, first seen Nov 8, 2026
- dirien/yet-another-agent-harnesstheir own version, first seen Nov 8, 2026
- denysdovhan/skillstheir own version, first seen Nov 8, 2026
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-dumasSkillvalidate-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
MicrosoftSkillact-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
decocmsSkilladd-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
MicrosoftSkillgenerate-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
mitsuhikoSkilloebb-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
mitsuhikoSkillpi-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
Other versions188 projects use a version of this.
Word for word · 0
None found.
Edited · 0
None found.
Wrote their own version · 188
- microsoft/vscode★ 195ksame name
- TryGhost/Ghost★ 56ksame name
- ToolJet/ToolJet★ 41ksame name
- ShareX/ShareX★ 41ksame name
- openai/symphony★ 27ksame name
- ccusage/ccusage★ 19ksame name
- ryoppippi/ccusage★ 19ksame name
- windmill-labs/windmill★ 18ksame name
- EverMind-AI/EverMemOS★ 14ksame name
- EverMind-AI/EverOS★ 14ksame name
178 more not listed
How matches are found. Word for word: the exact same text. Edited: shares passages with this file (“99% same” means 99% of its five-word phrases also appear here; 10% or more counts). Their own version: similar meaning, or, weakest, the same name. We can’t tell which project had it first. Projects are counted among the 200 most-starred candidates, and mentions are links to the repository we found, up to 50 per site, so both counts are a floor.
In this repository13 other files it gives its agents.
- AGENTS.mdAGENTS.md
- adr-writerSkill
- decision-analysisSkill
- detachSkill
- discussSkill
- govSkill
- guard-writerSkill
- initSkill
- migrateSkill
- quickSkill
- rfc-writerSkill
- specSkill
- wi-writerSkill
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
- Very specific: line 15
Run jj root first. If it succeeds, use only jj: a colocated repository also contains .git, so probing Git first picks the wrong tool.
- Distinctive: line 26
Do not create or reactivate a Work Item just to make a commit.
- Distinctive: line 27
Do not perform RFC or ADR lifecycle transitions.
- Very specific: line 28
Do not commit governed changes while govctl check fails.
- Distinctive: line 29
Do not absorb, revert, or reformat unrelated user changes.
- Distinctive: line 30
Stop when substantive implementation has no matching active or completed Work Item and is not spec-only governance maintenance.
- Distinctive: line 43
add a note only for a durable constraint or retry rule, never for progress, validation output, review state, or the commit itself.
“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.
Files
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 checkfails. - 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
doneonly 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 newgit 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.
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
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.

