Skip to main content
affpapa.org
RU EN
skill Claude Code CX Codex Cursor GitHub Copilot

terminal-ops — Claude skill: run commands, debug CI

A repo execution skill: runs commands, reads git state, debugs CI failures and makes narrow fixes with proof of what was actually verified.

Install into Claude Code · Skills CLI (Vercel) All methods and platforms ↓ 
npx skills add affaan-m/ECC --skill terminal-ops -a claude-code
Open on GitHub

What terminal-ops does

terminal-ops is an operator workflow, not general coding advice. It kicks in when the task depends on command output: a failing test, a broken build, a repo check, or a narrow fix you want pushed. The skill inspects the error, the file and git state before touching anything.

The workflow is spelled out in steps. First settle the working surface: repo path, branch, local diff, and the requested mode (inspect, fix, verify, push). Then read the failing surface, keep the fix narrow, and report with exact status words: inspected, changed locally, verified locally, committed, pushed, blocked. Output follows a fixed shape with SURFACE, EVIDENCE, ACTION and STATUS blocks.

It pulls in other ECC skills when they fit: verification-loop for proving steps, tdd-workflow when a fix needs regression coverage, security-review around secrets or auth, github-ops for CI and PR state, knowledge-ops to capture the outcome. Worth installing if you run an agent against a real repo and are tired of "should be fixed now". If you only want an audit, the skill stays read-only.

What it helps with

  • debug a failing CI run and find the cause
  • run a command in the repo and show its output
  • make a narrow fix and rerun the proving command
  • tell changed locally apart from committed and pushed
  • check git state before editing anything

Example prompts for the agent

  • run the tests in this repo and show me what fails
  • debug the CI failure on branch feature/auth, touch only that test
  • commit and push the fix, name the branch and the result

How to install terminal-ops

1Skills CLI (Vercel)

npx skills add affaan-m/ECC --skill terminal-ops -a claude-code

2Manually: put the files in place

~/.claude/skills/terminal-ops/SKILL.md

Copy the whole skill folder; for one project use .claude/skills/terminal-ops/

From the same set146

The whole set →
video-editing affaan-m AI-assisted workflow for editing, trimming, and enriching real footage. Connects raw recordings with FFmpeg cuts, Remotion overlays, and ElevenLabs voiceovers. Claude Code CX Codex Cursor +1 6,500installs docker-patterns affaan-m A skill with Dockerfile and Docker Compose patterns: local dev stacks, networking, volumes, container hardening. Claude Code CX Codex Cursor +1 6,300installs frontend-patterns affaan-m A skill for React and Next.js work: component patterns, state, data fetching, and render performance. Use it when building or reviewing UI. Claude Code CX Codex Cursor +1 5,900installs backend-patterns affaan-m A skill with backend patterns for Node.js, Express and Next.js API routes: layering, caching, transactions, error handling. Claude Code CX Codex Cursor +1 5,900installs coding-standards affaan-m Baseline cross-project coding conventions for naming, immutability, and clean code principles. Useful for code reviews and refactoring. Claude Code CX Codex Cursor +1 5,600installs api-design affaan-m Provides REST API design standards covering resource naming, status codes, pagination, and error payloads. Use it when creating or auditing API contracts. Claude Code CX Codex Cursor +1 5,500installs rust-testing affaan-m A skill for writing Rust tests: unit, integration, async, property-based, mocks and coverage. Useful when the project runs on TDD. Claude Code CX Codex Cursor +1 5,500installs laravel-security affaan-m This skill reviews Laravel authentication, Eloquent safety, CSRF, XSS, APIs, and production settings. Use it for security reviews or deployment checks. Claude Code CX Codex Cursor +1 5,400installs

Similar

google-cloud-networking-observability official google Investigate Google Cloud network logs, metrics, and connectivity paths. Use it to trace packet drops, firewall blocks, or routing problems. Claude Code Gemini CLI CX Codex 11,856installs cloudflare-deploy official openai This skill helps choose Cloudflare services and prepare application or infrastructure deployments through Workers, Pages, and related products. Claude Code CX Codex Cursor +1 4,300installs gcloud official Google LLC Validates gcloud commands, reduces command output, and adds execution guardrails for Google Cloud work. Use it when an agent handles the CLI. Claude Code Gemini CLI CX Codex 10,974installs agent-platform-skill-registry official google Connects agents to the Gemini Enterprise Agent Platform Skill Registry for discovery and lifecycle tasks. Useful when your workflow manages registered skills. Claude Code Gemini CLI CX Codex 10,068installs wizard Matt Pocock This skill creates an interactive bash wizard for manual setup steps, CI secrets, third-party dashboards, and one-off migrations. Claude Code 553,369installs hyperframes-cli heygen-com Controls HyperFrames video workflows from the CLI: audits layouts and contrast, edits timeline clips, captures snapshots, and renders locally or in cloud runtimes. Claude Code CX Codex Cursor +1 1,200,000installs setup-pre-commit Matt Pocock This skill configures pre-commit checks for a JavaScript repository, running Prettier, type checking, and tests before each commit. Claude Code 489,289installs using-git-worktrees Jesse Vincent Prepares an isolated workspace before feature work or plan execution. It checks the repository first, then uses native worktree support or Git. Claude Code CX Codex 217,153installs

Questions about terminal-ops

How do I install terminal-ops in Claude?

Run npx skills add affaan-m/ECC --skill terminal-ops -a claude-code. The skill lands at ~/.claude/skills/terminal-ops/SKILL.md.

What does terminal-ops do?

It drives an agent through a repo: runs commands, reads git, debugs CI and build failures, makes a narrow fix, and reports exactly what was verified.

How is terminal-ops different from general coding guidance?

It is deliberately narrower: a terminal execution workflow where the answer rests on command output. It will not claim a fix until the proving command has been rerun.

Source text

SKILL.md · MIT 
---
name: terminal-ops
description: 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.
metadata:
  origin: ECC
---

# 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

© affaan-m · MIT · affaan-m/ECC

See also

Project sponsors

Companies that keep this analytics open
Gold sponsor
Nutra.Club

Impressions, clicks and code copies — open statistics. We keep the numbers public for the same reason NeBlask itself is public. Become a sponsor