terminal-ops

Execute evidence-first repository operations with terminal and git verification.

Updated Jun 24, 2026
One-click install
npx skills add https://github.com/mostafa-ismail-2004/codex-plugin --skill terminal-ops-mostafa-ismail-2004
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: terminal-ops
Source: https://github.com/mostafa-ismail-2004/codex-plugin/tree/main/skills/terminal-ops
Command: npx skills add https://github.com/mostafa-ismail-2004/codex-plugin --skill terminal-ops-mostafa-ismail-2004

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Terminal Ops removes guesswork from repository work by turning debugging, verification, and narrow fixes into an evidence-first workflow that records exactly what was inspected and changed.

Core Features & Use Cases

  • Command-driven execution: Run repo commands, inspect test failures, and check git state before making edits.
  • Narrow fix workflow: Address one dominant issue at a time and avoid broad, speculative changes.
  • Proof-based reporting: Confirm changes with rerun verification commands and report whether work is inspected, changed locally, verified locally, committed, or pushed.
  • Use Case: A CI job fails, and you need the assistant to inspect the failure, make the smallest safe fix, rerun the proof command, and summarize the result precisely.

Quick Start

Use the terminal-ops skill to inspect the repo, diagnose the failing command, apply the smallest safe fix, and verify the result with exact evidence.

Frequently Asked Questions about terminal-ops

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I debug a failing CI job using git and terminal evidence?

Debug a failing CI job by running an evidence-first workflow that inspects command failures, checks git state, and reports exact execution proof. The terminal-ops process inspects repo failures, applies minimal safe fixes, and reruns verification commands to confirm the result.

What is the best way to verify local repository changes before pushing?

Verify local repository changes by rerunning the exact proof commands that initially failed or triggered the edit. This verification workflow records whether work is inspected, changed locally, verified locally, committed, or pushed, ensuring exact execution evidence before pushing code.

How do I apply a minimal safe fix to a command failure in my repo?

Apply a minimal safe fix by inspecting the specific command failure, addressing one dominant issue at a time, and avoiding broad speculative changes. The terminal-ops workflow diagnoses the failure, makes the smallest safe edit, and reruns the command to verify the result.

Can I inspect git state and troubleshoot repository issues without making broad code changes?

Inspect git state and troubleshoot repository issues safely using an inspection-first workflow that enforces minimal change scope. Terminal operations record exactly what was inspected and changed, ensuring narrow code fixes that target one dominant issue without speculative edits.

Does terminal-ops work without external dependencies for local repair workflows?

Terminal-ops runs local repair workflows without external dependencies, executing repository operations using built-in terminal and git commands. It applies evidence-first debugging to command failures and CI troubleshooting, requiring no additional packages to inspect, fix, and verify code.

Why should I use an evidence-first workflow for debugging and verification?

Use an evidence-first workflow for debugging and verification to remove guesswork from repository work. Terminal-ops records exactly what was inspected and changed, providing explicit verification reporting with terminal and git evidence to prove that local fixes are successfully verified.