oberconcejo/VS-CODE / .agents/skills/terminal-ops
terminal-ops
VerifiedEvidence-first repo execution workflow for ECC. Use when the user wants a command run, a repo checked, a CI failure debugged, or a narrow fix pushed with exact proof of what was executed and verified.
Terminal Ops
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.
Skill Stack
Pull these ECC-native skills into the workflow when relevant:
verification-loopfor exact proving steps after changestdd-workflowwhen the right fix needs regression coveragesecurity-reviewwhen secrets, auth, or external inputs are involvedgithub-opswhen the task depends on CI runs, PR state, or release statusknowledge-opswhen the verified outcome needs to be captured into durable project context
When to Use
- 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
Guardrails
- 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 actually moved upstream
Workflow
1. Resolve the working surface
Settle:
- exact repo path
- branch
- local diff state
- requested mode:
- inspect
- fix
- verify
- push
2. Read the failing surface first
Before changing anything:
- inspect the error
- inspect the file or test
- inspect git state
- use any already-supplied logs or context before re-reading blindly
3. Keep the fix narrow
Solve one dominant failure at a time:
- use the smallest useful proving command first
- only escalate to a bigger build/test pass after the local failure is addressed
- if a command keeps failing with the same signature, stop broad retries and narrow scope
4. Report exact execution state
Use exact status words:
- inspected
- changed locally
- verified locally
- committed
- pushed
- blocked
Output Format
SURFACE
- repo
- branch
- requested mode
EVIDENCE
- failing command / diff / test
ACTION
- what changed
STATUS
- inspected / changed locally / verified locally / committed / pushed / blocked
Pitfalls
- do not work from stale memory when the live repo state can be read
- do not widen a narrow fix into repo-wide churn
- do not use destructive git commands
- do not ignore unrelated local work
Verification
- the response names the proving command or test
- git-related work names the repo path and branch
- any push claim includes the target branch and exact result
Related skills
| Skill | Stars | Updated | Works with | Status | Install |
|---|---|---|---|---|---|
| planning-and-task-breakdownaddyosmani/agent-skillsBreaks work into ordered tasks. Use when you have a spec or clear requirements and need to break work into implementable tasks. Use when a task feels too large to start, when you need to estimate scope, or when parallel work is possible. | Stars: 118k | Updated | Claude CodeCodex | Verified | Install |
| screenpipethedotmack/claude-memSearch screen and audio history recorded by Screenpipe and optionally save selected context into claude-mem. Use when the user asks to recall desktop activity, a meeting, or something seen in another app through Screenpipe. | Stars: 117k | Updated | Claude CodeCodex | Verified | Install |
| contact-widgetnexu-io/open-designSelf-contained floating chat widget with welcome screen, social links, meeting button, and message input. Single HTML file, zero dependencies. | Stars: 108k | Updated | Claude CodeCodex | Verified | Install |
| meeting-notesnexu-io/open-designMeeting notes page — title bar with attendees, agenda checklist, decisions block, action items table with owners + dates, and a "next meeting" footer. Use when the brief mentions "meeting notes", "minutes", "1:1 notes", "all-hands recap", or "会议纪要". | Stars: 108k | Updated | Claude CodeCodex | Verified | Install |