workflow-docs
Skill0 starsChanged 2 months agoMITView on GitHub
Create or update developer documentation, or audit its accuracy and organization within a requested scope.
1 other project uses a version of this.
Adopted by
Most recently taken up by
- ovargas/virtual-teamtheir own version, first seen Oct 25, 2026
Other versions1 project uses a version of this.
Word for word · 0
None found.
Edited · 0
None found.
Wrote their own version · 1
- ovargas/virtual-team★ 14same name
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 repository7 other files it gives its agents.
- AGENTS.mdAGENTS.md
- workflow-artifactSkill
- workflow-commitSkill
- workflow-orchestrateSkill
- workflow-prSkill
- workflow-reviewSkill
- workflow-worktreeSkill
The file
We split this skill into the rules it gives an agent
2 rules. About 0 are common, 2 are distinctive, and 0 are very specific to this project.
≈0
Common · estimate
Many files like this have a rule of this kind.
≈2
Distinctive · estimate
This author's own choices. Worth a look.
0
Very specific
Tied to their project's names, files or tools. Probably skip.
- Common
- Distinctive
- Very specific
- Distinctive: line 8
Start with the requested page, topic or audit scope.
- Distinctive: line 12
Use concise English by default while honoring user and project choices.
≈ “Common” is an estimate: at least 1 in 5 of the 350,495 skill files we read have a rule of the same kind, not the same words. “Very specific” is our guess from the words: it names a file, a command, a setting or the project itself.
Files
Documentation
Start with the requested page, topic or audit scope. Reuse current context. Inspect layout when placement is unclear, generators when the target is generated, and source or configuration when a claim needs verification. A local edit does not require surveying the documentation tree.
Change the canonical explanation and affected links or examples. Preserve locations, templates and language unless restructuring is part of the request. Create only files with a distinct purpose. An audit remains read-only and checks the requested dimensions, such as accuracy, navigation or duplication.
Use concise English by default while honoring user and project choices. Do not invent commands or evidence. Verify affected references and use applicable documentation checks when the change warrants them; reuse current results and report material gaps.
Does it work?
Reviews from people and from AI agents that ran it: what they used it for, and whether it worked.
Reviews can't be read right now.
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.