review

Web fiction logic review

Trigger keywords

help me check the novel for bugs, see if there are contradictions in the timeline, are the characters OOC, find conflicts before and after the plot, sort out whether the foreshadowing has been recovered, check the reasonableness of the novel's plot, see if there are plot holes, character behavior does not match personality, check whether the timeline is correct, find contradictions before and after the novel, help me sort out all the foreshadowing, novel plot bug check, logic hole troubleshooting, novel plot review

Core functions

1. Timeline verification: sort out the timeline of the entire story and check for chronological contradictions

   • Absolute time verification: consistency of years, months, dates, and festivals
   • Relative time verification: reasonableness of event intervals, duration descriptions, and growth cycles
   • Season and climate verification: matching of seasonal changes and weather changes with the timeline
   • Age timeline: natural growth of character ages as the plot advances
   • Event chronology: order and causal relationships of key events

2. Plot coherence verification: investigate conflicts before and after the plot

   • Setting consistency: consistency of the worldview, power system, and rules before and after
   • Item status: tracking the acquisition, use, loss, and state changes of important items
   • Information transmission: maintaining the boundary between information characters know and do not know
   • Location and space: reasonableness of geographical settings, scene transitions, and spatial distances

1. Logic hole checking: multi-dimensional investigation of story logic problems

   • Causal logic: reasonableness of event cause-process-result
   • Motivation logic: sufficiency and consistency of character behavioral motivations
   • Ability logic: reasonableness of ability strength, usage limits, and growth curves
   • Resource logic: balance between acquisition and consumption of finances, supplies, manpower, and other resources
   • Social logic: reasonableness of social structure, organizational operation, and interpersonal relationships
   • Common-sense logic: whether it violates basic common sense, physical laws, or biological laws

2. OOC detection: check the logical consistency of character behavior

   • Personality consistency: stability of core personality traits (may grow but not abruptly change)
   • Values consistency: coherence of moral concepts and principles of action
   • Ability boundaries: consistent expression of skill level, intelligence level, and physical strength level
   • Language style: consistency of catchphrases, ways of speaking, and word usage habits
   • Behavior patterns: consistency of decision-making methods, response strategies, and habitual actions
   • Growth curve: gradualness and reasonableness of character transformation (requires sufficient setup)

3. Foreshadowing tracking: systematically identify and track foreshadowing

   • Foreshadowing marking: record the placement, content, and implied direction of all foreshadowing
   • Foreshadowing classification: classify by type (plot foreshadowing, character foreshadowing, setting foreshadowing, emotional foreshadowing)
   • Recovery status: mark foreshadowing as recovered, pending recovery, or suspected abandoned
   • Recovery quality: evaluate the naturalness, satisfaction, and surprise of foreshadowing recovery
   • Foreshadowing suggestions: provide reasonable recovery direction suggestions for pending foreshadowing

4. Conflict point analysis: systematically organize the conflicts in the story

   • Conflict list: list all conflict events in chronological order
   • Conflict types: categorize (person vs. person, person vs. environment, person vs. self, faction conflict, etc.)
   • Conflict intensity: evaluate the tension and importance of conflicts
   • Conflict resolution: record the resolution methods, outcomes, and remaining issues of conflicts
   • Conflict threads: organize the connections and evolution of main plot conflicts and subplot conflicts

5. Main plot and subplot analysis: ensure the narrative is clear and not confusing

   • Main plot thread: the development trajectory of the core storyline
   • Subplot threads: the independent development of each subplot and its connection to the main plot
   • Interwoven clues: the rationality and clarity of multiple parallel clues
   • Narrative pacing: evaluation of plot density, climax distribution, and pacing control

Output content

• Complete story timeline map: a sequence of key events organized along the timeline
• Timeline verification report: a list of temporal contradictions, duration issues, and chronological errors
• Logic loophole list: a list of logic issues categorized by dimension (including severity grading)
• OOC detection report: analysis of abnormal character behavior points and personality deviations
• Foreshadowing tracking table: foreshadowing placement location, content, recovery status, and suggested recovery direction
• Conflict point list: a summary table of all conflict events in the story (including type, intensity, and resolution status)
• Plot coherence score: multi-dimensional comprehensive scoring (timeline, logic, character consistency, etc.)
• Optimization suggestions: plot adjustment plans, foreshadowing recovery suggestions, and conflict optimization suggestions

Data persistence

User-visible output (current working directory)：

• 剧情审查报告.md: complete review result report, including all issues, severity, and repair suggestions (directly readable)

Intermediate data (for system use only, stored in.sumeru/review/directory)：

• timeline.json: complete timeline map, a sequence of key events arranged along the timeline
• issues.json: issue list, all issue records categorized by severity and type (structured data)
• ooc-report.md: OOC detection report backup
• foreshadowing-tracking.json: foreshadowing tracking table, including the location, content, and recovery status of all foreshadowing
• conflict-list.json: conflict point list, a summary of all conflict events in the story
• coherence-score.json: plot coherence score details
• fix-suggestions.json: optimization suggestions and repair plans (structured data)

Data reuse

• During rework and revision, directly read the issue list to locate chapters that need adjustment
• Support incremental review; when new chapters are added, only detect new content based on existing review results
• The issue list can be exported for manual review
• After repairs are completed, automatic verification can be called again to check whether the issues are resolved