review

Coordinates phased code and documentation reviews generating a final readiness report.

Updated Feb 6, 2026
One-click install
npx skills add https://github.com/JoernStoehler/msc-math --skill review-joernstoehler
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: review
Source: https://github.com/JoernStoehler/msc-math/tree/main/.claude/skills/review
Command: npx skills add https://github.com/JoernStoehler/msc-math --skill review-joernstoehler

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This Skill provides a disciplined, multi-phase workflow for reviewing code and documentation before presenting deliverables to Jörn, ensuring syntax/style issues are addressed prior to semantic correctness.

Core Features & Use Cases

  • Phase-separated review: runs Phase 1 for syntax/style (e.g., LaTeX, Rust, Python) and Phase 2 for content correctness, with strict sequencing.
  • Concerns-driven checks: loads task checklists from references, and processes files in a controlled order.
  • On-demand subagents: coordinates with specialized subagents for inspection as needed.
  • Use Case: A deliverable containing TeX, Rust, and Python code gets verified across syntax, semantics, and documentation.

Quick Start

Start a phase-ordered review by spawning Phase 1 syntax/style checks across the target files, then advance to Phase 2 semantic checks, and generate a structured report.

Frequently Asked Questions about review

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

FAQPage Schema
How do I automate code review for mixed LaTeX and Rust deliverables?

Automated code review for mixed LaTeX and Rust deliverables runs a strict Phase 1 syntax and style check, then advances to Phase 2 semantic verification to isolate concerns. It loads task-specific checklists and spawns subagents to inspect target files in a controlled sequence.

What is a phased code-review workflow and when do I need it?

A phased code-review workflow separates syntax and style validation from semantic correctness to prevent cross-phase interference. You need this structured process when preparing complex deliverables containing TeX, Rust, or Python code for final presentation.

Does this code review workflow support Python documentation verification?

Yes, the code review workflow supports Python documentation verification by loading comprehensive checklists from its references directory. It coordinates specialized subagents during Phase 2 to evaluate content correctness alongside TeX and Rust files.

Can I use subagents to check LaTeX syntax independently from semantic content?

Yes, you can spawn phase-specific subagents to check LaTeX syntax independently during Phase 1. The strict phase sequencing ensures style issues are fully resolved before Phase 2 begins evaluating semantic content correctness.

What is the best way to structure a final readiness report for code and documentation?

The best way to structure a final readiness report is to execute a phase-ordered review, running syntax checks before semantic checks. The workflow compiles the isolated findings from each phase-specific subagent into a single structured report.

Why does my code review workflow enforce a strict Phase 1 then Phase 2 sequence?

The code review workflow enforces a strict Phase 1 then Phase 2 sequence to avoid cross-phase interference. Resolving syntax and style issues first ensures that Phase 2 subagents evaluate semantic correctness without being distracted by formatting errors.