terminal-ops

What problem does it solve?

This skill defines an evidence-first operator workflow for running commands, inspecting repository and git state, reproducing failures, applying narrow fixes, and reporting exact proof of what was executed and verified so users can trust claims about local verification and pushes.

Core Features & Use Cases

• Inspect before edit: Read failing commands, logs, files, and git status before making any changes to avoid destructive actions.
• Narrow, provable fixes: Run the smallest useful proving command, re-run failing tests or commands, and record exact outputs that demonstrate verification.
• Clear execution states: Use explicit status words (inspected, changed locally, verified locally, committed, pushed, blocked) and include repo path and branch with any git-related claims.
• Integration-ready: Pull in complementary MCC skills such as verification-loop, tdd-workflow, security-review, and github-ops when relevant.
• Use Case: Debug a failing CI job by reproducing the failure locally, applying a minimal code or config change, re-running the proving command, committing the fix, and pushing with exact evidence.

Quick Start

Ask the assistant to run the failing command or test, inspect the repo path and branch, reproduce the failure, propose a narrow fix, and provide the proving command and verification steps.