tidy
Skill1 starsChanged 38 days agoNo licenceView on GitHub
Hygiene pass on this repo's `.wcp/issues/` queue: upgrade thin issues to the /issue bar, retitle, cancel high-confidence duplicates, block real dependencies, and set `done` when a work commit already exists. Skip any issue tidied in the last 7 days unless /tidy --force or /tidy 0123. Finish the board first, then one needs-you list. Skip live foreign claims. Track last pass via a tidy-pass line in the issue file plus a local ledger. Use when the user runs /tidy, /tidy --force, /tidy TEAM-123, says "tidy the queue", "tidy the board", "clean up the board", "thicken thin tickets", or "close issues that are already done".
24 other projects use a version of this.
Adopted by
Most recently taken up by
- nagi-studio/skillstheir own version, first seen Nov 8, 2026
- agentmemoir/skillstheir own version, first seen Nov 1, 2026
- NobiResearch/Ovenbirdtheir own version, first seen Nov 1, 2026
- croffasia/itsaplantheir own version, first seen Oct 31, 2026
- crimx/skillstheir own version, first seen Oct 28, 2026
- smkg75/wikidoctheir own version, first seen Oct 25, 2026
Used with
Projects with it also use architect, retro and 3 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.
Harut8Skillarchitect
Also in 3 projects that use this
AWSSkillretro
Conduct a retrospective on a coding session.
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
Microsoft AzureSkillverify
End-to-end app testing pipeline for browser-based web apps on cloud browsers via Azure Playwright Workspaces: verify the live app, author tests for working flows, heal failing tests, then re-run with video and produce one consolidated report. Three phases (app verification, test authoring, test healing) plus a scoped final sanity run; each phase emits a sub-report. Use when asked to "verify my app", "make sure my app works and has good test coverage", "do a full QA pass", "add tests where I'm missing coverage", "fix failing tests and add new ones", "smoke test before deploy", "QA my deployment", or any combined verify-and-test ask. Requires Azure CLI (`az login`) and a Playwright Workspace resource ID — bootstraps configs on first invocation. Browser-based web apps with Playwright only — not for unit/API tests, native mobile/desktop, load/perf, or full accessibility audits.
Also in 3 projects that use this
SentrySkillreview
Fixture review skill.
Also in 3 projects that use this
Other versions24 projects use a version of this.
Word for word · 0
None found.
Edited · 0
None found.
Wrote their own version · 24
- croffasia/itsaplan★ 2.2ksame name
- nagi-studio/skills★ 470same name
- mblode/agent-skills★ 189same name
- collectifweb/claude-skills★ 4same name
- crimx/skills★ 4same name
- wyattjoh/skills★ 3same name
- agentmemoir/skills★ 2same name
- jxxsteven7/zotero-librarian★ 2same name
- smkg75/wikidoc★ 2same name
- angusfretwell/skills★ 1same name
14 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 repository18 other files it gives its agents.
- agent-onboard-promptSkill
- deep-secSkill
- execute-planSkill
- human-copySkill
- identifySkill
- implementSkill
- issueSkill
- issuesSkill
- mapSkill
- prbSkill
- project-reviewSkill
- solveSkill
- startSkill
- statSkill
- vercel-flagsSkill
- walkSkill
- water-cooler-protocolSkill
- yeetSkill
The file
Show its rules and text
We split this skill into the rules it gives an agent
13 rules. 0 are common, 4 are distinctive, and 9 are very specific to this project.
0
Common
Most of the 19 edited versions we read keep these.
4
Distinctive
This author's own choices. Worth a look.
9
Very specific
Tied to their project's names, files or tools. Probably skip.
No licence file, so all rights are reserved — read it at the source. We count its rules but don't quote them. Read them on GitHub.
“Common” is measured: kept by at least 6 in 10 of the 19 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.
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.