wiki-history-ingest
Compare original and translation side by side
🇺🇸
Original
English🇨🇳
Translation
ChineseUnified History Ingest Router
统一历史导入路由器
This is a thin router for history sources only. It does not replace for documents.
wiki-ingest这是仅面向历史记录来源的轻量路由器,不会替代用于文档导入的。
wiki-ingestSubcommands
子命令
If the user invokes (or equivalent text command), dispatch directly:
/wiki-history-ingest <target>| Subcommand | Route To |
|---|---|
| |
| |
| infer from context using rules below |
如果用户调用 (或等价的文本命令),直接进行分发:
/wiki-history-ingest <target>| 子命令 | 分发至 |
|---|---|
| |
| |
| 根据以下规则从上下文推断 |
Routing Rules
路由规则
- If the user explicitly says or
claude, route directly.codex - If the user provides a path/source:
- or Claude memory/session JSONL artifacts ->
~/.claudeclaude-history-ingest - or rollout/session index artifacts ->
~/.codexcodex-history-ingest
- If ambiguous, ask one short clarification:
- "Should I ingest history or
claudehistory?"codex
- "Should I ingest
- 如果用户明确提到或
claude,直接分发到对应skill。codex - 如果用户提供了路径/来源:
- 或Claude内存/会话JSONL产物 ->
~/.claudeclaude-history-ingest - 或发布/会话索引产物 ->
~/.codexcodex-history-ingest
- 如果存在歧义,询问一条简短的澄清问题:
- "我应该导入历史记录还是
claude历史记录?"codex
- "我应该导入
Execution Contract
执行约定
- After routing, execute the destination skill's workflow exactly.
- Do not duplicate destination logic in this file.
- Leave manifest/index/log update semantics to the destination skill.
- 路由完成后,严格执行目标skill的工作流。
- 不要在本文件中重复实现目标skill的逻辑。
- 清单/索引/日志的更新逻辑交由目标skill处理。
UX Convention
UX约定
- Use for documents/content sources
wiki-ingest - Use for agent history sources
wiki-history-ingest
Examples:
/wiki-history-ingest claude/wiki-history-ingest codex- (agents that use
$wiki-history-ingest claudeinvocation)$skill
- 针对文档/内容来源使用
wiki-ingest - 针对Agent历史记录来源使用
wiki-history-ingest
示例:
/wiki-history-ingest claude/wiki-history-ingest codex- (使用
$wiki-history-ingest claude调用方式的Agent)$skill