terminal-ops

Execute repository commands with deterministic proof and exact status reporting.

86|21|Updated Feb 9, 2026

Search Tags:#git #verification #repository #terminal #ci #evidence-first

Ready to run

npx skills add https://github.com/Jamkris/everything-gemini-code --skill terminal-ops-jamkris

💬 Prompt for ChatGPT / Claude Chat▼

Please help me install this Agent Skill.
Skill: terminal-ops
Source: https://github.com/Jamkris/everything-gemini-code/tree/main/skills/terminal-ops
Command: npx skills add https://github.com/Jamkris/everything-gemini-code --skill terminal-ops-jamkris

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

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

Core Features & Use Cases

Deterministic command execution and state capture
Exact proving commands after changes
Guardrails to prevent destructive edits
Structured, stepwise workflow from inspection to push

Quick Start

Ask me to inspect the repository surface and execute the smallest proving command to reproduce and verify the issue.

Frequently Asked Questions about terminal-ops

High-intent search queries and answers about installing and using this skill.

FAQPage Schema

How do I debug a CI failure by inspecting the git repository state?▼

Pushing narrow fixes with verifiable proof requires a stepwise workflow from read-only inspection to editing, deterministic proving, and pushing. This Skill executes precise terminal operations and reports exact statuses like inspected, changed locally, verified locally, committed, and pushed.

Can I execute terminal commands to reproduce a repository issue without making destructive edits?▼

Evidence-first repository operations require deterministic command execution and exact proving commands after changes. This Skill captures repository state, runs the smallest proving command to reproduce issues, and verifies fixes locally before committing.

What is the best way to verify a repository change locally before committing?▼

The best way to verify a repository change locally is to use deterministic proving commands after making edits. This Skill enforces an evidence-first workflow that reports exact statuses like changed locally and verified locally before allowing a commit.

Does this evidence-first terminal workflow support pushing narrow fixes to git repositories?▼

This evidence-first terminal workflow supports pushing narrow fixes to git repositories by following a strictly defined process. It progresses stepwise from inspection to local verification, committing, and finally pushing with exact proof of what was executed.