terminal-ops

Execute repository operations with evidence-first proving commands and exact git reporting.

Updated Sep 13, 2025

Search Tags:#git #verification #terminal #evidence-first #ci debugging #repo execution #narrow fix

Ready to run

npx skills add https://github.com/llmh333/employee_management_spring --skill terminal-ops-llmh333

💬 Prompt for ChatGPT / Claude Chat▼

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

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Evidence-first terminal execution for fixing or debugging a repository while clearly separating what was inspected, changed, verified, committed, and pushed.

Core Features & Use Cases

Evidence-first execution workflow: Resolves the working surface (repo path, branch, diff state) and selects a requested mode such as inspect, fix, verify, or push.
Narrow, testable fixes: Reads the failing surface first (errors, files, tests, git state), then keeps the change minimal and escalates only when needed.
Exact reporting of operational outcomes: Produces an auditable status narrative with proof commands/tests and a precise git/push result.

Quick Start

Ask the AI to run a specific proving command on the current branch of the employee_management_spring repository, then report the exact output and whether any local changes were made.

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 build failure using terminal commands without making untracked changes?▼

Debug CI build failures by running minimum proving commands to inspect errors and git state first. This evidence-first terminal execution ensures changes remain narrow, testable, and audited before committing or pushing any repository modifications.

What is evidence-first execution for investigating repository errors?▼

Evidence-first execution resolves the working surface like repo path and branch, then reads failing tests or errors before applying fixes. It requires inspecting before editing and rerunning proving steps to verify the exact terminal and git outcomes.

How do I verify a narrow git patch by rerunning the original failing command?▼

Verify a narrow git patch by rerunning the exact proving command that initially failed. The workflow mandates reading the failing surface first, applying a minimal fix, and executing verification steps to report precise execution outcomes.

Can I use terminal execution to inspect and push audited repository changes on a specific branch?▼

Yes, you can inspect and push audited repository changes by selecting a mode like inspect, fix, verify, or push. The process resolves the branch and diff state, applies guardrails, and reports exact git push results in a standardized format.

What are the limitations of using automated terminal fixes for repository operations?▼

Automated terminal fixes require strict guardrails and should not be used without inspecting the current git state first. Limitations include the necessity to rerun proving steps before claiming a fix and escalating changes only when a narrow patch is insufficient.