story-review

To validate narrative content for story consistency, review PRs that modify story documents, NPC definitions, and quests to identify cross-document inconsistencies. This enforces frontmatter presence, naming consistency, act progression logic, pronoun alignment, and bidirectional references.

Yes, you can review uncommitted local narrative changes for NPC and quest definitions without posting to GitHub. Running the review locally automatically switches to local mode, outputting validation results inline rather than publishing them to a remote repository.

Validation checks applied to story documents and city/dungeon designs include enforcing frontmatter presence, naming consistency, act progression logic, pronoun alignment, and bidirectional references. This cross-document validation ensures story, NPC, and location coherence.

To post automated narrative review results directly to a GitHub PR, invoke the review process using a PR URL. This activates PR mode, automatically validating narrative content changes and posting the consistency check results as feedback to the GitHub pull request.

Yes, story content validation works for both published GitHub PRs and local unpushed changes. The system features automatic mode detection, switching between posting review results to GitHub or displaying inline results based on whether a PR URL is provided.

You should use automated cross-document validation for narrative content when modifying story documents, NPC definitions, quests, or city/dungeon designs. It prevents broken bidirectional references and maintains act progression logic before merging narrative changes.