shell-command

Enforce non-interactive shell execution in CI environments.

Updated Sep 25, 2025

Search Tags:#automation #shell #command-line #guardrails #ci #non-interactive

Ready to run

npx skills add https://github.com/iyaki/opencode-base-template --skill shell-command

💬 Prompt for ChatGPT / Claude Chat▼

Please help me install this Agent Skill.
Skill: shell-command
Source: https://github.com/iyaki/opencode-base-template/tree/main/.agents/skills/shell-command
Command: npx skills add https://github.com/iyaki/opencode-base-template --skill shell-command

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This Skill enforces non-interactive shell execution in OpenCode environments by default, ensuring commands do not hang due to prompts or editors.

Core Features & Use Cases

Enforces CI-friendly behavior: automatically applies non-interactive flags and environment settings.
Guardrails for shell commands: blocks prompts, editors, and interactive prompts in scripts.
Use Case: When deploying automation workflows in headless CI, this skill ensures commands complete without awaiting user input.

Quick Start

Run a non-interactive shell command sequence in a CI environment to ensure commands complete without prompts.

Frequently Asked Questions about shell-command

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

FAQPage Schema

Why do shell commands hang in CI environments?▼

Shell commands hang in CI environments when scripts trigger interactive prompts or open editors awaiting user input. Enforcing non-interactive shell execution with strict guardrails prevents these automated pipelines from stalling indefinitely.

How do I prevent shell scripts from waiting for user input in automated pipelines?▼

To prevent shell scripts from waiting for user input in automated pipelines, apply non-interactive flags and safe environment defaults. Setting CI=true and disabling editors and pagers ensures commands execute deterministically without halting.

What environment variables are needed for safe non-interactive shell execution?▼

Safe non-interactive shell execution requires the CI=true environment variable to signal headless operation. Disabling editors and pagers alongside applying strict guardrails further ensures commands complete without awaiting user input.

Does this approach work with existing CI automation workflows?▼

Yes, this approach works with existing CI automation workflows by automatically applying non-interactive flags and safe environment settings across your scripts. It enforces deterministic shell behavior without requiring manual command rewrites.

What are the limitations of using guardrails for non-interactive shell execution?▼

The limitation of using guardrails for non-interactive shell execution is that strictly blocking prompts means any command genuinely requiring user interaction will fail. This approach is designed exclusively for deterministic, headless CI pipelines.