quick
Skill276 starsChanged 36 days agoMITView on GitHub
Execute a trivial non-behavioral change without unnecessary governance ceremony
18 other projects use a version of this.
Adopted by
Most recently taken up by
- fab-codes/agent-workflow-templatetheir own version, first seen Nov 8, 2026
- AlleyBo55/no-overthinktheir own version, first seen Nov 8, 2026
- edwinidrus/dragonhoardtheir own version, first seen Nov 8, 2026
- notque/vexjoy-agenttheir own version, first seen Nov 7, 2026
- buildomator/buildomatortheir own version, first seen Nov 4, 2026
- joetawil7/first-passtheir own version, first seen Nov 1, 2026
Used with
Projects with it also use plant-seed, next and 5 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.
notqueSkillplant-seed
Capture forward-looking idea as a seed for future feature design.
Also in 3 projects that use this
VercelSkillnext
Next.js renderer for json-render that turns JSON specs into full Next.js applications with routes, layouts, SSR, and metadata. Use when working with @json-render/next, building Next.js apps from JSON specs, or creating AI-generated multi-page applications.
Also in 3 projects that use this
SentrySkillreview
Fixture review skill.
Also in 6 projects that use this
NVIDIASkillresearch
Before designing a feature, research how comparable libraries solve the problem, check best practices, known pitfalls, and upstream changes. Use when starting a new feature, investigating an unfamiliar area, or the user asks to research something.
Also in 4 projects that use this
AWSSkillship
Finalize dev work on an issue branch — update docs, push, and open a PR.
Also in 3 projects that use this
Hugging FaceSkillimplement
Make tests pass. Invoke after /write-tests produces failing tests.
Also in 3 projects that use this
Other versions18 projects use a version of this.
Word for word · 0
None found.
Edited · 0
None found.
Wrote their own version · 18
- notque/claude-code-toolkit★ 448same name
- notque/vexjoy-agent★ 448same name
- joetawil7/first-pass★ 128same name
- buildomator/buildomator★ 102same name
- rizukirr/vibekit★ 20same name
- jamillazarev/multica-ops★ 11same name
- codebycorey/delta-spec★ 4same name
- Yafan-Yang/ai-trading★ 4same name
- AlleyBo55/no-overthink★ 3same name
- beeltec/skills★ 2same name
8 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
- commitSkill
- decision-analysisSkill
- detachSkill
- discussSkill
- govSkill
- guard-writerSkill
- initSkill
- migrateSkill
- rfc-writerSkill
- specSkill
- wi-writerSkill
The file
We split this skill into the rules it gives an agent
7 rules. 0 are common, 4 are distinctive, and 3 are very specific to this project.
0
Common
Most of the 15 edited versions we read keep these.
4
Distinctive
This author's own choices. Worth a look.
3
Very specific
Tied to their project's names, files or tools. Probably skip.
- Common
- Distinctive
- Very specific
- Very specific: line 12
Run govctl status. If the task names a Work Item, read it with govctl work show <WI-ID>.
- Distinctive: line 19
Leave this workflow when the change affects behavior, edits a governance artifact, exposes an architectural choice, or depends on an …
- Distinctive: line 22
Do not create a Work Item for a typo, comment, formatting fix, or mechanical cleanup.
- Distinctive: line 24
Do not perform artifact lifecycle or destructive operations.
- Very specific: line 25
Do not issue raw VCS commands.
- Distinctive: line 26
Stop when the scope or authority is no longer clear.
- Very specific: line 56
Use commit to record the change.
“Common” is measured: kept by at least 6 in 10 of the 15 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
Quick Change
Complete $ARGUMENTS only while it stays small, local, and non-behavioral.
Run govctl status. If the task names a Work Item, read it with
govctl work show <WI-ID>; check govctl work list active and queue only
when an existing item may already own the cleanup. Use
govctl <resource> --help for current syntax.
Hard Stops
- Leave this workflow when the change affects behavior, edits a governance artifact, exposes an architectural choice, or depends on an ambiguous requirement.
- Do not create a Work Item for a typo, comment, formatting fix, or mechanical cleanup.
- Do not perform artifact lifecycle or destructive operations.
- Do not issue raw VCS commands; use
commit. - Stop when the scope or authority is no longer clear.
Routing
| Situation | Action |
| Typo, comment, small guide fix, local mechanical cleanup | Continue with quick |
| A matching Work Item already owns the cleanup | Keep its scope and closure rules |
| The user needs durable tracking | Use at most one coarse Work Item |
| Governance artifact maintenance only | Hand off to spec |
| Open design or requirement ambiguity | Hand off to discuss |
| Behavior, implementation, or broader verification | Hand off to gov |
Activate a queued Work Item only when it exactly owns this trivial cleanup;
otherwise hand off to gov. Never implement under or close a queued item. Keep
criteria observable and notes durable; progress goes in an existing loop or the
final response. Do not create a loop for an untracked trivial change.
Make the smallest coherent edit. govctl check must pass; run focused checks
when code or generated output changes, and switch to gov if they reveal
behavioral risk. When closing a tracked item, let govctl work move <WI-ID>
done run its guards instead of rerunning them by hand first.
Done When
- the change is still non-behavioral and within scope;
- focused checks and
govctl checkpass; - any Work Item reflects the result and passes closure; and
- the final response reports the edit and validation.
Use commit to record the change.
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.