---
id: daily-terminal-ops
name: "terminal-ops"
url: https://skills.yangsir.net/skill/daily-terminal-ops
author: affaan-m
domain: ai-ci-cd-deployment
tags: ["devops", "automation", "git", "ci-cd", "debugging"]
install_count: 2500
rating: 4.30 (25 reviews)
github: https://github.com/affaan-m/everything-claude-code
---

# terminal-ops

> 真实仓库执行操作，运行命令、检查 Git 状态、调试 CI/CD、精确修复问题并报告变更和验证结果

**Stats**: 2,500 installs · 4.3/5 (25 reviews)

## Before / After 对比

### 故障排查

**Before**:

手动执行命令、查看日志、测试修复，一个 CI 故障需要 30-60 分钟定位和解决

**After**:

自动收集 Git 状态、日志和测试结果，智能分析根因，生成修复方案并验证

| Metric | Before | After | Change |
|---|---|---|---|
| 排障时间 | 45分钟 | 8分钟 | -82% |

## Readme

# terminal-ops

# Terminal Ops

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.

## Skill Stack

Pull these ECC-native skills into the workflow when relevant:

- `verification-loop` for exact proving steps after changes

- `tdd-workflow` when the right fix needs regression coverage

- `security-review` when secrets, auth, or external inputs are involved

- `github-ops` when the task depends on CI runs, PR state, or release status

- `knowledge-ops` when the verified outcome needs to be captured into durable project context

## When to Use

- user says "fix", "debug", "run this", "check the repo", or "push it"

- the task depends on command output, git state, test results, or a verified local fix

- the answer must distinguish changed locally, verified locally, committed, and pushed

## Guardrails

- inspect before editing

- stay read-only if the user asked for audit/review only

- prefer repo-local scripts and helpers over improvised ad hoc wrappers

- do not claim fixed until the proving command was rerun

- do not claim pushed unless the branch actually moved upstream

## Workflow

### 1. Resolve the working surface

Settle:

- exact repo path

- branch

- local diff state

- requested mode:

inspect

- fix

- verify

- push

### 2. Read the failing surface first

Before changing anything:

- inspect the error

- inspect the file or test

- inspect git state

- use any already-supplied logs or context before re-reading blindly

### 3. Keep the fix narrow

Solve one dominant failure at a time:

- use the smallest useful proving command first

- only escalate to a bigger build/test pass after the local failure is addressed

- if a command keeps failing with the same signature, stop broad retries and narrow scope

### 4. Report exact execution state

Use exact status words:

- inspected

- changed locally

- verified locally

- committed

- pushed

- blocked

## Output Format

```
SURFACE
- repo
- branch
- requested mode

EVIDENCE
- failing command / diff / test

ACTION
- what changed

STATUS
- inspected / changed locally / verified locally / committed / pushed / blocked

```

## Pitfalls

- do not work from stale memory when the live repo state can be read

- do not widen a narrow fix into repo-wide churn

- do not use destructive git commands

- do not ignore unrelated local work

## Verification

- the response names the proving command or test

- git-related work names the repo path and branch

- any push claim includes the target branch and exact result

Weekly Installs530Repository[affaan-m/everyt…ude-code](https://github.com/affaan-m/everything-claude-code)GitHub Stars157.6KFirst Seen11 days agoSecurity Audits[Gen Agent Trust HubPass](/affaan-m/everything-claude-code/terminal-ops/security/agent-trust-hub)[SocketPass](/affaan-m/everything-claude-code/terminal-ops/security/socket)[SnykPass](/affaan-m/everything-claude-code/terminal-ops/security/snyk)Installed oncodex500opencode484gemini-cli481github-copilot480kimi-cli480antigravity480

---
*Source: https://skills.yangsir.net/skill/daily-terminal-ops*
*Markdown mirror: https://skills.yangsir.net/api/skill/daily-terminal-ops/markdown*