Enforce non-interactive shell execution in CI environments.
npx skills add https://github.com/iyaki/opencode-base-template --skill shell-command
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
This Skill enforces non-interactive shell execution in OpenCode environments by default, ensuring commands do not hang due to prompts or editors.
Run a non-interactive shell command sequence in a CI environment to ensure commands complete without prompts.
High-intent search queries and answers about installing and using this skill.
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.
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.
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.
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.
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.
jralphConfigure shell commands with non-interactive flags and environment variables for headless automation.
obraVerify completion claims by running commands and checking output.
AreteDriverImplements CI/CD pipelines using Batcomputer for automated code review and deployment gating.
shalevaminDevelop CLI tools with argument parsing, prompts, and shell completions.
