exomind

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.

Generate ExoMind development route maps, batch planning overviews, issue clustering, and next-step implementation route analyses 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.

面向“围绕一个明确目的，对照多个参考源的实现、做法或边界来形成判断”的调研分析型任务。适用于交叉分析、对标调研、竞品分析、参考已有软件怎么做、围绕某个主题找多个参考源对照等请求；当需要先找到合适参考源，再展开分析、比较、综合时，应触发此 skill。默认用于运行态交叉分析，只有在用户明确要求新增、补充或整理本地参考源时，才进入维护态。触发关键词：交叉分析、对标调研、竞品对比、参考源对照、多个参考源、调研分析、为什么参考X而不是Y、应该参考哪些。

Use when the full test suite has 5+ failures NOT directly caused by your current changes. Typical triggers: inheriting a red CI, post-merge breakage, pre-existing failures discovered during validation. NOT when 1-2 failures tied to your own edits (use systematic-debugging). NOT when writing new tests (use test-driven-development).

GitHub 公开仓库隐私泄露应急处置。当发现敏感信息（真实人名、个人日程、内部战略等） 被意外暴露在公开仓库的 issue、PR、代码文件、开发日志或 Git 历史中时使用。 即使用户只说「删掉那条 issue」也应调用此 skill——单独删除往往不够，下游系统 （devlog、GitHub Pages）和 Git 历史中可能同步存有副本。 触发词：泄露、误提交、私人信息、敏感内容、清除 Git 历史、删除 issue、人名被公开、 个人日程暴露、filter-repo、force push 清理。

Fetch and parse the latest ExoMind development report or route data from GitHub Pages manifests with provenance and trust metadata. Use when the user asks about project status, latest report, latest route, or development progress.

Generate a human-facing HTML verification page with checkboxes, step-by-step UI acceptance instructions, evidence fields, notes, progress tracking, and local persistence. Use when the user asks to create a manual verification page,验收页,人工验收清单,可勾选HTML检查页, or wants a systematic human UI workflow to verify implementation against a plan, issue batch, or feature set.

Triage and govern ExoMind GitHub issues by identifying completed, duplicated, stale, or mis-prioritized issues and applying the repository's issue governance rules.