Extend Claude with skills changedskills
Nearest release: v2.1.238, published an hour before this site recorded the change. Shown because the two are within 24 hours of each other. Nothing here says the release caused the edit.
Recorded here
Lines+0added
Lines−2removed
From line
38
where the diff opens
First seen
14 Aug 2026
this site's first read of the page
Recorded edits80to this page, all time
The whole hunk
from line 38, old and new numbered
/
from line 38
3838| `/verify` | Build and run your app to confirm a code change does what it should, without falling back to tests or type checks |
3939| `/run-skill-generator` | Teach `/run` and `/verify` how to build and launch your project |
4040
41All three skills require Claude Code v2.1.145 or later. Check your version with `claude --version` or the `/status` command.
42
4341`/run` and `/verify` work without setup. They infer the launch from your project type (CLI, server, TUI, browser-driven) and from what's in your README, `package.json`, or `Makefile`. That inference gets unreliable for projects that need anything beyond a standard launch: a database, an env file, a graphical session, a multi-step build.
4442
4543`/run-skill-generator` records the recipe instead. It gets your app running from a clean environment, captures what worked (the install commands, the env vars, the launch script), and commits it as a per-project skill at `.claude/skills/run-<name>/`. After that, `/run`, `/verify`, and any other agent in the repo follow the recorded recipe instead of rediscovering it. Run `/run-skill-generator` once per project, and again if the build or launch process changes.
No line in this hunk matches that.