Best fit
- 基于证据优先的仓库执行工作流，适用于ECC。当用户需要运行命令、检查仓库、调试CI失败或推送带有精确执行和验证证明的窄修复时使用。
affaan-m/ECC
terminal-ops
基于证据优先的仓库执行工作流，适用于ECC。当用户需要运行命令、检查仓库、调试CI失败或推送带有精确执行和验证证明的窄修复时使用。
63Collecting
See how to use itView GitHub source
npx skills add https://github.com/affaan-m/ECC --skill "docs/zh-CN/skills/terminal-ops"Automated source guide
Source checked Jul 28, 2026·Refresh due Oct 26, 2026
Reorganized from the pinned upstream SKILL.md
Turn terminal-ops's source instructions into a guide you can follow
According to the pinned SKILL.md from affaan-m/ECC: 当用户需要真实的仓库执行时使用此技能：运行命令、检查 git 状态、调试 CI 或构建、进行窄幅修复，并准确报告更改和验证的内容。
npx skills add https://github.com/affaan-m/ECC --skill "docs/zh-CN/skills/terminal-ops"Bring this context
- A concrete task that matches the documented purpose of terminal-ops.
- The files, examples, or context the task depends on.
- Your constraints, target environment, and definition of done.
Expected outputs
- A result that follows the pinned terminal-ops instructions.
- A concise record of assumptions, inputs used, and unresolved questions.
- A final check against the source workflow and relevant permission signals.
Key source sections
Read terminal-ops through these 5 source sections
Sections are extracted automatically from the pinned SKILL.md and link back to the source.
技能栈
verification-loop 用于更改后的精确验证步骤 tdd-workflow 当正确的修复需要回归覆盖时 security-review 当涉及密钥、认证或外部输入时 github-ops 当任务依赖于 CI 运行、PR 状态或发布状态时 knowledge-ops 当需要将验证结果捕获到持久的项目上下文中时
verification-loop 用于更改后的精确验证步骤tdd-workflow 当正确的修复需要回归覆盖时security-review 当涉及密钥、认证或外部输入时
使用时机
用户说"修复"、"调试"、"运行这个"、"检查仓库"或"推送它" 任务依赖于命令输出、git 状态、测试结果或已验证的本地修复 答案必须区分：本地已更改、本地已验证、已提交和已推送
用户说"修复"、"调试"、"运行这个"、"检查仓库"或"推送它"任务依赖于命令输出、git 状态、测试结果或已验证的本地修复答案必须区分：本地已更改、本地已验证、已提交和已推送
安全护栏
先检查再编辑 如果用户仅要求审计/审查，则保持只读 优先使用仓库本地的脚本和辅助工具，而非即兴的临时封装 在验证命令重新运行之前，不得声称已修复 除非分支确实已推送到上游，否则不得声称已推送
先检查再编辑如果用户仅要求审计/审查，则保持只读优先使用仓库本地的脚本和辅助工具，而非即兴的临时封装
工作流
确切的仓库路径 分支 本地差异状态 请求的模式： 检查 修复 验证 推送
确切的仓库路径分支本地差异状态
1. 确定工作表面
确切的仓库路径 分支 本地差异状态 请求的模式： 检查 修复 验证 推送
确切的仓库路径分支本地差异状态
SkillSignal prompt templates
Provide the task, context, and acceptance criteria
These prompts were written by SkillSignal from the source structure; they are not upstream text.
Task-start prompt
Confirm source fit, inputs, and outputs before acting.
Use terminal-ops to help me with: [specific task]. Context: [files, data, or background]. Constraints: [environment, scope, and prohibited actions]. Before acting, check the pinned SKILL.md and explain which sections apply, what inputs are still missing, and what you will deliver.
Source-guided execution
Make the Agent explicitly follow the key extracted sections.
Apply the pinned terminal-ops source to [task]. Pay particular attention to these source sections: “技能栈”, “使用时机”, “安全护栏”, “工作流”, “1. 确定工作表面”. Preserve the important decision at each step. Mark facts not covered by the source as “needs confirmation” instead of inventing them. Then verify the result against my acceptance criteria: [criteria].
Result-review prompt
Check omissions, permissions, and source drift before delivery.
Review the current terminal-ops result: (1) does it satisfy the original task; (2) were any applicable steps or limits in the pinned SKILL.md missed; (3) did it perform any unauthorized file, command, network, or data action; and (4) which conclusions remain unverified? List issues first, then fix only what the source or user authorization supports.
Output checklist
Verify each item before delivery
The task matches the purpose documented in the SKILL.md.
The source section “技能栈” has been checked.
The source section “使用时机” has been checked.
The source section “安全护栏” has been checked.
The source section “工作流” has been checked.
Inputs, constraints, and acceptance criteria are explicit.
Unverified facts, compatibility, and outcome claims are clearly marked.
Any file, command, network, or data action has been reviewed.
Choose a different workflow
When another Skill is the better fit
terminal-ops
Evidence-first repo execution workflow for ECC. Use when the user wants a command run, a repo checked, a CI failure debugged, or a narrow fix pushed with exact proof of what was executed and verified.
A separate implementation from affaan-m/ECC; compare its source, maintenance signals, and permission requirements.
Open source detailterminal-ops
ECCのための証拠優先のリポジトリ実行ワークフロー。ユーザーがコマンドの実行、リポジトリの確認、CIの失敗のデバッグ、正確な実行と検証の証明を伴う狭い修正のプッシュを必要とする場合に使用する。
A separate implementation from affaan-m/ECC; compare its source, maintenance signals, and permission requirements.
Open source detailab-testing
When the user wants to plan, design, or implement an A/B test or experiment, or build a growth experimentation program. Also use when the user mentions "A/B test," "split test," "experiment," "test this change," "variant copy," "multivariate test," "hypothesis," "should I test this," "which version is better," "test two versions," "statistical significance," "how long should I run this test," "growth experiments," "experiment velocity," "experiment backlog," "ICE score," "experimentation program
A separate implementation from coreyhaines31/marketingskills; compare its source, maintenance signals, and permission requirements.
Open source detailFAQ
What does terminal-ops do?
当用户需要真实的仓库执行时使用此技能：运行命令、检查 git 状态、调试 CI 或构建、进行窄幅修复，并准确报告更改和验证的内容。
How do I start using terminal-ops?
The catalog detected this source-specific install command: npx skills add https://github.com/affaan-m/ECC --skill "docs/zh-CN/skills/terminal-ops". Inspect the command and pinned source before running it.
Which Agent platforms does it declare?
No dedicated Agent platform is declared in the pinned source record.
Repository stars
234,327
Repository forks
35,711
Quality
63/100
Source repository last pushed
Quality breakdown
Based on traceable docs and repository signals; stars are not treated as quality.
Documentation19/30
Specificity7/25
Maintenance20/20
Trust signals17/25
Compare before choosing
Related Agent Skills and source variants
These links are selected from shared tasks, functions, stacks, platforms, and same-name variants. Compare the source owner, documentation, permissions, and maintenance signals.
terminal-ops by affaan-m
Evidence-first repo execution workflow for ECC. Use when the user wants a command run, a repo checked, a CI failure debugged, or a narrow fix pushed with exact proof of what was executed and verified.
terminal-ops by affaan-m
ECCのための証拠優先のリポジトリ実行ワークフロー。ユーザーがコマンドの実行、リポジトリの確認、CIの失敗のデバッグ、正確な実行と検証の証明を伴う狭い修正のプッシュを必要とする場合に使用する。
ab-testing by coreyhaines31
When the user wants to plan, design, or implement an A/B test or experiment, or build a growth experimentation program. Also use when the user mentions "A/B test," "split test," "experiment," "test this change," "variant copy," "multivariate test," "hypothesis," "should I test this," "which version is better," "test two versions," "statistical significance," "how long should I run this test," "growth experiments," "experiment velocity," "experiment backlog," "ICE score," "experimentation program
churn-prevention by coreyhaines31
When the user wants to reduce churn, build cancellation flows, set up save offers, recover failed payments, or implement retention strategies. Also use when the user mentions 'churn,' 'cancel flow,' 'offboarding,' 'save offer,' 'dunning,' 'failed payment recovery,' 'win-back,' 'retention,' 'exit survey,' 'pause subscription,' 'involuntary churn,' 'people keep canceling,' 'churn rate is too high,' 'how do I keep users,' or 'customers are leaving.' Use this whenever someone is losing subscribers o
design-intelligence by event4u-app
Grounded design brief from the adopted corpus — style, WCAG-checked color tokens, typography, layout pattern, anti-patterns. Use on ui-design-brief or any which-style/palette/font/chart decision.
View original Skill.mdThis page is parsed directly from the repository SKILL.md without editorial rewriting. Collected: Jul 28, 2026 · about 1 min
终端操作
当用户需要真实的仓库执行时使用此技能：运行命令、检查 git 状态、调试 CI 或构建、进行窄幅修复，并准确报告更改和验证的内容。
此技能有意比通用编码指导更窄。它是一种以证据为先的终端执行操作工作流。
技能栈
在相关时，将这些 ECC 原生技能引入工作流：
verification-loop用于更改后的精确验证步骤tdd-workflow当正确的修复需要回归覆盖时security-review当涉及密钥、认证或外部输入时github-ops当任务依赖于 CI 运行、PR 状态或发布状态时knowledge-ops当需要将验证结果捕获到持久的项目上下文中时
使用时机
- 用户说"修复"、"调试"、"运行这个"、"检查仓库"或"推送它"
- 任务依赖于命令输出、git 状态、测试结果或已验证的本地修复
- 答案必须区分：本地已更改、本地已验证、已提交和已推送
安全护栏
- 先检查再编辑
- 如果用户仅要求审计/审查，则保持只读
- 优先使用仓库本地的脚本和辅助工具，而非即兴的临时封装
- 在验证命令重新运行之前，不得声称已修复
- 除非分支确实已推送到上游，否则不得声称已推送
工作流
1. 确定工作表面
明确：
- 确切的仓库路径
- 分支
- 本地差异状态
- 请求的模式：
- 检查
- 修复
- 验证
- 推送
2. 首先读取失败表面
在更改任何内容之前：
- 检查错误
- 检查文件或测试
- 检查 git 状态
- 在盲目重新读取之前，使用任何已提供的日志或上下文
3. 保持修复的窄幅
一次解决一个主要失败：
- 首先使用最小的有用验证命令
- 仅在本地失败解决后，才升级到更大的构建/测试流程
- 如果某个命令持续以相同特征失败，停止广泛重试并缩小范围
4. 报告确切的执行状态
使用确切的状态词：
- 已检查
- 本地已更改
- 本地已验证
- 已提交
- 已推送
- 已阻塞
输出格式
表面
- 仓库
- 分支
- 请求模式
证据
- 失败的命令 / 差异 / 测试
操作
- 变更内容
状态
- 已检查 / 本地已更改 / 本地已验证 / 已提交 / 已推送 / 已阻止
陷阱
- 当可以读取实时仓库状态时，不要依赖过时的记忆
- 不要将窄幅修复扩大为仓库范围的变动
- 不要使用破坏性的 git 命令
- 不要忽略不相关的本地工作
验证
- 响应中需指明验证命令或测试
- 与 git 相关的工作需指明仓库路径和分支
- 任何推送声明需包含目标分支和确切结果
- Source repo
- affaan-m/ECC
- Skill path
- docs/zh-CN/skills/terminal-ops/SKILL.md
- Commit SHA
- 4e973d3eaf92
- Repository license
- MIT
- Data collected