review-fix-typst-diagrams

Automates iterative Typst diagram review and fix cycles until zero critical/warning findings remain.

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

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Iterative review and fix convergence loop for Typst diagrams. Fix until critical + warning = 0.

Core Features & Use Cases

  • Per-round review with a standard checklist for Typst diagrams
  • Automated convergence checks until critical + warning = 0, followed by build verification
  • Use Case: Apply this workflow to large Typst diagram libraries to maintain quality across rounds

Quick Start

Run a round-based Typst diagram review-and-fix loop until all critical and warning findings are resolved.

Frequently Asked Questions about review-fix-typst-diagrams

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

FAQPage Schema
How do I automate Typst diagram review and fix convergence to zero issues?

Automate Typst diagram review by running an iterative fix loop that applies a standard checklist, counts critical and warning findings, and verifies convergence to zero issues through compilation checks.

What is the best way to verify Typst diagram builds after fixing review findings?

Verify Typst diagram builds by enforcing round-based checkpoints that run typst compile after applying fixes, ensuring the iterative review loop converges with zero critical and warning findings.

Can I apply iterative diagram review to a specific Typst directory scope?

Apply iterative diagram review to a defined Typst directory scope using glob patterns, executing per-round reviews and convergence checks until all critical and warning findings are resolved.

How does the round-based convergence loop work for Typst diagram projects?

The convergence loop works by executing per-round reviews against a standard checklist, counting issues, applying fixes, and running build verification until critical and warning findings reach zero.

Do I need any external dependencies to run Typst diagram build verification?

No external dependencies are required to run Typst diagram build verification, as the workflow uses standard typst compile commands within its per-round checkpoints to enforce convergence rules.