设计与 UI
logic-review
Review stable chapter or manuscript drafts for paragraph flow, transitions, argument continuity, and repeated rhetorical functions before editing. Use after the author-approved spine is stable; route structural drift back to thesis-control.
yha9806 · 已有静态检查记录
安装与使用
运行命令前先阅读来源与依赖说明。复制命令不会自动安装或执行。
npx skills add yha9806/academic-writing-toolkit --skill logic-review技能说明
name: logic-review description: Review stable chapter or manuscript drafts for paragraph flow, transitions, argument continuity, and repeated rhetorical functions before editing. Use after the author-approved spine is stable; route structural drift back to thesis-control. allowed-tools: Read, Glob, Bash, Edit
/logic-review — Paragraph Logic Review
Purpose
Find paragraphs that may need a topic sentence, a clearer transition, merging, re-ordering, or removal of duplicated argumentative work. The deterministic script flags mechanical candidates; the agent separately reviews rhetorical functions without redefining the manuscript spine.
Trigger Words
This skill activates on: logic review, flow check, paragraph logic, /logic-review.
Workflow
- Run:
python3 scripts/audit-logic.py --base-dir . --json - Confirm that the research object, core question, intended use, primary
experiment, headline claim, and evidence boundary are stable under the
active
/thesis-controlcontract. If they are not, stop the language pass and route the issue to drift control or revision escalation. - Read the flagged paragraphs and nearby context.
- Label each relevant sentence or paragraph by its main function:
problem,gap,method,evidence,interpretation,boundary, ortransition. - Flag duplicated functions and monotonous sequences, especially repeated
evidence -> disclaimerendings. Prefer deleting or consolidating repeated argumentative work over generating synonymous wording. - Check boundary placement. Scope must remain aligned across the paper, but full limitation prose need not be repeated after every result. Preserve essential local qualifiers and concentrate fuller study-boundary language in the abstract ending, Methods boundary, Discussion/Limitations, and conclusion when appropriate.
- Present a numbered review table with location, function, issue type, why it matters, and a proposed edit.
- Wait for user approval before editing chapter files.
- Apply only approved edits, then re-run the audit.
Constraints
- Never auto-fix chapter logic without user approval.
- Preserve the author's argument and section structure.
- Keep edits local to the flagged paragraph unless the user approves a broader rewrite.
- Do not use a logic or style pass to repair an unstable research question, evidence chain, application purpose, or contribution order.
- No emoji.