running-check-scriptlisted

# Running the `check` Script This skill is the **single source of truth** for executing the `package.json` `check` script in lt-dev workflows. Every reviewer, rebaser, and orchestrator that needs to guarantee project runnability must follow this procedure verbatim — duplicating the rules across agents leads to drift. > **Goal:** A truly green `check` run (exit 0) is a non-negotiable prerequisite for any review or rebase to be considered complete. The only acceptable residual is an upstream dependency vulnerability where the full fix escalation ladder has been exhausted. ## When to Use This Skill | Caller | Phase | Trigger | |--------|-------|---------| | `/lt-dev:review` | Phase 1.5 | Before spawning any specialized reviewer | | `lt-dev:code-reviewer` | Phase 1.5 | Before single-pass review (skip if orchestrator already ran it) | | `lt-dev:branch-rebaser` | Phase 6.5 | After lint/format, before tests | | `lt-dev:test-reviewer` | (input briefing) | Honors the skip semantics defined here | ## Procedure ### Step 1 — Discover `check` scripts Use the dedicated helper script (located in the lt-dev plugin): ```bash bash "${CLAUDE_PLUGIN_ROOT}/scripts/discover-check-scripts.sh" "$(pwd)" ``` Output is TSV, one project per line: ``` <package.json path>\t<check script>\t<includes_tests:yes|no>\t<package manager> ``` The helper: - Uses `git ls-files "package.json" "**/package.json"` so it respects `.gitignore` and skips `node_modules` - Parses JSON via `jq` → `node -e` → `grep