Skip to content

0.2.1

Latest
Latest

Choose a tag to compare

View all tags
@hallikkristjan-code hallikkristjan-code released this 06 Nov 22:43
v0.2.1
041cfba

Upgrade from 0.2.0. If you installed the skill into a project with npx skills add, 0.2.0 gave you wrong results: it read its own code as yours.

Found by following the README in a clean session on a fresh create-next-app project, and by running the probe on 34 local repositories.

Wrong results in 0.2.0, fixed

  • The probe read itself. A skill installed in .agents/skills, .claude/skills or any other agent's skills/ folder counted as the app's code. Gates 6, 9 and 12 passed on it, and fix then skipped the health route. Installed skills are now left out.
  • fix did nothing through a link. Started through .claude/skills, which links to .agents/skills, fix.mjs printed nothing, wrote nothing and exited 0. It now runs.
  • Gate 7 refused rehearsed drills. It knew four English labels. Any label in any language now counts, unless it names a plan (Next, Planned, Due).
  • Gate 4 refused a real date. (due: 2027-01-24, earlier if convenient) was reported as invalid. An impossible date still is.
  • A readable pyproject.toml was reported as unread. Plain Python libraries got "stage not detected".

Faster

Following imports now visits each file once, and each file is read once. One repository went from 40 s to 0.3 s, another from 53 s to 2.5 s.

New check

Gate 3 fails when .gitignore hides .env.example, as create-next-app's .env* does, because nobody who clones the repo gets it. It names the line to add, !.env.example, and you add it yourself: fix does not edit .gitignore.

Expect this on a fresh project

A new create-next-app has no test script, so fix does not write the CI workflow and the project stops at 3 of 4 required gates until you add one. That is on purpose: CI with no tests in it would be a green light that means nothing.

Checked, and not checked

  • 223 tests on Ubuntu and Windows with Node 20, 22 and 24.
  • The README in a clean Claude Code session and in Codex, then a typecheck and a production build of the generated project on Next.js 16.4.5.
  • Not checked: the generated workflows on GitHub Actions, the rollback and restore guides on a real Supabase project, macOS.

Full list: CHANGELOG.md

Assets 2
Loading