Skip to main content
Agent skill

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.

Get started

Get the complete skill folder, including its scripts and reference files.

When to use this skill

Use Terminal Ops when an AI agent needs a reusable SKILL.md workflow for this job: 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.

When not to use it

Skip Terminal Ops when the task is outside the coding category, or when a more specific skill in this directory already covers the same workflow with clearer triggers.

How to install

Where will you use it?

Install scope
Claude Code folder setup
mkdir -p ~/.claude/skills/terminal-ops
# Save SKILL.md to ~/.claude/skills/terminal-ops/SKILL.md
  1. Claude Code personal install: place the skill and its bundled files at ~/.claude/skills/terminal-ops/SKILL.md. For a shared project, commit the folder at .claude/skills/terminal-ops/ instead.
  2. Current Claude Code detects SKILL.md changes in watched directories during the session. If you just created a top-level skills directory, run /reload-skills. Check that the skill is listed before testing its trigger.
  3. For Claude chat or Cowork in the Desktop app, manage uploaded skills in Customize > Skills; copying files into a local Claude Code folder is not a Desktop install. Other agents may use different install locations.

Full install guide for Claude, Cursor, and Codex →

Try a starter prompt

After installing the skill, paste this starter prompt into your agent to verify it triggers on a small task.

Starter prompt
Use the Terminal Ops skill for this task: user says "fix", "debug", "run this", "check the repo", or "push it". Confirm any required inputs or files before making changes.

What supports this recommendation?

72/100 provisional content score. This measures documentation, practical detail and source signals. It is not a measured task success rate or a security certification.

Documentation
77/100
Practical detail
74/100
Source evidence
63/100
Source signals
70/100
Model compatibility evidence
  • claudeuntested

    No model-specific signal or recorded compatibility test was found.

  • chatgptuntested

    No model-specific signal or recorded compatibility test was found.

  • geminiuntested

    No model-specific signal or recorded compatibility test was found.

  • copilotuntested

    No model-specific signal or recorded compatibility test was found.

  • llamauntested

    No model-specific signal or recorded compatibility test was found.

  • perplexityuntested

    No model-specific signal or recorded compatibility test was found.

  • mistraluntested

    No model-specific signal or recorded compatibility test was found.

  • grokuntested

    No model-specific signal or recorded compatibility test was found.

Inferred compatibility is based on content signals. Check the app, its available tools and setup requirements before running a skill.

What this skill does

# 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

```text 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

Intended uses

  • 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

Implementation notes

  • Review the source instructions and adapt inputs before running the workflow.

Try it, then tell us how it went

A copied prompt does not tell us whether the task worked. Report your result after checking the output. We collect your tool and outcome, never your files or prompt.