cm-terminal

Announce, monitor, and verify terminal command output, stopping on errors.

48|23|Updated Mar 17, 2026
One-click install
npx skills add https://github.com/tody-agent/codymaster --skill cm-terminal
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: cm-terminal
Source: https://github.com/tody-agent/codymaster/tree/main/skills/cm-terminal
Command: npx skills add https://github.com/tody-agent/codymaster --skill cm-terminal

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Running terminal commands without verifying their outcomes leaves workflows blind and error-prone.

Core Features & Use Cases

  • Announce and log every command before execution to provide traceability.
  • Read and verify command output, stop on errors, and prevent cascading failures.
  • Apply to build, test, install, deploy, and routine scripting tasks to maintain discipline and reliability.

Quick Start

Instruct the AI to announce, monitor, and verify every terminal command before proceeding.

Frequently Asked Questions about cm-terminal

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

FAQPage Schema
How do I monitor terminal command output and stop execution on errors?

To monitor terminal command output and stop on errors, you need a structured execution protocol that reads output immediately, detects error patterns, and halts workflows to prevent cascading failures. This approach enforces strict command handling and updates task status upon failure.

What is the best way to log terminal commands before execution during deployments?

The best way to log terminal commands before execution is to announce each command prior to running it, providing full traceability for build, test, install, and deploy pipelines. This discipline maintains reliability across development and operations workflows.

Why does my automated build script keep running after a command failure?

Automated build scripts keep running after a failure because they lack strict error detection patterns and a protocol to halt on errors. Without immediate output reading and task status updates, workflows remain blind to failures and allow cascading issues.

Do I need structured command handling for routine devops scripting tasks?

Yes, you need structured command handling for routine devops scripting to maintain discipline and reliability. Enforcing strict monitoring, output verification, and error halts prevents error-prone workflows and ensures day-to-day operations remain visible and error-free.

Can I apply terminal output verification to both development and operations pipelines?

Yes, you can apply terminal output verification to both development and operations pipelines. The monitoring protocol works across builds, tests, installs, and deployments, ensuring structured command handling and immediate error detection regardless of the environment.