review-typst

Review Typst files for logic, citations, cross-references, and compilation issues.

Updated Jan 20, 2026
One-click install
npx skills add https://github.com/yannickloth/health-me-cfs --skill review-typst
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: review-typst
Source: https://github.com/yannickloth/health-me-cfs/tree/main/.claude/skills/review-typst
Command: npx skills add https://github.com/yannickloth/health-me-cfs --skill review-typst

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Typst documents often suffer from logical inconsistencies, missing or incorrect citations, and cross-reference or compilation issues. This skill provides a structured, iterative review workflow to surface and fix these problems before publishing.

Core Features & Use Cases

  • Iterative review cycles: R1, R2, ..., progressively audit changes and new issues.
  • Comprehensive audits: assess logic, citation accuracy, symbol consistency, cross-references, and Typst syntax.
  • Build verification: ensure Typst compiles after fixes to validate changes.

Quick Start

Run the review workflow on your Typst project to start the first adversarial review round across the specified scope.

Frequently Asked Questions about review-typst

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I check Typst documents for citation and cross-reference errors?

An iterative adversarial review audits Typst files to surface logical gaps, citation misalignments, and syntax or cross-reference issues. It progressively reviews changes across rounds until issues converge to zero or a maximum limit is reached.

How do I verify that my Typst project compiles after fixing documentation issues?

The review workflow includes build verification that executes Typst compilation after fixes to validate changes. This ensures the document compiles successfully once logical gaps, citation misalignments, and cross-reference issues are resolved.

Can I run a code review on a specific directory within my Typst project?

Yes, you can run a review on a specific directory within your Typst project. The adversarial review workflow operates over a defined scope such as specific directories or the entire project scope.

What is an iterative adversarial review for Typst files?

An iterative adversarial review for Typst files is a structured workflow that progresses through multiple review rounds (R1, R2, etc.) to progressively audit logic, citation accuracy, symbol consistency, and Typst syntax until issues converge to zero or a maximum round limit is reached.

Why does my Typst document fail to compile after updating cross-references?

Your Typst document may fail to compile after updating cross-references due to invalid reference targets or syntax misalignments. An adversarial review validates cross-references and executes Typst compilation to catch these exact compilation failures.

Do I need a references.bib file to review Typst citations?

Yes, you need a references.bib file to review Typst citations. The review workflow explicitly enforces that all citations exist in references.bib to ensure citation accuracy and prevent missing reference errors during compilation.