zenstory-ai/oh-story-claudecode / skills/story-import
story-import
Verified逆向导入已有小说。将已写好的小说(半成品或完本)反向解析为标准项目目录结构,兼容 story-long-write / story-short-write 后续写作流程;内部复用 story-long-analyze / story-short-analyze 的拆解管道,按篇幅自动分流。触发方式:/story-import、「导入小说」「反向解析」「导入」「把我的书导进来」。
| File | Kind | Size |
|---|---|---|
| SKILL.md | skill md | 10.7 KB |
| references/benchmark-sync.md | markdown | 4.0 KB |
| references/character-state-reverse.md | markdown | 4.2 KB |
| references/deep-analysis.md | markdown | 4.3 KB |
| references/import-report.md | markdown | 4.3 KB |
| references/import-special-cases.md | markdown | 2.5 KB |
| references/import-tracking.md | markdown | 6.7 KB |
| references/length-routing.md | markdown | 1.5 KB |
| references/outline-reverse-rules.md | markdown | 6.0 KB |
| references/outline-reverse.md | markdown | 2.8 KB |
| references/structure-mapping-long.md | markdown | 20.1 KB |
| references/structure-mapping-short.md | markdown | 10.2 KB |
| references/tracking-initialization.md | markdown | 1.6 KB |
| scripts/build_outline_brief.jsexecutable | script | 15.4 KB |
| scripts/check-outline-contract.js | script | 12.4 KB |
| scripts/outline_view.jsexecutable | script | 15.1 KB |
| scripts/tracking_commit.jsexecutable | script | 84.7 KB |
| scripts/wordcount_core.jsexecutable | script | 20.3 KB |
references/import-special-cases.md
View on GitHub# 导入的特殊情况
遇到流程答疑或旧追踪迁移时读取。
## 流程答疑
用户问「导入续写先装环境还是先导入」「已有小说怎么续写」「导入流程」这类问题时,先直接给结论,再继续收集原文——避免用户只想确认流程却被直接要求贴原文:
1. **推荐顺序**:先 `/story-setup` 装好写作环境,新开或刷新会话后运行 `/story-import`,最后用 `/story-long-write 写第N章` 续写(N 是还没写的第一章)。
2. **也可以直接 `/story-import`**:导入会在深度分析前检查写作环境;没装时给「先去装」或「直接导入,慢一点」两种选择。
3. **当前协议项目**(书名目录下有 `追踪/_tracking-state.json`):先查导入记录;若仍有未完成项,从该项续跑。已完成导入时,确认项目根 `.active-book` 指向正确书目,再用 `/story-long-write 写第N章` 续写,不重复导入。
4. **旧追踪项目**(有 `追踪/` 和正文,但没有 `追踪/_tracking-state.json`):日更会停下要求重新导入,但**不需要重跑全书拆解**,只重建追踪,见下一节。
## 旧追踪项目迁移
书名目录下有 `追踪/` 与正文、但没有 `追踪/_tracking-state.json` 时,项目用的是旧的追踪结构。正文和 `设定/`、`大纲/`、`拆文库/` 都不受影响,**只需重建 `追踪/`**,不重跑深度分析、不碰正文:
1. 检查章号最大的 `正文/第NNN章_*.md` 是否完整,确定最后完整章号 `N`;不能仅凭最大文件名判定。
2. 从旧 `追踪/` 现有文件(角色状态、伏笔、时间线等,文件名按项目实际情况)和最近 3-5 章正文,重建当前状态:核心角色快照、未回收伏笔、已揭示时间线事件、长期约束、下一章承诺。角色快照的反推方法见 [character-state-reverse.md](character-state-reverse.md)。
3. 按 [import-tracking.md](import-tracking.md) 构造初始化事务(其中点名的 tracking-initialization.md 完整读取),`last_chapter` 写 `N`(第 1..N 章不伪造逐章记录),执行 `tracking_commit.js init`。
4. `init` 会把旧追踪结构按原样整体移入 `追踪/_旧追踪存档/` 再建当前协议——旧内容不删除、不参与解析,留给作者查阅。
5. 跑 `tracking_commit.js check` 确认通过,再回 `/story-long-write` 写下一章(第 N+1 章)续写。
重建结果以第 2 步的证据为准;拿不准的字段留空或写进 `continuity_risks`,不杜撰。用户明确要求重拆全书时才走完整导入。
Related skills
| Skill | Stars | Updated | Works with | Status | Install |
|---|---|---|---|---|---|
| slack-gif-creatoranthropics/skillsKnowledge and utilities for creating animated GIFs optimized for Slack. Provides constraints, validation tools, and animation concepts. Use when users request animated GIFs for Slack like "make me a GIF of X doing Y for Slack." | Stars: 198k | Updated | Claude CodeCodex | Verified | Install |
| ponytailDietrichGebert/ponytailLazy senior dev mode for any coding task: the smallest change that fully solves it, and a reply a busy human understands in one read. | Stars: 196k | Updated | Claude CodeCodex | Verified | Install |
| ponytail-debtDietrichGebert/ponytailHarvest every shortcut: comment into one debt ledger, so deferrals get tracked instead of forgotten. One-shot report. | Stars: 196k | Updated | Claude CodeCodex | Verified | Install |
| ponytail-debtDietrichGebert/ponytailList every `shortcut:` comment (and older `ponytail:` ones) as a debt ledger. One-shot report, changes nothing. Use for "ponytail debt", "what did ponytail defer", "list the shortcuts", /ponytail-debt. | Stars: 196k | Updated | Claude CodeCodex | Verified | Install |