Software Design Review
atilladeniz/Kubeli
Analyzes code based on John Ousterhout's "A Philosophy of Software Design".
Run all code quality skills — effects, memo, callbacks, state, React Query, emcn design review, url-state, comments, and test-audit — analyzing in parallel, then applying fixes sequentially
Install Cleanup
$ npx skills add simstudioai/sim --skill cleanup -a claude-codeProject install by default; add -g for ~/.claude/skills/.
$ gh skill install simstudioai/sim cleanup --agent claude-codeProject scope by default; add --scope user for a personal install. Needs GitHub CLI 2.90.0 or later (public preview).
$ git clone --depth 1 https://github.com/simstudioai/sim.git skills-src && mkdir -p .claude/skills && cp -r skills-src/.agents/skills/cleanup .claude/skills/cleanup && rm -rf skills-srcUse ~/.claude/skills/ instead of .claude/skills for a personal install. The folder must contain SKILL.md.
Claude Code skills documentation · loads skills from .claude/skills/
Install the "cleanup" agent skill from https://github.com/simstudioai/sim/tree/main/.agents/skills/cleanup into .claude/skills/cleanup/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "cleanup", then confirm the skill loads.Claude Code copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
$skill-installer install https://github.com/simstudioai/sim/tree/main/.agents/skills/cleanupType this inside Codex. $skill-installer <name> installs a curated skill from openai/skills. The installer writes to $CODEX_HOME/skills (default ~/.codex/skills). Restart Codex if the skill does not show up.
$ npx skills add simstudioai/sim --skill cleanup -a codexProject install goes to .agents/skills/; add -g for ~/.codex/skills/.
$ gh skill install simstudioai/sim cleanup --agent codexProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/simstudioai/sim.git skills-src && mkdir -p .agents/skills && cp -r skills-src/.agents/skills/cleanup .agents/skills/cleanup && rm -rf skills-srcUse ~/.agents/skills/ instead of .agents/skills for a personal install.
Codex skills documentation · loads skills from .agents/skills/
Install the "cleanup" agent skill from https://github.com/simstudioai/sim/tree/main/.agents/skills/cleanup into .agents/skills/cleanup/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "cleanup", then confirm the skill loads.Codex copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
$ npx skills add simstudioai/sim --skill cleanup -a cursorProject install goes to .agents/skills/; add -g for ~/.cursor/skills/.
$ gh skill install simstudioai/sim cleanup --agent cursorProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/simstudioai/sim.git skills-src && mkdir -p .cursor/skills && cp -r skills-src/.agents/skills/cleanup .cursor/skills/cleanup && rm -rf skills-srcUse ~/.cursor/skills/ instead of .cursor/skills for a personal install.
Cursor skills documentation · loads skills from .cursor/skills/, .agents/skills/, .claude/skills/, .codex/skills/
Install the "cleanup" agent skill from https://github.com/simstudioai/sim/tree/main/.agents/skills/cleanup into .cursor/skills/cleanup/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "cleanup", then confirm the skill loads.Cursor copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
$ gemini skills install https://github.com/simstudioai/sim.git --path .agents/skills/cleanup--scope user (default) or --scope workspace; --path is the subfolder of the repo that holds the skill; --consent skips the security confirmation prompt.
$ npx skills add simstudioai/sim --skill cleanup -a gemini-cliProject install goes to .agents/skills/; add -g for ~/.gemini/skills/.
$ gh skill install simstudioai/sim cleanup --agent gemini-cliProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/simstudioai/sim.git skills-src && mkdir -p .gemini/skills && cp -r skills-src/.agents/skills/cleanup .gemini/skills/cleanup && rm -rf skills-srcUse ~/.gemini/skills/ instead of .gemini/skills for a personal install, then run /skills reload.
Gemini CLI skills documentation · loads skills from .gemini/skills/, .agents/skills/
Install the "cleanup" agent skill from https://github.com/simstudioai/sim/tree/main/.agents/skills/cleanup into .gemini/skills/cleanup/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "cleanup", then confirm the skill loads.Gemini CLI copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
$ gh skill install simstudioai/sim cleanupInstalls for Copilot at project scope by default; add --scope user for a personal install. Preview a skill first with gh skill preview. Needs GitHub CLI 2.90.0 or later (public preview).
$ npx skills add simstudioai/sim --skill cleanup -a github-copilotProject install goes to .agents/skills/; add -g for ~/.copilot/skills/.
$ git clone --depth 1 https://github.com/simstudioai/sim.git skills-src && mkdir -p .github/skills && cp -r skills-src/.agents/skills/cleanup .github/skills/cleanup && rm -rf skills-srcUse ~/.copilot/skills/ instead of .github/skills for a personal install. Commit .github/skills so cloud agent and code review can use it.
GitHub Copilot skills documentation · loads skills from .github/skills/, .claude/skills/, .agents/skills/
Install the "cleanup" agent skill from https://github.com/simstudioai/sim/tree/main/.agents/skills/cleanup into .github/skills/cleanup/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "cleanup", then confirm the skill loads.GitHub Copilot copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
$ npx skills add simstudioai/sim --skill cleanup -a opencodeOpenCode documents no install command of its own. Project install goes to .agents/skills/; add -g for ~/.config/opencode/skills/.
$ gh skill install simstudioai/sim cleanup --agent opencodeProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/simstudioai/sim.git skills-src && mkdir -p .opencode/skills && cp -r skills-src/.agents/skills/cleanup .opencode/skills/cleanup && rm -rf skills-srcUse ~/.config/opencode/skills/ instead of .opencode/skills for a personal install.
OpenCode skills documentation · loads skills from .opencode/skills/, .claude/skills/, .agents/skills/
Install the "cleanup" agent skill from https://github.com/simstudioai/sim/tree/main/.agents/skills/cleanup into .opencode/skills/cleanup/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "cleanup", then confirm the skill loads.OpenCode copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
Facts
- Skill name
cleanup- GitHub stars
- 30k
- Token cost
- ~1.4k tokens
- SKILL.md length
- 844 words
- Files
- 1
- Skills in repo
- 40
- Repo updated
- First seen
- Licence
- Apache-2.0
At a glance
Run all code quality skills — effects, memo, callbacks, state, React Query, emcn design review, url-state, comments, and test-audit — analyzing in parallel, then applying fixes sequentially
- Works in 4 steps: Parallel analysis (read-only) → Converge → Sequential apply → …
- Tasks that involve Design review and critique
- SKILL.md covers Step 1 — Parallel analysis…, Step 2 — Converge, Step 3 — Sequential apply and Step 4 — Summary, plus 1 more section
- Calls git and bun
What it does
Cleanup is an agent skill from simstudioai/sim. Run all code quality skills — effects, memo, callbacks, state, React Query, emcn design review, url-state, comments, and test-audit — analyzing in parallel, then applying fixes sequentially
Its SKILL.md is about 1.4k tokens, which your agent loads only when the skill is triggered. It is a single SKILL.md file with no bundled scripts.
It sits in Development, covering Design review and critique and Code quality. It works with TanStack. The repository describes itself as: Sim is the collaborative workspace to build, deploy, and monitor AI agents and workflows. Used by 100,000+ builders. The licence is Apache-2.0.
When your agent uses it
- Tasks that involve Design review and critique
- Tasks that involve Code quality
Example prompts
- “/cleanup”
Workflow steps
4 steps, taken from the step headings in SKILL.md.
What it can do on your machine
Read from SKILL.md and the folder at commit 546d4e7. It shows what the files ask for, not the result of running them.
Tool permissions
Pre-approves nothing: there is no allowed-tools line, so your agent's usual permission prompts apply.
From allowed-tools in the SKILL.md frontmatter.
Runs code
Shell commands in SKILL.md call:
gitbun
From the folder's file list and the shell code blocks in SKILL.md.
Network
No URLs in SKILL.md. Its commands use git, which can reach the network depending on how they are called.
From URLs in SKILL.md, links to its own repository left out.
Credentials
Names no API keys, tokens, secrets or passwords.
From names ending in _API_KEY, _TOKEN, _SECRET, _KEY or _PASSWORD in SKILL.md.
Context cost
Cleanup loads about 1.4k tokens when it runs. Until then it costs about 49 tokens; SKILL.md has 844 words of instructions outside code blocks.
Estimates: characters ÷ 4, the usual rule of thumb; real counts depend on the model's tokenizer. Scripts and assets cost tokens only if the agent reads them.
Safety
Auto-check passed
The automated check found no risky patterns in SKILL.md.
Automated static check — not a guarantee. Review scripts before installing. It scans the text of SKILL.md for risky patterns (piping downloads into a shell, reading credential files, hidden Unicode, destructive commands); files beside SKILL.md are not scanned.
SKILL.md
The full file from simstudioai/sim at commit 546d4e7, republished under its Apache-2.0 licence (© simstudioai). 844 words, ~1,450 tokens.
Download SKILL.mdSave it as
.claude/skills/cleanup/SKILL.md (or your agent's skills folder).- name
- cleanup
- description
- Run all code quality skills — effects, memo, callbacks, state, React Query, emcn design review, url-state, comments, and test-audit — analyzing in parallel, then applying fixes sequentially
- argument-hint
- [scope] [fix=true|false]
Cleanup
Arguments:
- scope: what to review (default: your current changes). Examples: "diff to staging", "PR #123", "src/components/", "whole codebase"
- fix: whether to apply fixes (default: true). Set to false to only propose changes.
User arguments: $ARGUMENTS
Step 1 — Parallel analysis (read-only)
Parse $ARGUMENTS into scope and fix: extract the fix=true|false token wherever it appears in the string and strip it from scope; defaults are the current changes and fix=true. fix is consumed by Step 3 only — the passes below always run fix=false.
Spawn up to nine passes concurrently as subagents in a single message (multiple Agent tool calls); pass 9 runs only when its condition holds. Each runs its skill on the parsed scope with fix=false — analysis and proposals ONLY, no edits. Instruct each agent to return its findings as a structured list: for every proposed change, the file path, line range, a one-line description of the change, and the exact before/after so the orchestrator can apply it without re-deriving.
Run these in parallel on the parsed scope:
/you-might-not-need-an-effect <scope> fix=false/you-might-not-need-a-memo <scope> fix=false/you-might-not-need-a-callback <scope> fix=false/you-might-not-need-state <scope> fix=false/react-query-best-practices <scope> fix=false/emcn-design-review <scope> fix=false/you-might-not-need-url-state <scope> fix=false/you-might-not-need-a-comment <scope> fix=false/test-audit audit <test paths>— read-only; only when the scope adds or changes test files (*.test.ts(x),*.integration.ts,**/e2e/**,apps/sim/scripts/test-*-e2e.ts). First resolve a free-form scope to the concrete list of added or changed test paths (git diff --name-onlyagainst the scope's base) and pass those paths. It applies the authoring gate to every new or changed test and proposes deleting the ones that fail it.
Step 2 — Converge
Collect all findings into one list, keeping each proposal tagged with the pass that produced it — do NOT collapse a file's proposals into a single unlabeled patch, because Step 3 applies in pass order and needs those labels. Detect overlaps where two passes touch the same region (common: a state pass and an effect pass on the same block, or a memo and callback pass on the same component). Reconcile only genuine same-region conflicts, and drop proposals a sibling pass has made moot; a reconciled change inherits the pass label of whichever of its passes comes first in the Step 3 dependency order (effects → state → memo → callback → React Query → url-state → emcn → comments → tests), so it is applied at the earliest safe point. Non-overlapping proposals stay as-is with their own labels. The output is a per-pass list of surviving changes, not a per-file patch.
Show full SKILL.md (434 more words)Show less
Step 3 — Sequential apply
If fix=false, skip this step — just report the proposals from Step 2.
Otherwise apply the surviving changes yourself (in the main context, not delegated), iterating pass by pass in this dependency order so earlier structural changes settle before later passes build on them:
- effects → 2. state → 3. memo → 4. callback → 5. React Query → 6. url-state → 7. emcn design → 8. comments → 9. tests
For each pass in turn, apply all of that pass's changes, then move to the next pass. A file touched by several passes is therefore edited once per pass, in this order — not once as a merged patch. This is what makes the ordering real: a single merged-per-file patch would collapse all passes into one edit and lose it.
Comments apply after every structural pass, on purpose: that pass operates on whatever the earlier passes settled the code into, so it never edits lines a sibling pass is about to delete or rewrite. Tests apply last because they only touch test files; in Step 2, drop any other pass's proposal on a test file the tests pass deletes.
Treat every Step 1 proposal as snapshot-relative, not authoritative. All passes analyzed the original files in parallel, so a proposal's line ranges and before/after text describe the code as it was before any edits — once an earlier pass has run, a later pass's snippet may no longer match. So for each change, before applying:
- Re-read the file and locate the target by its content (the proposal's
old_stringsnippet), not by its line number — line numbers from Step 1 are only a hint for where to look, since earlier edits shift them. - If the
old_stringstill matches verbatim, apply it — a content-anchored edit is safe even if its line moved. - If it no longer matches (an earlier pass altered that region), do not force the stale patch. Re-derive the change from the current code by re-applying that pass's rule to the construct, or drop it if a prior pass already made it moot. Never apply a proposal against text it wasn't computed from.
After all edits, run bun run lint from the repo root (it autofixes formatting across the repo; there is no per-file target).
Step 4 — Summary
Output a summary across all passes that ran: what each found, what was applied vs. skipped-as-redundant, and any proposals that need a human decision.
Boundary findings
Never resolve a boundary finding by adding a // boundary-raw-fetch / // double-cast-allowed annotation — fix the call (adopt the contract + requestJson, or narrow the type). Annotations are only for the documented exceptions in .claude/rules/sim-api-contracts.md → Boundary annotations.
© simstudioai, Apache-2.0. Rendered from Markdown: HTML in the file is shown as text, images as links, and headings moved down two levels. Raw file
Files
Just SKILL.md in .agents/skills/cleanup of simstudioai/sim.
Open the folder on GitHubat commit 546d4e7
Compare with similar skills
Cleanup next to the 5 skills that share the most tags, products or categories with it. Stars are the repository's; “used in” counts other GitHub owners with a copy.
| Skill | Stars | Used in | Tokens | Auto-check | Licence | Repo updated |
|---|---|---|---|---|---|---|
| Cleanup this skillsimstudioai/sim | 30k | — | ~1.4k | Automated safety check: Pass | Apache-2.0 | |
| Software Design Reviewatilladeniz/Kubeli | 387 | — | ~5.3k | Automated safety check: Pass | MIT | |
| Code Reviewgetsentry/skills | 1k | 3 repos | ~692 | Automated safety check: Pass | Apache-2.0 | |
| Improve Appwondelai/skills | 2.4k | — | ~6.1k | Automated safety check: Pass | MIT | |
| Design EvaluationAbhinavbwj/Urban-Design-Skills-Claude | 132 | 1 repos | ~9.2k | Automated safety check: Pass | MIT | |
| 122 Java Type Designjabrena/plinth | 445 | — | ~977 | Automated safety check: Pass | Apache-2.0 |
Similar skills
- Official
Code Review
getsentry/skills
Perform code reviews following Sentry engineering practices.
Improve App
wondelai/skills
Guided journey from a shipped app that works but feels rough to a product that fits the job, flows without friction, reads clearly, and persuades honestly.
Design Evaluation
Abhinavbwj/Urban-Design-Skills-Claude
Evaluate urban designs against comprehensive criteria drawn from all major global standards, certification systems, and theoretical frameworks.
122 Java Type Design
jabrena/plinth
A skill your agent uses when you need to review, improve, or refactor Java code for type design quality — including establishing clear type hierarchies, applying consistent naming conventions…
WooCommerce Code Review
woocommerce/woocommerce
Reviews WooCommerce code changes against the project's standards, flagging backend PHP architecture, naming, documentation, data integrity and testing violations.
More from simstudioai/sim
All 40 skills in this repoSim Helm
simstudioai/sim
Install, upgrade, and operate the Sim Helm chart on Kubernetes.
Add Column Type
simstudioai/sim
Add a new table column type to Sim — registry entry, icon, storage shape, coercion, and the behavioral hooks the grid and API read.
Add Enrichment
simstudioai/sim
Add a code-defined table enrichment (registry entry) under apps/sim/enrichments/ backed by an ordered provider cascade, ensuring every provider tool it calls has hosted-key support.
Add Hosted Key
simstudioai/sim
Add hosted API key support to a tool so Sim provides the key (metered and billed to the workspace) when a user has not brought their own.
Add Managed CLI
simstudioai/sim
Add or upgrade a curated, immutable managed CLI for Sim Function sandboxes, including client-safe catalog metadata, a pinned server-only installation recipe, checksum and executable verification…
Add Selector
simstudioai/sim
Add or update a Sim dynamic selector using the shared manifest, server attachment, and selectors.execute path.
Related
Works with
Categories
Questions about Cleanup
What does Cleanup do?
Run all code quality skills — effects, memo, callbacks, state, React Query, emcn design review, url-state, comments, and test-audit — analyzing in parallel, then applying fixes sequentially. Cleanup is an agent skill from simstudioai/sim.
When should I use Cleanup?
Cleanup fits situations like: tasks that involve Design review and critique; tasks that involve Code quality.
How do I install Cleanup in Claude Code?
Run `npx skills add simstudioai/sim --skill cleanup -a claude-code`. Or copy the skill folder (.agents/skills/cleanup in simstudioai/sim) into .claude/skills/cleanup in your project. Claude Code loads it when a task matches its description.
How do I install Cleanup in Codex?
Run `npx skills add simstudioai/sim --skill cleanup -a codex`. Or copy the skill folder (.agents/skills/cleanup in simstudioai/sim) into .agents/skills/cleanup in your project. Codex loads it when a task matches its description.
Can I use Cleanup in Cursor, Gemini CLI or GitHub Copilot?
Cursor, Gemini CLI, GitHub Copilot and OpenCode also load SKILL.md folders. With the skills CLI, run `npx skills add simstudioai/sim --skill cleanup -a cursor` (or -a gemini-cli, github-copilot or opencode for the others). To copy it by hand, put the folder in .cursor/skills/cleanup, .gemini/skills/cleanup, .github/skills/cleanup and .opencode/skills/cleanup in your project.
What does Cleanup need to run?
Going by SKILL.md and its folder, Cleanup needs the command-line tools its instructions call (git and bun).
Does Cleanup access the network?
SKILL.md contains no URLs. Its commands use git, which can reach the network depending on how they are called. This is read from the text; nothing was executed.
Is Cleanup safe to install?
Our automated static check of SKILL.md found no risky patterns, such as piping downloads into a shell, reading credential files or hidden Unicode. It is not a guarantee. Review the folder before installing.
What licence does Cleanup use?
Cleanup is published under the Apache-2.0 licence (the repository's licence). It allows redistribution, so the full SKILL.md is shown on this page.
How many tokens does Cleanup use?
About 1.4k tokens (SKILL.md is roughly 5.8k characters). Agents keep only the skill's name and description in context until a task matches; then they load SKILL.md in full.
What are the alternatives to Cleanup?
Skills that share tags, products or a category with Cleanup: Software Design Review (atilladeniz/Kubeli, 387 stars), Code Review (getsentry/skills, 1k stars), Improve App (wondelai/skills, 2.4k stars) and Design Evaluation (Abhinavbwj/Urban-Design-Skills-Claude, 132 stars). The comparison table on this page puts their stars, adoption, token cost, safety result and licence side by side.
Who maintains Cleanup?
simstudioai (a GitHub organization) maintains it in simstudioai/sim, which has 29,785 GitHub stars. The repository holds 40 skills in this directory. The repository was last updated on October 7, 2026.
Source: simstudioai/sim on GitHub. Facts on this page come from the repository at the commit we read; the author's words are quoted as theirs.