$ ~/registry/skill/affaan-m-terminal-ops

SKILL

terminal-ops

Name: terminal-ops
Author: affaan-m

Run repo tasks, debug CI, and deliver fixes with verified evidence.

Stars

★ 229,796

Source

GitHub

Updated

2026-07-15

// securityLow risk

Prompt only, no code
Open source
Community-trusted· 229.8k

Running security audit…

Credentials
Network egress
Code execution
Data access
Supply chain

// install

Copy the install command and let the AI configure it · recommended for beginners

Please install the "terminal-ops" skill from askskill:
1. Download https://raw.githubusercontent.com/affaan-m/ECC/main/skills/terminal-ops/SKILL.md
2. Save it as ~/.claude/skills/terminal-ops/SKILL.md
3. Reload skills and tell me it's ready

// download

Download SKILL.mdInstall manifest ↗

// examples

Debug a CI failure

Prompt

Please inspect the latest CI failure in this repo, reproduce the failure, identify the exact error, and propose the smallest possible fix. Clearly list the commands you ran, key outputs, and verification results.

Expected

A report with the root cause, reproduction and fix steps, executed commands, and proof that the fix passes verification.

Run repository checks

Prompt

Run tests, lint, and type checks in this repository, summarize all failures, and prioritize what should be fixed first. Include evidence for each step you executed.

Expected

An overview of check results, categorized failures, priority recommendations, and evidence from the corresponding commands and outputs.

Apply a narrow fix

Prompt

Apply the smallest possible fix for this specific bug without refactoring unrelated code. Afterward, show the changes made, the validation commands you ran, and why the fix is confirmed.

Expected

A precise summary of changes, affected files, validation logs, and verifiable evidence that the fix works.

// docs

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