sumeru-review

Compare original and translation side by side

🇺🇸

Original

English

🇨🇳

Translation

Chinese

网文逻辑审查

Web Novel Logic Review

触发关键词

Trigger Keywords

帮我检查下小说有没有bug、看看时间线有没有矛盾、人物有没有OOC、找剧情前后冲突、梳理伏笔有没有回收、检查小说剧情合理性、看看有没有剧情漏洞、人物行为不符合性格、检查时间线对不对、找小说前后矛盾的地方、帮我梳理所有伏笔、小说剧情bug检查、逻辑漏洞排查、小说剧情审查

Help me check if there are bugs in my novel, Check if there are timeline contradictions, Check if characters are OOC, Find plot conflicts between different parts, Sort out whether foreshadowings are resolved, Check the rationality of novel plots, Check if there are plot loopholes, Character behaviors are inconsistent with their personalities, Check if the timeline is correct, Find contradictions in the novel, Help me sort out all foreshadowings, Novel plot bug check, Logical loophole troubleshooting, Novel plot review

核心功能

Core Features

三阶段审查修复流程设计

Three-Stage Review and Repair Process Design

为确保审查全面性和修复质量，本 skill 采用三阶段审查修复流程：

第一阶段：全局信息审查

加载完整大纲和章节细纲，建立全局审查基准
分析整体剧情脉络和时间线结构
审查全局设定一致性（世界观、力量体系、规则设定）
识别主线支线关联问题和伏笔回收情况
检查整体冲突点分布和节奏把控
记录全局问题清单到
```
.sumeru/review/global-issues.json
```

第二阶段：章节细节审查（Agent Team 并行）

使用多 Agent 并行处理，每个 Agent 负责一定数量的章节
⚠️ 遵循全局约束：每个子Agent最多负责3个章节（详见 AGENTS.md "子Agent并行处理规则"）
所需Agent数 = ceil(总章节数 / 3)，分配策略为按章节顺序连续分配
为每章生成核心剧情概要（去掉细节，仅保留关键事件）
对每章进行详细审查：
- 字数统计与填充需求识别
- 时间线与事件时序验证
- 人物行为与性格一致性（OOC检测）
- 物品状态与信息边界检查
- 场景描写与对话质量评估
- 伏笔设置与回收状态
生成章节概要到
```
.sumeru/review/summaries/
```
目录
记录章节问题清单到
```
.sumeru/review/chapter-issues/
```
目录
支持断点续传，已审查章节可跳过

第三阶段：统一修复执行

合并全局问题和章节问题，按严重程度排序（致命 > 严重 > 中等 > 轻微）
制定并执行修复计划，分为两种修复类型：
- 轻量修复（review 直接执行）：文字修正、段落调整、语句优化、字数填充等 minor 修改，直接修改
  chapters/
  文件（修改前自动备份到
```
.sumeru/write/original/
```
  ）
- 重写修复（标记待处理）：剧情逻辑严重矛盾、大面积OOC、设定崩坏等需要重写的章节，记录到修复计划
执行轻量修复策略：
- 全局问题修复：调整整体时间线、统一设定、优化主线结构
- 章节问题修复：逐章修复字数、逻辑、OOC、剧情矛盾等轻量级问题
- 联动修复：处理跨章节的关联问题（如伏笔回收、人物成长）
生成修复报告到
```
.sumeru/review/fix-report.json
```
生成修复计划
```
fix-plan.json
```
，标记需要重写的章节及具体修复建议
修复后重新审查，验证所有轻量修复问题已彻底解决

To ensure comprehensive review and repair quality, this Skill adopts a three-stage review and repair process:

Phase 1: Global Information Review

Load complete outline and chapter detailed outlines to establish a global review benchmark
Analyze the overall plot context and timeline structure
Review consistency of global settings (worldview, power system, rule settings)
Identify issues with main and subplot correlations and foreshadowing resolution status
Review overall conflict distribution and rhythm control
Record global issue list to
```
.sumeru/review/global-issues.json
```

Phase 2: Chapter Detail Review (Agent Team Parallel Processing)

Use multiple Agents for parallel processing, with each Agent responsible for a certain number of chapters
⚠️ Follow global constraint: each sub-Agent is responsible for a maximum of 3 chapters (see AGENTS.md "Sub-Agent Parallel Processing Rules")
Required number of Agents = ceil(total chapters / 3), allocation strategy is sequential continuous assignment by chapter order
Generate a core plot summary for each chapter (remove details, retain only key events)
Conduct detailed review for each chapter:
- Word count statistics and filling demand identification
- Timeline and event sequence verification
- Consistency of character behavior and personality (OOC detection)
- Item status and information boundary check
- Scene description and dialogue quality evaluation
- Foreshadowing setting and resolution status
Generate chapter summaries to
```
.sumeru/review/summaries/
```
directory
Record chapter issue list to
```
.sumeru/review/chapter-issues/
```
directory
Support resumable review, skip already reviewed chapters

Phase 3: Unified Repair Execution

Merge global issues and chapter issues, sort by severity (Fatal > Severe > Medium > Minor)
Develop and execute repair plan, divided into two repair types:
- Lightweight Repair (executed directly by review): minor modifications such as text correction, paragraph adjustment, sentence optimization, word count filling, directly modify files in chapters/ directory (automatically back up original files to
```
.sumeru/write/original/
```
  before modification)
- Rewrite Repair (marked as pending): chapters with severe plot logic contradictions, large-scale OOC, setting collapse that require rewriting are recorded in the repair plan
Execute lightweight repair strategy:
- Global issue repair: adjust overall timeline, unify settings, optimize main plot structure
- Chapter issue repair: fix lightweight issues such as word count, logic, OOC, plot contradictions chapter by chapter
- Linked repair: handle cross-chapter related issues (such as foreshadowing resolution, character growth)
Generate repair report to
```
.sumeru/review/fix-report.json
```
Generate repair plan
```
fix-plan.json
```
, mark chapters that need rewriting and specific repair suggestions
Conduct re-review after repair to verify that all lightweight repair issues are completely resolved

三阶段功能分配

Three-Stage Function Allocation

第一阶段：全局审查功能

整体剧情脉络分析：审查主线、支线、伏笔的整体分布
全局时间线校验：梳理完整时间线，识别大跨度时序问题
设定一致性检查：验证世界观、力量体系、规则设定的统一性
冲突点分布评估：评估冲突强度、分布密度、节奏把控
伏笔回收状态检查：识别所有未回收的伏笔和回收方向

第二阶段：章节细节审查功能 6. 字数检查与填充：确保每章字数达标，字数不足自动填充 7. 章节时间线与事件时序：检查每章内部的时间逻辑和事件顺序 8. OOC检测与人物一致性：检查人物行为、性格、对话的一致性 9. 物品状态与信息边界：追踪物品状态变化和人物信息边界 10. 场景描写与对话质量：评估场景细节和对话的自然度 11. 章节伏笔设置：记录每章的伏笔设置和预期回收位置

⚠️ 遵循全局约束：每个子Agent最多负责3个章节的审查（详见 AGENTS.md）

第三阶段：统一修复功能 12. 问题统一修复：合并所有问题，按严重程度排序，制定修复计划 13. 轻量修复执行：文字修正、段落调整、语句优化、字数填充等直接修改

chapters/

文件 14. 重写修复标记：对需要重写的章节生成

fix-plan.json

，记录具体问题与修复建议 15. 全局问题修复：调整整体剧情、时间线、设定等大尺度问题 16. 章节问题修复：逐章修复字数、逻辑、人物、场景等轻量级细节问题 17. 联动修复：处理跨章节关联问题，确保修复后的整体一致性 18. 修复验证：修复后重新审查，确保所有轻量修复问题已彻底解决

⚠️ 轻量修复阶段遵循全局约束：每个Agent最多负责3个章节（详见 AGENTS.md）

Phase 1: Global Review Functions

Overall plot context analysis: review the overall distribution of main plot, subplots, and foreshadowings
Global timeline verification: sort out the complete timeline, identify large-span sequence issues
Setting consistency check: verify the unity of worldview, power system, and rule settings
Conflict distribution evaluation: evaluate conflict intensity, distribution density, and rhythm control
Foreshadowing resolution status check: identify all unresolved foreshadowings and resolution direction suggestions

Phase 2: Chapter Detail Review Functions 6. Word count check and filling: ensure each chapter meets the word count standard, automatically fill if word count is insufficient 7. Chapter timeline and event sequence: check the time logic and event order within each chapter 8. OOC detection and character consistency: check the consistency of character behavior, personality, and dialogue 9. Item status and information boundary: track item status changes and character information boundaries 10. Scene description and dialogue quality: evaluate the detail of scenes and naturalness of dialogue 11. Chapter foreshadowing setting: record foreshadowing settings and expected resolution positions in each chapter

⚠️ Follow global constraint: each sub-Agent is responsible for a maximum of 3 chapters for review (see AGENTS.md)

Phase 3: Unified Repair Functions 12. Unified issue repair: merge all issues, sort by severity, develop repair plan 13. Lightweight repair execution: directly modify files in chapters/ directory for text correction, paragraph adjustment, sentence optimization, word count filling, etc. 14. Rewrite repair marking: generate

fix-plan.json

for chapters that need rewriting, record specific issues and repair suggestions 15. Global issue repair: adjust large-scale issues such as overall plot, timeline, and settings 16. Chapter issue repair: fix lightweight details such as word count, logic, characters, scenes chapter by chapter 17. Linked repair: handle cross-chapter related issues to ensure overall consistency after repair 18. Repair verification: conduct re-review after repair to ensure all lightweight repair issues are completely resolved

⚠️ Follow global constraint: each Agent is responsible for a maximum of 3 chapters during lightweight repair phase (see AGENTS.md)

修复机制说明

Repair Mechanism Description

轻量级修复：直接修改
```
chapters/
```
中有问题的段落或句子，修改前自动备份原始文件到
```
.sumeru/write/original/
```
重写修复：对于严重有问题的章节，记录到
```
fix-plan.json
```
，建议使用
```
sumeru-write
```
重新生成
自动备份：修改
```
chapters/
```
文件前，自动将原始版本备份到
```
.sumeru/write/original/
```
，确保可回滚
修复记录：所有修复操作都记录在
```
issues-fixed.json
```
中，包含修复前后对比

Lightweight Repair: directly modify problematic paragraphs or sentences in chapters/ directory, automatically back up original files to
```
.sumeru/write/original/
```
before modification
Rewrite Repair: for severely problematic chapters, record to
```
fix-plan.json
```
, suggest using
```
sumeru-write
```
to regenerate
Automatic Backup: automatically back up the original version to
```
.sumeru/write/original/
```
before modifying files in chapters/ directory to ensure rollback capability
Repair Records: all repair operations are recorded in
```
issues-fixed.json
```
, including before-and-after repair comparisons

输出内容

Output Content

第一阶段：全局审查输出

全局剧情脉络分析报告：主线、支线、伏笔的整体分布图
完整故事时间线图谱：按时间轴整理的关键事件序列
设定一致性检查报告：世界观、力量体系、规则设定的统一性分析
冲突点分布评估：冲突强度、分布密度、节奏把控评估
全局伏笔回收状态表：所有未回收伏笔清单与回收方向建议

第二阶段：章节细节审查输出

章节概要目录：每章核心剧情概要（
```
.sumeru/review/summaries/
```
）
字数检查报告：每章字数统计、不达标的章节列表、填充改进记录
章节时间线与事件时序报告：每章内部时间逻辑检查结果
OOC检测报告：人物行为异常点、性格偏离分析
物品状态追踪表：重要物品的获得、使用、丢失状态变化
章节伏笔设置记录表：每章伏笔设置与预期回收位置
剧情连贯性评分：多维度综合评分（时间线、逻辑性、人物一致性等）

第三阶段：统一修复输出

问题修复报告：所有问题的修复情况记录、修复前后对比
全局问题修复记录：整体剧情、时间线、设定的调整记录
章节问题修复记录：逐章修复的详细记录
联动修复说明：跨章节关联问题的处理方案
修复验证报告：修复后重新审查的验证结果
优化建议：剧情调整方案、伏笔回收建议、冲突优化建议

Phase 1: Global Review Output

Overall Plot Context Analysis Report: overall distribution map of main plot, subplots, and foreshadowings
Complete Story Timeline Map: sequence of key events organized by timeline
Setting Consistency Check Report: unity analysis of worldview, power system, and rule settings
Conflict Distribution Evaluation: evaluation of conflict intensity, distribution density, and rhythm control
Global Foreshadowing Resolution Status Table: list of all unresolved foreshadowings and resolution direction suggestions

Phase 2: Chapter Detail Review Output

Chapter Summary Directory: core plot summary for each chapter (
```
.sumeru/review/summaries/
```
)
Word Count Check Report: word count statistics for each chapter, list of chapters that do not meet standards, filling improvement records
Chapter Timeline and Event Sequence Report: results of time logic check within each chapter
OOC Detection Report: abnormal character behavior points, personality deviation analysis
Item Status Tracking Table: status changes of important items (obtained, used, lost)
Chapter Foreshadowing Setting Record Table: foreshadowing settings and expected resolution positions in each chapter
Plot Coherence Score: multi-dimensional comprehensive score (timeline, logic, character consistency, etc.)

Phase 3: Unified Repair Output

Issue Repair Report: repair status records of all issues, before-and-after repair comparisons
Global Issue Repair Record: adjustment records of overall plot, timeline, and settings
Chapter Issue Repair Record: detailed repair records chapter by chapter
Linked Repair Description: solutions for cross-chapter related issues
Repair Verification Report: verification results of re-review after repair
Optimization Suggestions: plot adjustment plans, foreshadowing resolution suggestions, conflict optimization suggestions

数据持久化

Data Persistence

用户可见输出（当前工作目录）：

```
剧情审查报告.md
```
：完整审查结果报告，包含所有问题、严重程度、修复建议（直接可读）
```
字数检查与填充报告.md
```
：字数统计、填充改进记录
```
全局审查报告.md
```
：第一阶段的全局分析结果
```
章节细节审查报告.md
```
：第二阶段的章节分析结果
```
统一修复报告.md
```
：第三阶段的修复记录

中间数据（仅系统内部使用，存于
.sumeru/review/
目录）： 第一阶段：全局审查数据

```
global-issues.json
```
：全局问题清单，包含时间线、设定、伏笔等问题
```
timeline.json
```
：完整时间线图谱，按时间轴排列的关键事件序列
```
plot-map.json
```
：剧情脉络图，显示主线、支线、冲突点分布
```
foreshadowing-tracking.json
```
：伏笔追踪表，包含所有伏笔的位置、内容、回收状态
```
coherence-score.json
```
：剧情连贯性评分明细

第二阶段：章节细节审查数据

```
summaries/
```
：章节概要目录
- ```
001.json
```
  、
```
002.json
```
  ... 每章的核心剧情概要（章节号三位数零填充）
- ```
summary-progress.json
```
  ：概要生成进度记录
```
chapter-issues/
```
：章节问题清单
- ```
001.json
```
  、
```
002.json
```
  ... 每章的详细问题记录（章节号三位数零填充）
```
word-count.json
```
：字数统计数据，每章字数、目标字数、填充情况

第三阶段：统一修复数据

```
issues.json
```
：合并后的完整问题清单，按严重程度、类型分类
```
fix-report.json
```
：问题修复报告，包含修复前后对比
```
fix-plan.json
```
：重写修复计划，标记需要重写的章节及具体修复建议
```
issues-fixed.json
```
：已修复问题记录
```
global-fix.log
```
：全局问题修复日志
```
chapter-fix.log
```
：章节问题修复日志

User-Visible Output (Current Working Directory):

```
剧情审查报告.md
```
: complete review result report, including all issues, severity levels, and repair suggestions (directly readable)
```
字数检查与填充报告.md
```
: word count statistics, filling improvement records
```
全局审查报告.md
```
: global analysis results of Phase 1
```
章节细节审查报告.md
```
: chapter analysis results of Phase 2
```
统一修复报告.md
```
: repair records of Phase 3

Intermediate Data (Only for Internal System Use, Stored in
.sumeru/review/
Directory): Phase 1: Global Review Data

```
global-issues.json
```
: global issue list, including timeline, setting, foreshadowing, and other issues
```
timeline.json
```
: complete timeline map, sequence of key events arranged by timeline
```
plot-map.json
```
: plot context map, showing distribution of main plot, subplots, and conflict points
```
foreshadowing-tracking.json
```
: foreshadowing tracking table, including position, content, and resolution status of all foreshadowings
```
coherence-score.json
```
: plot coherence score details

Phase 2: Chapter Detail Review Data

```
summaries/
```
: chapter summary directory
- ```
001.json
```
  ,
```
002.json
```
  ... core plot summary for each chapter (chapter number padded with three zeros)
- ```
summary-progress.json
```
  : summary generation progress record
```
chapter-issues/
```
: chapter issue list
- ```
001.json
```
  ,
```
002.json
```
  ... detailed issue records for each chapter (chapter number padded with three zeros)
```
word-count.json
```
: word count data, including word count per chapter, target word count, and filling status

Phase 3: Unified Repair Data

```
issues.json
```
: merged complete issue list, classified by severity and type
```
fix-report.json
```
: issue repair report, including before-and-after repair comparisons
```
fix-plan.json
```
: rewrite repair plan, mark chapters that need rewriting and specific repair suggestions
```
issues-fixed.json
```
: resolved issue records
```
global-fix.log
```
: global issue repair log
```
chapter-fix.log
```
: chapter issue repair log

与其他 Skill 配合

Cooperation with Other Skills

前置 Skill：读取
```
sumeru-outline
```
的大纲数据和
```
sumeru-write
```
的章节数据
- 使用
```
.sumeru/outline/
```
  的世界观、人设、大纲作为基准
- 使用
  .sumeru/outline/chapter-outlines.json
  作为预期剧情参考
- 使用
```
chapters/
```
  目录下的章节内容进行审查
- 将实际章节内容与细纲进行对比，识别剧情偏离
修复计划输出：修复完成后生成
```
fix-plan.json
```
，其中标记了需要重写的章节及具体修复建议
- worldbuilder 在编排流程时读取此文件，决定是否需要调用
```
sumeru-write
```
  进行重写
- 独立使用时，用户可查看
```
fix-plan.json
```
  后手动调用
```
sumeru-write
```
  重写指定章节
后续 Skill：
- sumeru-write：读取
```
fix-plan.json
```
  ，执行重写修复（由 worldbuilder 编排或用户手动调用）
- sumeru-polish：接收修复后的章节内容，进行文笔润色
- sumeru-finalize：接收修复后的章节内容，进行完稿校验和多平台导出

Predecessor Skills: Read outline data from
```
sumeru-outline
```
and chapter data from
```
sumeru-write
```
- Use worldview, character settings, and outline from
```
.sumeru/outline/
```
  as benchmarks
- Use
  .sumeru/outline/chapter-outlines.json
  as expected plot reference
- Use chapter content in chapters/ directory for review
- Compare actual chapter content with detailed outlines to identify plot deviations
Repair Plan Output: Generate
```
fix-plan.json
```
after repair completion, which marks chapters that need rewriting and specific repair suggestions
- worldbuilder reads this file when orchestrating processes to decide whether to call
```
sumeru-write
```
  for rewriting
- When used independently, users can view
```
fix-plan.json
```
  and manually call
```
sumeru-write
```
  to rewrite specified chapters
Successor Skills:
- sumeru-write: Read
```
fix-plan.json
```
  to execute rewrite repair (orchestrated by worldbuilder or manually called by users)
- sumeru-polish: Receive repaired chapter content for stylistic polishing
- sumeru-finalize: Receive repaired chapter content for final draft verification and multi-platform export

三阶段数据流向

Three-Stage Data Flow

sumeru-write 章节
    ↓
第一阶段：全局审查（global-issues.json）
    ↓
第二阶段：章节细节审查（chapter-issues/ + summaries/）
    ↓
合并问题清单（issues.json）
    ↓
第三阶段：统一修复
    ├─ 轻量修复 → 直接修改 chapters/（自动备份到 .sumeru/write/original/）
    └─ 重写修复 → 生成 fix-plan.json
    ↓
供 polish 和 finalize 使用

sumeru-write chapters
    ↓
Phase 1: Global Review (global-issues.json)
    ↓
Phase 2: Chapter Detail Review (chapter-issues/ + summaries/)
    ↓
Merge Issue List (issues.json)
    ↓
Phase 3: Unified Repair
    ├─ Lightweight Repair → Directly modify chapters/ (auto-backup to .sumeru/write/original/)
    └─ Rewrite Repair → Generate fix-plan.json
    ↓
Used by polish and finalize

数据复用

Data Reuse

返工修改时直接读取问题清单定位需要调整的章节
支持增量审查，新增章节时基于已有审查结果只检测新增内容
修复完成后可再次调用自动验证问题是否解决
字数填充记录可用于后续章节的字数参考

Directly read issue list to locate chapters that need adjustment during rework
Support incremental review, only detect new content based on existing review results when adding new chapters
Can be called again after repair to automatically verify if issues are resolved
Word count filling records can be used as word count reference for subsequent chapters