baseline

# project-baseline ## Overview A **testable readiness standard**: 90 rules, each backed by a check a zero-dependency Node runner executes on a repo *at rest*. Blockers fail CI (`exit 1`); the judgment calls a script can't make resolve via a dated **sign-off ledger**. The throughline: *don't trust a written promise — make something check it.* A checklist doc drifts; this is the checklist as an exit code. Runs natively under **Hermes** and **Claude Code** (and any agent that loads `SKILL.md`). The runner is portable — plain Node, no agent-specific dependency. Source: `github.com/AdarGit008/baseline-skill` (reference repo: `baseline-demo`). ## When to Use - "run baseline", "score this repo", "check build-readiness / project-readiness" - "audit this repo against a standard", "is this build-ready?" - "set up / adopt / scaffold baseline here" - "fix the baseline failures", "get this to green" - "what does SEC-03 check", "why did CTX-05 fail" **Don't use for:** general logic/bug review (use a code-review skill) or writing tests (use a TDD skill). Baseline checks *readiness posture at rest*, not runtime correctness. ## Setup — resolve the toolkit path first `$SKILL_DIR` = the absolute path of the directory containing this file. Resolve it to a concrete path before running anything (never pass the literal `$SKILL_DIR` to the shell). Typical locations: - Hermes: `~/.hermes/skills/software-development/baseline` - Claude Code: `~/.claude/skills/baseline` The unified CLI is **`ba...