Why this skill exists. The same canon-break patterns recur across long-form fiction projects: a character's documented physical invariant gets accidentally inverted in a later chapter; an artifact moves room without explanation; a recurring character appears under a generic descriptor when an established proper name already exists; a count or age stated in the bible doesn't match what the text actually shows. Each break is cheap to catch at lint time and expensive to catch in print.

Use cases:

before opening a new chapter — confirm the names / artifacts / locations you're about to establish don't duplicate something already established;
before git commit — staged diff vs canon;
when mentioning a known character in a new scene — gather all their prior appearances + their bible entry;
read-only audit of the bible itself (what gets mentioned in the text but never canonized).

What the skill needs to know about your project:

where your chapter files live (any of .md / .tex / .txt / .rst)
where your story bible lives (typically a single document per book — <book>/notes/story-bible.{md,tex,txt} or similar)
which books are in the same series (so the skill can cross-reference inherited canon)

If the project follows the conventional layout (<book>/{lang}/chapters/* for chapters, <book>/notes/story-bible.* for the bible), the default routing works out of the box. Otherwise, override the routing patterns in references/routing.md.

canon-check