Terminal Ops

When you need to fix something in a repo and prove you actually fixed it, this is the workflow. It's narrower than general coding help: you inspect first, make the smallest change that solves the problem, run the proving command, and report exactly what state things are in (changed locally, verified, committed, pushed). The guardrails are sensible: don't claim it's fixed until you reran the test, don't say you pushed unless the branch actually moved upstream, and don't turn a one-line fix into repo-wide churn. It pulls in other ECC skills like verification-loop and tdd-workflow when the fix needs real coverage. Good for CI failures, debug sessions, and anything where "trust me" isn't enough.

skills.sh installs: 3.6K
GitHub stars: 229.1K
last updated: Jul 14, 2026

View on GitHub

Install

$ npx -y skills add affaan-m/everything-claude-code --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