← ClaudeAtlas

stdd-lintlisted

STDD mechanical checker. A pure rule-based (non-model-judgment) checker that runs the 13 checks catalogued in references/checklist.md (placeholder/coverage/fingerprint/cross-artifact checks) against a single STDD change. Triggers: "/stdd-lint", or any stdd-* skill's boundary/coverage call.
twjohnwu/tlor-orchestration · ★ 0 · Code & Development · score 72
Install: claude install-skill twjohnwu/tlor-orchestration
# stdd-lint — Eagle Vision 鷹之視野 Opt-in skill (installed from `stdd-skills/`, not auto-loaded from the plugin's `skills/` directory). Internal reusable checker: called from the boundary-check steps of `stdd-spec`, `stdd-plan`, and `stdd-execute`, and also callable directly by the user. It is a **structural** checker for THIS framework's own spec/tasks placeholders, ID continuity, GWT completeness, coverage, fingerprint state, and cross-artifact reference consistency (REQ/S IDs, `api.yml` operations/fields, Mermaid DB-operation notes) against `design-be.md`/`design-fe.md`/`api.yml`/`tasks.md` — do not confuse this with third-party OpenAPI syntax/schema validation (e.g. `redocly`), which remains a separate concern referenced elsewhere and out of scope here; this skill only cross-references `api.yml`'s already-valid content against the other artifacts, it does not validate `api.yml` itself. Run every applicable check below against the target change's `STDD/<name>/` directory and return ONE combined report — do not stop at the first failing check. See `references/checklist.md` for a one-table summary of all 13 checks (trigger condition + FAIL condition, one row each). ## Check 1 — Placeholder text scan (S-26) Given `spec.md` or `tasks.md` exists, scan both (whichever exist) for: - `TBD`, `TODO`, `similar to Task N` (with no concrete content), unresolved/ dangling references, empty verification-command fields, and generic filler phrasing such as "add appropriate error hand