terminal-ops

Resolve the working surface by identifying the exact repo path, branch, and local diff state before making changes. Inspecting git state and error outputs first ensures you apply narrow, proven terminal commands to debug CI failures.

An evidence-first workflow for repository fixes involves inspecting the error output and git state before making changes. It reports exact execution state—inspected, changed locally, verified locally, committed, pushed, or blocked—providing auditable proof of actions.

Yes, you can run a read-only audit on a repository without applying edits. When the requested mode is audit or review only, the system inspects the git state and files while making no modifications to the repository.

Verify terminal execution by running deterministic commands and reporting exact outcomes with auditable traces. The system provides explicit statuses like inspected, verified locally, or blocked to confirm what was executed and checked.

Yes, this terminal execution approach integrates natively with verification-loop, tdd-workflow, security-review, github-ops, and knowledge-ops. This synergy embeds deterministic terminal execution and auditable traces directly into broader CI and security review workflows.

You should avoid broad fixes when operating a repository. The system keeps fixes narrow by reading the failing surface first and using proven commands, ensuring changes are isolated, verifiable, and do not introduce unintended side effects.