Validate devbook Markdown chapters against the schema and repair reported metadata errors.
npx skills add https://github.com/JSdotNet/devbook --skill validate-jsdotnet
Please help me install this Agent Skill. Skill: validate Source: https://github.com/JSdotNet/devbook/tree/main/plugins/devbook/skills/validate Command: npx skills add https://github.com/JSdotNet/devbook --skill validate-jsdotnet
node .devbook/_tools/devbook-meta/build.mjs --check to parse every chapter and report unresolved references and schema violations with exit codes. - Guided Repair: Maps each reported symptom — dangling references, missing meta blocks, duplicate numbers, bad status or type values, malformed annotations — to the correct fix in the authored Markdown. - CI Triage: Explains why CI can fail when local checks pass, such as references breaking only in the merge result of two clean branches. - Use Case: When a pull request fails the devbook-meta check, run this Skill to identify the broken related reference, repoint it at the renamed chapter, and re-run the check until it exits 0. ## Quick Start Run devbook validate on this repository and fix every broken reference and malformed meta block the check reports.High-intent search queries and answers about installing and using this skill.
Run `node .devbook/_tools/devbook-meta/build.mjs --check` from the repository root. Exit code 0 means every reference resolves and every meta block matches the schema; exit code 1 lists problems to fix in the source Markdown.
Repoint the `related`, `depends-on`, or `refines` field at the real chapter, or remove it if the relationship is gone. Never delete the target chapter to silence the error, and never hand-edit generated files under `_meta/`.
CI fails only on unresolved references or schema violations in the authored Markdown, never on drifted `_meta/` indexes, which produce warnings. Compare against the merge result, since a reference can break when two individually clean branches land together.
It never checks installation state such as stamp drift or outstanding migrations, which belong to `devbook:update`. It also never refreshes generated `_meta/` indexes or applies migrations; those are handled by the paths named in the repository's AGENTS.md.
Restore it by running `devbook:update`, or `devbook:init` where devbook has no stamp yet. Copying the tool files by hand lands them unstamped, so the next reconcile cannot distinguish them from customized files.
DarkbluelrOrchestrate DevBooks delivery from Proposal to Archive with SSOT routing and gate checks.
posit-devUpdates an existing pull request with new commits and revised metadata.
element22llcApply pending structural migrations and reconcile spec spine and scaffold against current templates.
learnn-comRecords technical decisions as ADR or ADL files and updates adoption documentation.