tidy-up
Skill0 starsChanged 2 months agoMITView on GitHub
Run lint, test, and build checks, then update any affected documentation. Use /tidy-up when you're done with work but weren't using tasks. 2. If a check fails, fix exactly what the output names, then run the checks once more. If they still fail, stop: report what fails, paste the relevant output, and end your turn with a line beginning BLOCKED: — do not keep iterating, and never edit a test or a check to make it pass. 3. Once checks…
In this repository6 other files it gives its agents.
- CLAUDE.mdCLAUDE.md
- analyze-sessionSkill
- add-mcp-toolSkill
- figma-guidelinesSkill
- figma-pluginsSkill
- figma-sub-agentsSkill
The file
We split this skill into the rules it gives an agent
4 rules. About 0 are common, 2 are distinctive, and 2 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.
2
Very specific
Tied to their project's names, files or tools. Probably skip.
- Common
- Distinctive
- Very specific
- Very specific: line 3
Run lint, test, and build checks, then update any affected documentation.
- Distinctive: line 7
Run the task completion checks once:
- Distinctive: line 11
If a check fails, fix exactly what the output names, then run the checks once more.
- Very specific: line 12
If they still fail, stop: report what fails, paste the relevant output, and end your turn with a line beginning BLOCKED: — do not keep …
≈ “Common” is an estimate: at least 1 in 5 of the 364,980 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
Skill: Tidy Up
Run lint, test, and build checks, then update any affected documentation. Use /tidy-up when you're done with work but weren't using tasks.
Steps
- Run the task completion checks once:
"$CLAUDE_PROJECT_DIR"/.claude/hooks/task-completion-checks.sh - If a check fails, fix exactly what the output names, then run the checks once more.
If they still fail, stop: report what fails, paste the relevant output, and end your
turn with a line beginning
BLOCKED:— do not keep iterating, and never edit a test or a check to make it pass. - Once checks pass, update any docs (CLAUDE.md, SKILL.md, prompts, README.md) and project memory files affected by your changes. Skip what's already accurate.
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.

