$ loading_
用于仓库命令执行、CI排障与小范围修复，并提供可核验执行证据。
复制安装指令，让 AI 自动完成配置 · 推荐新手
请帮我安装 askskill 上的 "terminal-ops" 技能： 1. 下载 https://raw.githubusercontent.com/affaan-m/ECC/main/skills/terminal-ops/SKILL.md 2. 保存为 ~/.claude/skills/terminal-ops/SKILL.md 3. 装好后重载技能，告诉我可以用了
请检查这个仓库最近一次 CI 失败的原因，复现失败步骤，定位具体报错，并给出最小修复方案。请明确列出你执行过的命令、关键输出和验证结果。
返回失败原因、复现与修复过程、已执行命令清单，以及修复后验证通过的证据。
在该仓库中运行测试、lint 和类型检查，汇总所有失败项，并按优先级说明应该先处理哪些问题。请附上每一步执行证据。
输出检查结果总览、失败项分类、优先级建议，以及对应命令和结果证据。
针对这个明确的缺陷做最小改动修复，不要重构无关代码。完成后展示变更内容、执行过的验证命令，以及为什么确认修复有效。
提供精确修改说明、变更文件摘要、验证记录，以及修复有效性的可核验证据。
Use this when the user wants real repo execution: run commands, inspect git state, debug CI or builds, make a narrow fix, and report exactly what changed and what was verified.
This skill is intentionally narrower than general coding guidance. It is an operator workflow for evidence-first terminal execution.
Pull these ECC-native skills into the workflow when relevant:
verification-loop for exact proving steps after changestdd-workflow when the right fix needs regression coveragesecurity-review when secrets, auth, or external inputs are involvedgithub-ops when the task depends on CI runs, PR state, or release statusknowledge-ops when the verified outcome needs to be captured into durable project contextSettle:
Before changing anything:
Solve one dominant failure at a time:
Use exact status words:
SURFACE
- repo
- branch
- requested mode
EVIDENCE
- failing command / diff / test
ACTION
- what changed
STATUS
- inspected / changed locally / verified locally / committed / pushed / blocked
通过双评审智能体对结果进行对抗式校验，提升输出发布前的可靠性
基于公开证据与本地材料，快速完成最新事实调研、对比分析与建议输出