القائمة
Show help for the book review pipeline
التثبيت باستخدام Codex أو Claude انسخ هذا Prompt والصقه في Codex أو Claude أو مساعد آخر ليراجع صفحة Skill ويثبّتها لك.
استنادا إلى تصنيف SOC المهني
Explicitly invoked only. Authoritative reference for the Ragu formal-verification project — Clean DSL semantics (Circuit monad, Expression, Operation, ProvableType, FormalCircuit) and Ragu-side concepts (extraction driver, formal instances, input/output serialization, assumptions, CI). Routes to the live in-tree FV docs; the docs are the spec, not opinion. Pair with /fv-review for opinion / pattern-matching guidance. Invoke when the user types `/fv-docs` or asks for the canonical definition of a Clean / Ragu-FV concept.
Explicitly invoked only. Lessons learned from porting Ragu Rust circuits to Clean Lean formal verification reimpls — when not to formalize an empty circuit, picking FormalCircuit vs FormalAssertion vs GeneralFormalCircuit, mirroring Rust delegation, length polymorphism, naming conventions, and reading proof failures (stuck goals, hypotheses you're forced to add) as under-constraint / undocumented-precondition bug signals. Distilled from PR review feedback (mitschabaude et al.) and refined over time. Do NOT auto-trigger on general formal verification, Lean, or Ragu questions; only invoke when the user explicitly types `/fv-review` or asks by name.
Explicitly invoked only. Loads context for the Verified-zkEVM `clean` codebase — an embedded Lean DSL for formally verified zk circuits (AIR/PLONK/R1CS) with Circuit monad, ProvableType/ProvableStruct, FormalCircuit (soundness/completeness), and gadget composition. Do NOT auto-trigger on general Lean, ZK, or circuit questions; only invoke when the user explicitly types `/clean-circuits` or asks by name to use this skill.
Review any part of the book using parallel specialist agents
Review code using parallel specialist agents
Audit documentation surface placement (book vs. rustdoc) and refine the policy
| name | help-book-review |
| description | Show help for the book review pipeline |
| user-invocable | true |
Print the following help text exactly, then stop. Do not add commentary.
Three skills, one feedback loop:
/book-review — review any part of the book
/book-refine — improve the review system based on your feedback
/doc-audit — audit book vs. rustdoc surface placement
/book-review review uncommitted changes
/book-review book/src/guide/gadgets/ review a whole section
/book-review book/src/protocol/core/nark.md review a specific chapter
/book-review book/src/protocol/core/nark.md:40-80 focus on specific lines
/book-review book/src/protocol/prelim/bulletproofs.md book/src/protocol/core/nark.md
review multiple files + cross-file consistency
/book-review "accumulation schemes" find and review a topic wherever it appears
/book-review "the transition from preliminaries to core construction"
review a conceptual boundary across chapters
Launches one parallel agent per policy file in .claude/book-review/. Currently:
grammar, prose, structure, math, formatting. Results are
synthesized and presented as must-fix issues first, then suggestions.
After a review, give feedback in natural language, then:
/book-refine use feedback from the conversation
/book-refine "stop flagging passive voice in definitions"
/book-refine "I'd write 'the prover' not 'a prover'"
/book-refine "add a reviewer for code example accuracy"
This enters plan mode — it reads all policies, generalizes your feedback into
a principle, audits for duplication/contradictions, and shows you the proposed
changes before executing. New policy files are auto-discovered by /book-review.
.claude/review-shared/writing.md shared writing rules (grammar + prose reviewers)
.claude/review-shared/math.md shared math notation rules (math reviewer)
.claude/review-shared/surface-placement.md book vs. rustdoc placement policy
.claude/book-review/standards.md master standards (all reviewers)
.claude/book-review/grammar.md book-specific grammar rules
.claude/book-review/prose.md transitions, terminology appendix
.claude/book-review/structure.md organization, flow, progressive disclosure
.claude/book-review/math.md notation, correctness, accessibility
.claude/book-review/formatting.md line width, headings, code blocks
.claude/book-review/formatting-examples.md concrete before/after examples
Edit these directly or let /book-refine manage them.