Terminal Ops

This is the workflow for when someone says "fix it" or "run this" and you need to execute commands, inspect git state, and report exactly what happened. It's deliberately narrow: read the failure first, make the smallest fix that addresses it, verify with the actual proving command, and use precise status words like "changed locally" versus "pushed." The guardrails are sensible, no destructive git ops, no claiming something is fixed until you rerun the test, no working from memory when you can read the live repo. It pulls in other ECC skills like verification-loop or tdd-workflow when the fix needs more rigor. Useful when the difference between "I changed it" and "I verified it and pushed it" actually matters.

skills.sh installs: 5.4K
GitHub stars: 300.3K
last updated: Aug 21, 2026

View on GitHub

Install

$ npx -y skills add affaan-m/ecc --skill terminal-ops --agent claude-code

Installs into .claude/skills of the current project.

Files

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