julien-ref-doc-review

Tag-based documentation review uses four core tags—@FIX, @TODO, @VERIFY, @OK—to annotate documents with actionable signals. Assign tags to specific sections, optionally flag systemic changes with [MACRO], then parse the annotations to generate a consolidated review plan and impact analysis.

Yes. Tag-driven review applies to technical documents, API references, user guides, and policy papers. It handles both micro edits and macro systemic changes, making it suitable for API docs where consistency and cross-reference verification matter.

@FIX addresses immediate, localized edits to specific content. [MACRO] flags changes with broader systemic impact across multiple files or sections, triggering cross-file impact analysis and wider validation to prevent unintended downstream effects.

Claude-driven parsing extracts tagged annotations from your document, generates a structured review plan, performs cross-file impact analysis, and proposes specific changes with verification steps—eliminating manual synthesis and surfacing dependencies you might miss.

Yes. The @VERIFY tag marks content requiring validation against authoritative sources. During parsing, Claude identifies all @VERIFY instances, generates verification requirements, and produces a report showing which sections need source confirmation before committing changes.

Yes. The Skill supports markdown annotation. Embed tags as comments within your markdown file—@FIX, @TODO, @VERIFY, @OK—then use the review document prompt to parse annotations and generate a change proposal report in markdown-compatible format.