terminal-ops

Topics in the source

• Terminal Ops
• Skill Stack
• When to Use
• Guardrails
• Workflow
• 1. Resolve the working surface
• 2. Read the failing surface first
• 3. Keep the fix narrow

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. 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 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 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 act

This is an excerpt. Refer to the complete source and its current requirements.