oh-story-claudecode
Oh Story packages Chinese web-fiction workflows as agent skills, spanning research, outlines, prose, checks and publication preparation. For authors keeping a long manuscript in files, its practical question is how chapter completion becomes durable progress that another session can recover. We reviewed plugin version 0.10.0 at a fixed commit, containing fourteen skills. Python 3.12.13 and Node.js 26.6.0 ran actual chapter and tracking commands in a disposable project. We did not install host hooks, ask a model to write fiction or publish anything.
Twelve checks exercised normal and exceptional paths. A thousand-character specimen returned ready without changing tracking JSON, and a subsequent commit advanced progress. An eight-hundred-character specimen against the same target required a decision; ordinary commit failed without changing the completed chapter. Explicit current-length acceptance committed it and recorded the exception. A known prose-pattern specimen triggered a blocking quality error. A stale revision was refused, a corrected chapter committed, and manually changing a derived context view caused a consistency failure until restored.
These results concern deterministic workflow behavior. The repeated Chinese characters were precise length specimens, not a literary-quality benchmark, and passing rules does not prove readability, originality or detector avoidance. The explicit acceptance command is a caller convention rather than authenticated author approval. Teams should maintain canonical tracking state, regenerate derived views and separately verify host execution. Choose a small manuscript copy for an initial trial when visible chapter closure and recoverable state are useful; evaluate plot coherence, style and actual creative output through editorial review.
Read the full review, verification scope and sources →Features
Why choose it
Trade-offs
Maintenance check
- Last commit
- 2026-11-05
- Commits, last 90 days
- 100+
- Releases, last 90 days
- 20
- Latest release
- v0.10.1 (2026-11-05)
- Open issues
- 10
- Recent issues with at least one comment
- 0/2
Oldest week on the left; the latest four weeks are orange. Source: GitHub commit activity.
Status rule: archived on GitHub = Archived; last commit within 90 days = Active; 91 to 365 days = Slowing; older = Stale. All figures come from the GitHub API on the date shown.
Most discussed open issues
- #88 使用story-long-write生成的内容后,story-review时请求被内容安全系统拦截4 comments · 2026-05-23
- #132 📢 交流方式:Telegram 群 & GitHub Discussions1 comments · 2026-06-04
- #280 能适配 CodeBuddy 吗0 comments · 2026-08-03
Issue titles are quoted from GitHub. Open the link to check whether a problem still applies to the version you use.
Who it fits
- You maintain outlines and story state in files and want explicit chapter closure.
- You will review prose and keep canonical state consistent.
- You expect rule checks to prove writing quality or originality.
- You need verified platform publishing or host integration from this review.
Compatibility
Use cases
Alternatives
Comments
No comments yet. Be the first!