一键导入
dev-route
Generate ExoMind development route maps, batch planning overviews, issue clustering, and next-step implementation route analyses for this repository.
用 Codex 或 Claude 帮你安装 复制这段 Prompt,粘贴到 Codex、Claude 或其他助手里,让它检查 Skill 页面并帮你完成安装。
菜单
Generate ExoMind development route maps, batch planning overviews, issue clustering, and next-step implementation route analyses for this repository.
用 Codex 或 Claude 帮你安装 复制这段 Prompt,粘贴到 Codex、Claude 或其他助手里,让它检查 Skill 页面并帮你完成安装。
基于 SOC 职业分类
Use when publishing an ExoMind preview build or formal release, or when reconciling release automation/docs around GitHub Release notes, Pages metadata, canonical tags, and CHANGELOG governance.
CRITICAL: Use for ownership/borrow/lifetime issues. Triggers: E0382, E0597, E0506, E0507, E0515, E0716, E0106, value moved, borrowed value does not live long enough, cannot move out of, use of moved value, ownership, borrow, lifetime, 'a, 'static, move, clone, Copy, 所有权, 借用, 生命周期
CRITICAL: Use for concurrency/async. Triggers: E0277 Send Sync, cannot be sent between threads, thread, spawn, channel, mpsc, Mutex, RwLock, Atomic, async, await, Future, tokio, deadlock, race condition, 并发, 线程, 异步, 死锁
Teach an AI Agent to connect to ExoMind Runtime via HTTP/curl. Prefer `/act/*` feature APIs first, and fall back to raw resource routes only when `/act` has no matching action or when low-level truth/debugging is required. Use when the user mentions ExoMind, `/act`, await, event log, RT access, curl, profiles, tasks, or timeblocks in ExoMind.
Generate ExoMind development daily reports, including 早报、午报、晚报、夜报、日报, issue/PR status summaries, and devlog dashboards for this repository.
Track ExoMind issues from natural-language user reports by deduplicating, checking current dev state, creating or updating issues, and linking dependencies without asking the user for structured forms.
| name | dev-route |
| description | Generate ExoMind development route maps, batch planning overviews, issue clustering, and next-step implementation route analyses for this repository. |
This skill is the project-local skill entry extracted from docs/agents/dev-route/.
Use this skill when the user asks for:
bun run devlog:extract --type route to get the latest published route as Agent-friendly text. This is required for batch status comparison, trigger detection, and batch letter continuation.references/AGENTS.md for the route-planning workflow, issue clustering rules, and output requirements.references/prompt.md if you need the original execution prompt wording.assets/route-template.html when the requested output needs the existing HTML route template.To extract structured data from a published route (Agent-friendly text or JSON):
bun run devlog:extract --type route # 最新航线 → 纯文本摘要
bun run devlog:extract --type route --format json # 最新航线 → JSON
bun run devlog:extract --file <path> # 指定 HTML 文件
bun run devlog:extract --type route --source pages # 强制从 GitHub Pages 读取
When generating a new route, read the previous route first to compare batch status changes and detect triggers.
devlog:extract 默认按 GitHub Pages routes/manifest.json -> data JSON -> latest.json 读取,并在输出顶部返回 [devlog-source] 或 _devlogSource。
已发布归档现在要求 dataFile 必须存在;HTML 解析仅保留给显式 --file 或本地 temp/ 兜底。
必须检查该来源块,确认:
pages-jsontrust 是否为 highconsistency 是否为 ok如果来源块显示 fallback、本地来源、HTML 兼容解析或一致性不完整,必须在后续输出中明确说明,不得把它表述为“最新已发布状态”。
gh limits and priority checks.bun run route:publish;不再引入 v1/v2 心智。