What does this skill do?

Terminal Skill Operations provides an operational workflow for performing actual actions on a repository: running commands, inspecting Git status, debugging continuous integration or builds, applying targeted fixes, and reporting with precise evidence what was changed and verified. It clearly distinguishes between inspection, local correction, verification, and pushing to the remote.

Read-only inspection
Check the Git status, the diff against the remote, and the recent history before making any changes.
Debugging Test Errors
Identify the test that fails, read the file in question, and apply the minimum necessary correction.
CI or build correction
Investigate the continuous integration failure, reduce the scope, and test using the smallest command.
Push verified to the remote server
Commit and push changes only after rerunning the test that verifies the bug has been fixed.

Usage examples

🐛 Debugging a test
The AuthService test is failing; debug it and apply the minimum necessary fix.
🔍 Check out the repo
Check the repository status in read-only mode: status, log, and diff against origin/main.
🔧 Fixing a CI issue
The CI build fails during the lint step; check the error and fix only what is necessary.
📤 Upload verified changes
Fix the compilation error, check what's happening, and push to the feat/auth-refresh branch.

Features

Evidence-Based Workflow Check the repository's live status before taking any action: error, file, test, and logs are available.
Surgical correction Fix one dominant bug at a time using the smallest, most useful test case.
Verification Before Reporting Run the command again to verify that the issue has been resolved before marking it as "fixed."
Structured Report Four clear sections: SURFACE, EVIDENCE, ACTION, and STATUS, with precise status descriptions.
Inspect, Fix, Verify, and Push modes It clearly distinguishes between inspection, local correction, verification, and uploading to the remote server.

Frequently asked questions

Four modes: inspect (read-only), fix (local correction), verify (verify changes), and push (commit and push to the remote).
No. The skill prevents destructive Git commands and does not expand a narrow fix into a global refactor of the repository.
No. The skill works with terminal and Git access from Claude Code or Cowork. It does not require setting up any external MCP.
Using a structured format with four sections: SURFACE (repo, branch, mode), EVIDENCE (command or diff), ACTION (change applied), and STATUS (inspected, changed locally, verified locally, committed, pushed, or blocked).
Terminal Operations — Debugging and Correcting Repositories with Claude AI

¿Prefieres escuchar el contenido? Genera la narración de audio con un clic.