Roadmap
cloudposse/atmos
Maintain and update the Atmos roadmap page (website/src/data/roadmap.js): milestone/initiative/quarter schema, progress-percentage math, the curated featured[] cap (max 6, never auto-modified), and…
Gating migrations and clean-up code behind an update milestone.
Install Version Bound Cleanup
$ npx skills add pdparchitect/noodle --skill version-bound-cleanup -a claude-codeProject install by default; add -g for ~/.claude/skills/.
$ gh skill install pdparchitect/noodle version-bound-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/pdparchitect/noodle.git skills-src && mkdir -p .claude/skills && cp -r skills-src/.agents/skills/version-bound-cleanup .claude/skills/version-bound-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 "version-bound-cleanup" agent skill from https://github.com/pdparchitect/noodle/tree/main/.agents/skills/version-bound-cleanup into .claude/skills/version-bound-cleanup/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "version-bound-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/pdparchitect/noodle/tree/main/.agents/skills/version-bound-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 pdparchitect/noodle --skill version-bound-cleanup -a codexProject install goes to .agents/skills/; add -g for ~/.codex/skills/.
$ gh skill install pdparchitect/noodle version-bound-cleanup --agent codexProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/pdparchitect/noodle.git skills-src && mkdir -p .agents/skills && cp -r skills-src/.agents/skills/version-bound-cleanup .agents/skills/version-bound-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 "version-bound-cleanup" agent skill from https://github.com/pdparchitect/noodle/tree/main/.agents/skills/version-bound-cleanup into .agents/skills/version-bound-cleanup/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "version-bound-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 pdparchitect/noodle --skill version-bound-cleanup -a cursorProject install goes to .agents/skills/; add -g for ~/.cursor/skills/.
$ gh skill install pdparchitect/noodle version-bound-cleanup --agent cursorProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/pdparchitect/noodle.git skills-src && mkdir -p .cursor/skills && cp -r skills-src/.agents/skills/version-bound-cleanup .cursor/skills/version-bound-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 "version-bound-cleanup" agent skill from https://github.com/pdparchitect/noodle/tree/main/.agents/skills/version-bound-cleanup into .cursor/skills/version-bound-cleanup/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "version-bound-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/pdparchitect/noodle.git --path .agents/skills/version-bound-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 pdparchitect/noodle --skill version-bound-cleanup -a gemini-cliProject install goes to .agents/skills/; add -g for ~/.gemini/skills/.
$ gh skill install pdparchitect/noodle version-bound-cleanup --agent gemini-cliProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/pdparchitect/noodle.git skills-src && mkdir -p .gemini/skills && cp -r skills-src/.agents/skills/version-bound-cleanup .gemini/skills/version-bound-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 "version-bound-cleanup" agent skill from https://github.com/pdparchitect/noodle/tree/main/.agents/skills/version-bound-cleanup into .gemini/skills/version-bound-cleanup/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "version-bound-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 pdparchitect/noodle version-bound-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 pdparchitect/noodle --skill version-bound-cleanup -a github-copilotProject install goes to .agents/skills/; add -g for ~/.copilot/skills/.
$ git clone --depth 1 https://github.com/pdparchitect/noodle.git skills-src && mkdir -p .github/skills && cp -r skills-src/.agents/skills/version-bound-cleanup .github/skills/version-bound-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 "version-bound-cleanup" agent skill from https://github.com/pdparchitect/noodle/tree/main/.agents/skills/version-bound-cleanup into .github/skills/version-bound-cleanup/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "version-bound-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 pdparchitect/noodle --skill version-bound-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 pdparchitect/noodle version-bound-cleanup --agent opencodeProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/pdparchitect/noodle.git skills-src && mkdir -p .opencode/skills && cp -r skills-src/.agents/skills/version-bound-cleanup .opencode/skills/version-bound-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 "version-bound-cleanup" agent skill from https://github.com/pdparchitect/noodle/tree/main/.agents/skills/version-bound-cleanup into .opencode/skills/version-bound-cleanup/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "version-bound-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
version-bound-cleanup- GitHub stars
- 141
- Token cost
- ~650 tokens
- SKILL.md length
- 329 words
- Files
- 1
- Skills in repo
- 8
- Repo updated
- First seen
- Licence
- Apache-2.0
At a glance
Gating migrations and clean-up code behind an update milestone.
- Works in 6 steps: Find the app whose release ships the… → The milestone is that app's next… → Add the milestone to the app's… → …
- Writing code that moves
- SKILL.md covers When writing a migration and When asked what can be removed
- Instructions only: no scripts, shell commands, URLs or credentials in SKILL.md
What it does
Version Bound Cleanup is an agent skill from pdparchitect/noodle. Gating migrations and clean-up code behind an update milestone. Use when writing code that moves, renames, rewrites or deletes data left by an earlier version, reads an old format, or backfills a new field for existing data, in Noodle, Hub, Applet, Computer, Browser or Mobile; and when asked what clean-up code can be removed.
Its SKILL.md is about 650 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 Product & Project Management, covering Project management and Refactoring. The licence is Apache-2.0.
When your agent uses it
- Writing code that moves
- Deletes data left by an earlier version
- Reads an old format
- Backfills a new field for existing data
Example prompts
- “/version-bound-cleanup”
Workflow steps
6 steps, taken from the first numbered list in SKILL.md.
- Find the app whose release ships the code: its VERSION and changelog. Shared code
- The milestone is that app's next release: the dated section still being prepared,
- Add the milestone to the app's Support/update-milestones.json, in ascending order.
- Mark the code, its call site and its tests with the release that may delete it,
- Never write TODO(NEXT_VERSION) or a TODO without a milestone behind it.
- Mention the milestone in the report to the user; it forces an upgrade step on them.
What it can do on your machine
Read from SKILL.md and the folder at commit 515f964. 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
No scripts in the folder and no shell commands in SKILL.md (its code samples are swift).
From the folder's file list and the shell code blocks in SKILL.md.
Network
No URLs in SKILL.md.
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
Version Bound Cleanup loads about 650 tokens when it runs. Until then it costs about 87 tokens; SKILL.md has 329 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 pdparchitect/noodle at commit 515f964, republished under its Apache-2.0 licence (© pdparchitect). 329 words, ~650 tokens.
Download SKILL.mdSave it as
.claude/skills/version-bound-cleanup/SKILL.md (or your agent's skills folder).- name
- version-bound-cleanup
- description
- Gating migrations and clean-up code behind an update milestone. Use when writing code that moves, renames, rewrites or deletes data left by an earlier version, reads an old format, or backfills a new field for existing data, in Noodle, Hub, Applet, Computer, Browser or Mobile; and when asked what clean-up code can be removed.
Version-bound clean-up
A migration runs only for people who install the release that ships it. Sparkle lets people skip releases, so every migration is tied to an update milestone: a release people must run before any later one. The code lives until the release after the milestone, then goes.
The milestone mechanism is described in docs/releases.md,
under Update milestones. Read it first.
When writing a migration
Find the app whose release ships the code: its
VERSIONand changelog. Shared code underSources/ships with every app that runs it; gate it for each one.The milestone is that app's next release: the dated section still being prepared, otherwise the next version after
VERSION. Ask if unsure which.Add the milestone to the app's
Support/update-milestones.json, in ascending order. Create the file for an app that has none; release packaging picks it up.Mark the code, its call site and its tests with the release that may delete it, the one after the milestone:
swift // TODO(Hub 0.7.0): remove with its call in HubBots.init and // HubTests.testBotsFromBeforeGetTheirOwnerWhenTheHubOpens. Milestone: Hub 0.6.0.Name the app unless it is Noodle; version numbers differ between apps. Name every call site and test so removal is one pass.
Never write
TODO(NEXT_VERSION)or a TODO without a milestone behind it.Mention the milestone in the report to the user; it forces an upgrade step on them.
Mobile ships through the App Store, which has no milestones. Ask the user how long a Mobile migration stays.
Where skipping the milestone could damage data, keep a startup check that names the release to run first instead of deleting the code outright.
When asked what can be removed
grep -rn 'TODO(' --include='*.swift'outside.build, and compare each with its app'sVERSIONand milestones file.- Removable: the named release is at or below the next one, and the milestone it depends on is listed and published.
- Flag anything overdue, and any
TODO(NEXT_VERSION)or migration with no milestone. - Removing it follows the TODO: the code, its call sites and its tests, together.
© pdparchitect, 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/version-bound-cleanup of pdparchitect/noodle.
Open the folder on GitHubat commit 515f964
Compare with similar skills
Version Bound 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 |
|---|---|---|---|---|---|---|
| Version Bound Cleanup this skillpdparchitect/noodle | 141 | — | ~650 | Automated safety check: Pass | Apache-2.0 | |
| Roadmapcloudposse/atmos | 1.4k | — | ~2.5k | Automated safety check: Pass | Apache-2.0 | |
| Project Final Reviewfirehol/iprange | 241 | — | ~1.2k | Automated safety check: Pass | Custom licence | |
| Maintainability Reviewpmndrs/glyph | 392 | — | ~1.7k | Automated safety check: Pass | MIT | |
| CCPM Project Managementautomazeio/ccpm | 8.4k | — | ~1.1k | Automated safety check: Pass | MIT | |
| Dough Execute Planterryyin/lizard | 2.5k | — | ~4.3k | Automated safety check: Pass | Custom licence |
Similar skills
Project Final Review
firehol/iprange
Perform independent adversarial final reviews of milestones, releases, migrations, refactors, fixes, close-outs, and other work claimed ready, complete, production-grade, accepted, or safe to proceed.
Maintainability Review
pmndrs/glyph
Audit and improve repository code milestone by milestone for correctness, clarity, local reasoning, DRY design, explicit state modeling, panic resistance, and trustworthy TypeScript boundaries.
CCPM Project Management
automazeio/ccpm
Runs a spec-driven workflow from PRD to epic to GitHub issues to parallel agents, with status, standup and blocked-work reports from bundled scripts.
Dough Execute Plan
terryyin/lizard
Executes one selected story or bounded retrospective correction through an executable plan, or one authorized planless slice from a selected simple story or a contextual instruction, with…
Ichartjs
wanghetommy/ichartjs
Plan, validate, render, explain, and safely edit iChart.js visualizations from tabular, project, or diagram data.
More from pdparchitect/noodle
All 8 skills in this repoAgents Md Symlink
pdparchitect/noodle
Every AGENTS.md must have a sibling CLAUDE.md symlink pointing to it.
UI Copy
pdparchitect/noodle
Rules for user-visible text and controls in the Noodle apps.
Helper Visibility
pdparchitect/noodle
Dock and app-switcher policy for Noodle helpers. An agent skill from pdparchitect/noodle.
Mint Release
pdparchitect/noodle
Procedure for minting or publishing a version of Noodle, Computer, Applet, Browser, Hub or the Computer images.
No Code Docs
pdparchitect/noodle
Code is documented only in the source. An agent skill from pdparchitect/noodle.
Apple History Utilities
pdparchitect/noodle
Upkeep of the Apple utilities copied into NoodleAppleRuntime.
Related
Questions about Version Bound Cleanup
What does Version Bound Cleanup do?
Gating migrations and clean-up code behind an update milestone. Version Bound Cleanup is an agent skill from pdparchitect/noodle. Gating migrations and clean-up code behind an update milestone.
When should I use Version Bound Cleanup?
Version Bound Cleanup fits situations like: writing code that moves; deletes data left by an earlier version; reads an old format; backfills a new field for existing data.
How do I install Version Bound Cleanup in Claude Code?
Run `npx skills add pdparchitect/noodle --skill version-bound-cleanup -a claude-code`. Or copy the skill folder (.agents/skills/version-bound-cleanup in pdparchitect/noodle) into .claude/skills/version-bound-cleanup in your project. Claude Code loads it when a task matches its description.
How do I install Version Bound Cleanup in Codex?
Run `npx skills add pdparchitect/noodle --skill version-bound-cleanup -a codex`. Or copy the skill folder (.agents/skills/version-bound-cleanup in pdparchitect/noodle) into .agents/skills/version-bound-cleanup in your project. Codex loads it when a task matches its description.
Can I use Version Bound 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 pdparchitect/noodle --skill version-bound-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/version-bound-cleanup, .gemini/skills/version-bound-cleanup, .github/skills/version-bound-cleanup and .opencode/skills/version-bound-cleanup in your project.
What does Version Bound Cleanup need to run?
SKILL.md names no scripts, command-line tools or credentials: Version Bound Cleanup is instructions for the agent only.
Does Version Bound Cleanup access the network?
SKILL.md contains no URLs. Any network use would come from the scripts or tools the agent runs. This is read from the text; nothing was executed.
Is Version Bound 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 Version Bound Cleanup use?
Version Bound 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 Version Bound Cleanup use?
About 650 tokens (SKILL.md is roughly 2.6k 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 Version Bound Cleanup?
Skills that share tags, products or a category with Version Bound Cleanup: Roadmap (cloudposse/atmos, 1.4k stars), Project Final Review (firehol/iprange, 241 stars), Maintainability Review (pmndrs/glyph, 392 stars) and CCPM Project Management (automazeio/ccpm, 8.4k stars). The comparison table on this page puts their stars, adoption, token cost, safety result and licence side by side.
Who maintains Version Bound Cleanup?
pdparchitect (a GitHub user) maintains it in pdparchitect/noodle, which has 141 GitHub stars. The repository holds 8 skills in this directory. The repository was last updated on October 7, 2026.
Source: pdparchitect/noodle on GitHub. Facts on this page come from the repository at the commit we read; the author's words are quoted as theirs.