| name | check-project-specs |
| description | Partial Skill: invoke by name only — project-spec/check-project-specs' engine that runs every project-spec check against the one spec governing the invoking package — the per-project CI entrypoint, not triggered by users directly. |
| user-invocable | false |
| metadata | {"internal":true} |
Check Project Specs
The per-project entrypoint for the project-spec checks. It resolves the one spec that governs
the invoking package and runs each project-spec engine against it, so a project's spec checks are a
task the project owns rather than a path some root script hardcodes. It carries a self-contained
.mts script (the repo's node-≥23.6 / no-deps convention).
Resolution — spec-first, never by name
A package knows its own directory; exactly one spec declares project-path pointing at it. The
engine inverts that map via discover-specs' collectSpecs:
- The project dir is the cwd (
--project <dir> overrides — the cwd is what a package-manager
script gives you for free).
- Walk up for
pnpm-workspace.yaml → the repo root.
- Match the repo-relative project dir against each spec's
project-path.
The reverse map is irregular and not derivable by name — plugins/cyberfleet is governed by
, and two different projects both own a skill named . Only
inverts reliably, which is why the spec stays the single source of truth for the
mapping and no path is ever written into a package's scripts.
