terminal-ops

The terminal-ops skill provides a focused, evidence-first workflow for executing and verifying operations directly in a repository. It is designed to handle tasks that involve running commands, inspecting git states, debugging CI failures, and applying narrow fixes with precise proof of execution and verification. Unlike general coding guidance tools, this skill emphasizes controlled and auditable operations, ensuring that all actions are traceable and confirmed before claims of success or deployment are made.

Its main features include a structured workflow for resolving the working surface, carefully reading failing surfaces before intervention, keeping fixes narrow and targeted, and reporting the exact execution state. The skill leverages complementary ECC-native skills such as verification-loop, tdd-workflow, security-review, github-ops, and knowledge-ops, which support regression testing, security considerations, CI interactions, and knowledge capture. Output is standardized to show the surface, evidence, actions taken, and precise status (inspected, changed locally, verified locally, committed, pushed, or blocked), making it ideal for reproducible and verifiable development tasks.

Terminal-ops is primarily aimed at developers and operators who require precise, evidence-backed control over repository actions. It is useful for scenarios where a user needs to debug a build, apply a minimal fix, or verify that a change has been correctly applied and pushed. It is also beneficial for code reviewers and team members who need to audit operations without risk of unintended changes. By enforcing narrow, verifiable workflows, terminal-ops reduces the risk of accidental repository-wide modifications and ensures that every action is accountable and reproducible.