command-executor

Execute safe commands and capture stdout, stderr, and exit codes.

1|Updated Oct 31, 2025
One-click install
npx skills add https://github.com/d-oit/command-verify --skill command-executor
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: command-executor
Source: https://github.com/d-oit/command-verify/tree/main/command-executor/skills/command-executor
Command: npx skills add https://github.com/d-oit/command-verify --skill command-executor

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This Skill extends the command-verify functionality by actually running safe commands and capturing their real-time output. It eliminates the uncertainty of whether documentation examples or build steps truly work, preventing broken processes and ensuring the reliability of your project's instructions. It provides concrete proof of execution, saving you from manual testing and debugging.

Core Features & Use Cases

  • Safe Execution: Prioritizes safety by only running commands categorized as "Safe" or "Conditional" (with explicit user confirmation), preventing accidental destructive actions.
  • Output Capture: Records stdout, stderr, and exit codes for each command, providing verifiable results and detailed insights into execution.
  • Performance Comparison: Automatically detects performance regressions or unexpected output changes by comparing current runs with historical data, ensuring consistent performance.
  • Use Case: After updating your project's build scripts or CI/CD configurations, ask this Skill to "execute the safe commands." It will run npm run build, npm run test, and npm run lint, capturing their outputs and confirming they still function correctly, giving you peace of mind before deployment.

Quick Start

Execute all safe commands in the project and show their output.

Frequently Asked Questions about command-executor

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

FAQPage Schema
How do I execute and verify commands work correctly in my project?

Command execution captures real output—stdout, stderr, and exit codes—to verify that build steps, tests, and CI/CD commands actually run as documented. This eliminates guesswork about whether your project's instructions truly work before deployment.

Can I safely run commands without accidentally deleting files or breaking my system?

Safe execution prioritizes safety by only running commands marked as safe or conditional, requiring explicit confirmation for any potentially destructive actions. This prevents accidental damage while still letting you validate your automation.

How do I detect performance regressions when running build or test commands?

Performance comparison automatically detects output changes and performance regressions by comparing current command runs against historical cached results, surfacing unexpected behavior immediately.

What should I do after updating CI/CD configurations to confirm they still work?

Execute all safe commands in your project to capture their real-time output and confirm build, test, and lint steps function correctly. The Skill records results with timestamps and exit codes for audit verification.

How do I automate validation of documentation examples and build scripts?

Run commands through safe execution with output capture to prove documentation examples and build steps work as written. Persistent caching tracks results across runs, eliminating manual testing and preventing broken processes.