在每次回复中使用固定前缀并列出本次实际参考的指令/文件，便于校验是否遵循上下文与规则。
The English summary is being prepared. Showing the original description.
See how to installReview the instructions the agent will receive before you install.
让用户能快速确认我是否实际引用/遵循了本次会话中的指令与文件。
✨ 已启用上下文校验 开头。尊敬的主人：在回复末尾追加两行：
已读指令：<指令文件及其核心要求>
已启用技能：<技能名与简要功能>
清单规则：
已启用技能：技能名 - 技能说明已读指令：无已启用技能：无read_file）。已读指令：无。为了增强透明度和可追踪性，当列出某个已启用技能时，应在回复正文中体现该技能的实际使用证据：
| 技能名 | 使用证据 | 验证方式 |
|---|---|---|
_git-commit | 提交说明文件末尾有签名行 | 搜索 "🤖 本提交由 _git-commit" |
_file-output-guard | 文件中包含 [Part X/?] 分段标记 | 查看文件内容的分段标记 |
_change-summary | PR 描述中有 "提交摘要" 段落（来自 git log --oneline） | 检查 PR 或 PR_DESCRIPTION.local.md |
_traceability-check | 提交说明覆盖了 git diff --name-only --cached 列出的所有文件 | 对照检查清单 |
_code-health-check | 回复中提及测试通过、编译成功等验证结果 | 查看回复内容或控制台输出 |
_instruction-guard | 本次回复的 "已读指令" 列出了被读取的指令文件 | 见"已读指令"行 |
最佳实践：
_git-commit - 格式化提交说明 时，回复中应提及 "已使用 Conventional Commits 格式" 或 "已添加签名行"追加一行：
仓库状态：分支=<branch> | 未提交=<count_uncommitted> | 未跟踪=<count_untracked>
填写规则：
git rev-parse --abbrev-ref HEADgit status --porcelain 中已跟踪且变更的条目数git status --porcelain 中以 ?? 开头的条目数将会话结尾信息放在 diff 格式代码框中，利用语法高亮区分不同类型信息：
─────────────────────────────────────────────
+ ✅ 已读指令：[文件名]
- 🔧 已启用技能：技能名 A - 技能说明
- 🔧 已启用技能：技能名 B - 技能说明
! 📦 仓库状态：分支=<branch>
! └─ 未提交：<n> (仅当>0时显示)
! └─ 未跟踪：<m> (仅当>0时显示)
─────────────────────────────────────────────
格式说明：
+ 绿色：已读指令- 红色：已启用技能! 橙色：仓库状态└─ 树形结构展示细节─（U+2500）No reviews yet. Tell others what you thought.
No login needed. Share how it worked for you, ask a question, or note where it did not run.
No comments yet. Be the first to write one.
Master backend architectures, REST API design, microservices, and server-side development across multiple languages. Use this as a central index to access specialized sub-skills.
The English summary is being prepared. Showing the original description.
Automate 21risk tasks via Rube MCP (Composio). Always search tools first for current schemas.
The English summary is being prepared. Showing the original description.
Automate 2chat tasks via Rube MCP (Composio). Always search tools first for current schemas.
The English summary is being prepared. Showing the original description.
Arquitecto de Soluciones Principal y Consultor Tecnológico de Andru.ia. Diagnostica y traza la hoja de ruta óptima para proyectos de IA en español.
The English summary is being prepared. Showing the original description.
[00] META. Orchestrate skills into dynamic chains for complex tasks. Analyzes the task, discovers available skills, builds an optimal chain, explains why each skill is needed, and executes step-by-step with user confirmation. Use for any complex task requiring multiple thinking/research/analysis steps. Triggers on "plan this", "how to approach", "what's the strategy", "build a plan", or any multi-step problem requiring skill orchestration.
The English summary is being prepared. Showing the original description.
[00] TnR ABSOLUTE RIGOR — Systemic Verification Doctrine. Forced cognitive exertion for high-stakes investigations. Mandates absolute deconstruction, mathematical proof chains, and ≥95% derived certainty. Zero-tolerance for heuristics or sentiment-based reasoning. Shortcuts are defined as intentional hallucinations.
The English summary is being prepared. Showing the original description.