OpenCode Shell Strategy

https://github.com/jredeker/opencode-shell-strategy
Admin
A plugin for OpenCode that provides instructions to LLMs for executing non-interactive shell...
Tokens:12,407
Snippets:131
Trust Score:8
License:MIT
Update:1 month ago
Show doc for...
Tokens:
Raw
### apt-get install -y

Source: https://github.com/jredeker/opencode-shell-strategy/blob/trunk/_autodocs/api-reference/shell_strategy.md

Installs a package without prompting for confirmation.

```bash
apt-get install -y pkg
```

--------------------------------

### pip install --no-input

Source: https://github.com/jredeker/opencode-shell-strategy/blob/trunk/_autodocs/api-reference/shell_strategy.md

Installs a package without interactive prompts.

```bash
pip install --no-input pkg
```

--------------------------------

### apt-get install non-interactive

Source: https://github.com/jredeker/opencode-shell-strategy/blob/trunk/shell_strategy.md

apt-get install is interactive by default; use -y to avoid prompts.

```bash
apt-get install pkg
```

```bash
apt-get install -y pkg
```

--------------------------------

### Configure OpenCode with remote instruction file

Source: https://github.com/jredeker/opencode-shell-strategy/blob/trunk/README.md

Add the remote instruction file to your OpenCode configuration. Restart OpenCode to load the rules automatically at the start of each session.

```json
{
  "instructions": [
    "https://raw.githubusercontent.com/JRedeker/opencode-shell-strategy/trunk/shell_strategy.md"
  ]
}
```

--------------------------------

### npm install non-interactive

Source: https://github.com/jredeker/opencode-shell-strategy/blob/trunk/shell_strategy.md

npm install is non-interactive by default. Use it directly; do not pass a blanket --yes or --force flag.

```bash
npm install
```

```bash
npm install
```

--------------------------------

### pip install non-interactive

Source: https://github.com/jredeker/opencode-shell-strategy/blob/trunk/shell_strategy.md

pip install is interactive by default; use --no-input to avoid prompts.

```bash
pip install pkg
```

```bash
pip install --no-input pkg
```

--------------------------------

### Derived values: DOCS_DIR, README, STRATEGY, PROG

Source: https://github.com/jredeker/opencode-shell-strategy/blob/trunk/_autodocs/api-reference/test.sh.md

Sets up the script's key variables. DOCS_DIR defaults to '.', README and STRATEGY point to the files to verify, and PROG is the basename of the script.

```sh
DOCS_DIR="${DOCS_DIR:-.}"
README="$DOCS_DIR/README.md"
STRATEGY="$DOCS_DIR/shell_strategy.md"
PROG=$(basename "$0")
```

--------------------------------

### npm init -y non-interactive

Source: https://github.com/jredeker/opencode-shell-strategy/blob/trunk/_autodocs/api-reference/shell_strategy.md

Use to initialize a package without prompts. Equivalent to npm init --yes.

```bash
npm init -y
```

--------------------------------

### Usage signature: ./test.sh [red|green|verify]

Source: https://github.com/jredeker/opencode-shell-strategy/blob/trunk/_autodocs/api-reference/test.sh.md

Shows the command-line usage of test.sh. The script accepts an optional positional argument: green (default), verify (alias for green), or red (inverted exit semantics for mutation testing). Any other value prints usage and exits 2.

```sh
./test.sh [red|green|verify]
```

--------------------------------

### package.json entry point for opencode-shell-non-interactive-strategy

Source: https://github.com/jredeker/opencode-shell-strategy/blob/trunk/_autodocs/api-reference/shell_strategy.md

Declares the package entry point as shell_strategy.md, making it the primary exported artifact loaded by OpenCode as an instruction file.

```json
{
  "name": "opencode-shell-non-interactive-strategy",
  "version": "1.1.0",
  "main": "shell_strategy.md"
}
```

--------------------------------

### mv -i a b

Source: https://github.com/jredeker/opencode-shell-strategy/blob/trunk/_autodocs/api-reference/shell_strategy.md

Prompts before overwriting b.

```bash
mv -i a b
```

--------------------------------

### cp -i a b

Source: https://github.com/jredeker/opencode-shell-strategy/blob/trunk/_autodocs/api-reference/shell_strategy.md

Prompts before overwriting b.

```bash
cp -i a b
```

--------------------------------

### ./test.sh [red|green|verify]

Source: https://github.com/jredeker/opencode-shell-strategy/blob/trunk/_autodocs/api-reference/test.sh.md

Command-line interface for the test.sh verification script. It accepts an optional positional argument to control the expected outcome and uses environment variables for configuration.

```APIDOC
## [SCRIPT] ./test.sh [red|green|verify]

### Description
Verification script for the shell strategy rule set. It checks the documentation files and exits with a status code indicating success or failure based on the expected outcome.

### Method
CLI invocation

### Endpoint
`./test.sh [red|green|verify]`

### Parameters
#### Positional Arguments
- **phase** (string) - Optional - The verification phase: `green` (default) or `verify` expect zero failures; `red` expects failures (inverted exit semantics). Any other value prints usage and exits with code 2.

#### Environment Variables
- **DOCS_DIR** (string) - Optional - Directory containing `README.md` and `shell_strategy.md` to verify. Defaults to `.`.
- **TMPDIR** (string) - Optional - Base directory for the per-run scratch directory. Defaults to `/tmp`.

### Request Example
```sh
./test.sh verify
```

### Response
#### Success Response (exit 0)
- All checks passed when phase is `green` or `verify`; or failures exist when phase is `red`.

#### Failure Response (exit 1)
- Failures exist when phase is `green` or `verify`; or no failures when phase is `red`.

#### Usage Error (exit 2)
- Invalid phase argument; prints usage message to stderr.

#### Response Example
```sh
# Example output (not specified in source)
```
```

--------------------------------

### Validate failure detection with ./test.sh red

Source: https://github.com/jredeker/opencode-shell-strategy/blob/trunk/_autodocs/api-reference/test.sh.md

Use this only when checking the fixture's failure detection. It copies the docs to /tmp/t, appends a prohibited 'sudo -S pkg' block, and runs with DOCS_DIR=/tmp/t. The script reports 'FAIL: <file>:<line> contains prohibited pattern: sudo -S' and exits 0 because the red phase expects failures.

```sh
# Only if checking the fixture's failure detection
cp -r /workspace/home/opencode-shell-strategy /tmp/t
printf '\n```sh\nsudo -S pkg\n```\n' >> /tmp/t/shell_strategy.md
DOCS_DIR=/tmp/t ./test.sh red
# FAIL: <file>:<line> contains prohibited pattern: sudo -S
# exit code 0 (red phase: expected failures found)
```

--------------------------------

### SSH first contact with accept-new and timeout

Source: https://github.com/jredeker/opencode-shell-strategy/blob/trunk/README.md

Use for an explicitly trusted first contact with a new host. The command fails if the host key changes; do not use StrictHostKeyChecking=no.

```bash
ssh -o BatchMode=yes -o StrictHostKeyChecking=accept-new -o ConnectTimeout=10 user@host
```

--------------------------------

### npm init non-interactive

Source: https://github.com/jredeker/opencode-shell-strategy/blob/trunk/shell_strategy.md

npm init is interactive by default; use npm init -y for non-interactive initialization. npm init -y is the documented shorthand for npm init --yes.

```bash
npm init
```

```bash
npm init -y
```

--------------------------------

### Basic verification with ./test.sh verify

Source: https://github.com/jredeker/opencode-shell-strategy/blob/trunk/_autodocs/api-reference/test.sh.md

Run the documented CI usage to verify the required safe form 'BatchMode=yes' is present. On success, the script prints 'OK: required safe form 'BatchMode=yes' found', followed by all checks, and ends with 'PASS: 0 failures' and exit code 0.

```sh
./test.sh verify
# OK: required safe form 'BatchMode=yes' found
# ... (all checks) ...
# PASS: 0 failures
# exit code 0
```

--------------------------------

### mv file operations

Source: https://github.com/jredeker/opencode-shell-strategy/blob/trunk/shell_strategy.md

mv -i prompts before overwrite. Use mv a b if you accept the default, or mv -f a b if overwrite is intended.

```bash
mv -i a b
```

```bash
mv a b
```

```bash
mv -f a b
```

--------------------------------

### git add <file>

Source: https://github.com/jredeker/opencode-shell-strategy/blob/trunk/_autodocs/api-reference/shell_strategy.md

Adds a specific file without interactive prompting.

```bash
git add <file>
```

--------------------------------

### cp file operations

Source: https://github.com/jredeker/opencode-shell-strategy/blob/trunk/shell_strategy.md

cp -i prompts before overwrite. Use cp a b if you accept the default, or cp -f a b if overwrite is intended.

```bash
cp -i a b
```

```bash
cp a b
```

```bash
cp -f a b
```

--------------------------------

### rm -i file

Source: https://github.com/jredeker/opencode-shell-strategy/blob/trunk/_autodocs/api-reference/shell_strategy.md

Prompts before removing a file.

```bash
rm -i file
```

--------------------------------

### Authorized non-interactive flags: apt-get -y, npm init -y, pip --no-input

Source: https://github.com/jredeker/opencode-shell-strategy/blob/trunk/shell_strategy.md

Use these commands when the requested action is already authorized and the tool provides a non-interactive flag. Each command uses a documented flag to avoid interactive prompts.

```bash
apt-get install -y pkg
npm init -y
pip install --no-input pkg
```

--------------------------------

### Check test.sh verify exit status in shell

Source: https://github.com/jredeker/opencode-shell-strategy/blob/trunk/_autodocs/errors.md

Use this POSIX shell pattern to run the test.sh verify command and check its exit status. If the command succeeds, print a success message; otherwise capture the exit code, print a failure message, and exit with that code. Note that exit code 2 indicates an invalid invocation (e.g., wrong phase argument), not non-compliance.

```sh
if ./test.sh verify; then
  echo "strategy docs compliant"
else
  rc=$?
  echo "verification failed (exit $rc)"
  exit "$rc"
fi
```

--------------------------------

### unzip overwrite without prompting

Source: https://github.com/jredeker/opencode-shell-strategy/blob/trunk/shell_strategy.md

Overwrites existing files without prompting.

```bash
unzip -o file.zip
```

--------------------------------

### mv -f a b

Source: https://github.com/jredeker/opencode-shell-strategy/blob/trunk/_autodocs/api-reference/shell_strategy.md

Forces overwrite without prompting.

```bash
mv -f a b
```

--------------------------------

### git add non-interactive

Source: https://github.com/jredeker/opencode-shell-strategy/blob/trunk/shell_strategy.md

git add -p is interactive; use git add <file> to add a specific file non-interactively.

```bash
git add -p
```

```bash
git add <file>
```

--------------------------------

### node non-interactive

Source: https://github.com/jredeker/opencode-shell-strategy/blob/trunk/shell_strategy.md

node is interactive; use node -e "code" for non-interactive execution.

```bash
node
```

```bash
node -e "code"
```

--------------------------------

### cp -f a b

Source: https://github.com/jredeker/opencode-shell-strategy/blob/trunk/_autodocs/api-reference/shell_strategy.md

Forces overwrite without prompting.

```bash
cp -f a b
```

--------------------------------

### Prohibited patterns catalog (lines 45-54)

Source: https://github.com/jredeker/opencode-shell-strategy/blob/trunk/_autodocs/api-reference/test.sh.md

List of prohibited patterns that the script scans for in fenced shell blocks. These patterns are matched as literal substrings. The patterns include 'yes |', 'StrictHostKeyChecking=no', 'sudo -S', 'echo "password" | sudo', 'export', and profile file redirections.

```text
yes |
StrictHostKeyChecking=no
sudo -S
echo "password" | sudo
export
>> ~/.bashrc
>> ~/.profile
>> ~/.zshrc
```

--------------------------------

### Argument parsing: case statement for red|green|verify

Source: https://github.com/jredeker/opencode-shell-strategy/blob/trunk/_autodocs/api-reference/test.sh.md

Parses the single optional positional argument. Defaults to 'green'. Accepts 'red', 'green', or 'verify'; otherwise prints usage to stderr and exits 2. No flags are supported.

```sh
PHASE="${1:-green}"

case "$PHASE" in
  red|green|verify) ;;
  *) echo "Usage: $PROG [red|green|verify]" >&2; exit 2 ;;
esac
```

--------------------------------

### cp a b

Source: https://github.com/jredeker/opencode-shell-strategy/blob/trunk/_autodocs/api-reference/shell_strategy.md

Copies a to b, overwriting without prompting if b exists.

```bash
cp a b
```

--------------------------------

### Run privileged command with sudo -n

Source: https://github.com/jredeker/opencode-shell-strategy/blob/trunk/README.md

Run a privileged command only when it needs no password. If a password is required, sudo -n fails immediately; do not pipe passwords into sudo -S.

```bash
sudo -n systemctl status nginx
```

--------------------------------

### python non-interactive

Source: https://github.com/jredeker/opencode-shell-strategy/blob/trunk/shell_strategy.md

python is interactive; use python -c "code" for non-interactive execution.

```bash
python
```

```bash
python -c "code"
```

--------------------------------

### Required safe forms (Stage 5)

Source: https://github.com/jredeker/opencode-shell-strategy/blob/trunk/_autodocs/api-reference/test.sh.md

List of required safe forms that must appear in the concatenated shell blocks. These are checked via substring match using grep -F. Missing forms produce a failure message.

```text
BatchMode=yes
StrictHostKeyChecking=accept-new
sudo -n
npm init -y
```

--------------------------------

### mv a b

Source: https://github.com/jredeker/opencode-shell-strategy/blob/trunk/_autodocs/api-reference/shell_strategy.md

Moves a to b, overwriting without prompting if b exists.

```bash
mv a b
```

--------------------------------

### node -e "code"

Source: https://github.com/jredeker/opencode-shell-strategy/blob/trunk/_autodocs/api-reference/shell_strategy.md

Runs Node.js code non-interactively.

```bash
node -e "code"
```

--------------------------------

### Fail-fast non-interactive mode: sudo -n and ssh BatchMode

Source: https://github.com/jredeker/opencode-shell-strategy/blob/trunk/shell_strategy.md

Use these commands when the requested action requires credentials or a user choice and the tool has a non-interactive mode that fails visibly. The sudo -n flag fails if a password is required, and the ssh options disable interactive prompts and set a connection timeout.

```bash
sudo -n command
ssh -o BatchMode=yes -o StrictHostKeyChecking=accept-new -o ConnectTimeout=10 user@host
```

--------------------------------

### python -c "code"

Source: https://github.com/jredeker/opencode-shell-strategy/blob/trunk/_autodocs/api-reference/shell_strategy.md

Runs Python code non-interactively.

```bash
python -c "code"
```

--------------------------------

### rm file operations

Source: https://github.com/jredeker/opencode-shell-strategy/blob/trunk/shell_strategy.md

rm file does not prompt by default. rm -i prompts; rm -f suppresses errors and never prompts. Verify the target before running destructive commands.

```bash
rm file
```

```bash
rm -i file
```

```bash
rm -f file
```

--------------------------------

### git --no-pager log

Source: https://github.com/jredeker/opencode-shell-strategy/blob/trunk/_autodocs/api-reference/shell_strategy.md

Shows git log without pager.

```bash
git --no-pager log
```

--------------------------------

### Disable git HTTP prompts with GIT_TERMINAL_PROMPT=0

Source: https://github.com/jredeker/opencode-shell-strategy/blob/trunk/shell_strategy.md

Sets GIT_TERMINAL_PROMPT to 0 for a single git clone command to disable HTTP password prompts. Use when the tool does not provide a dedicated flag; do not set globally as an anti-hang technique.

```bash
GIT_TERMINAL_PROMPT=0 git clone https://github.com/example/repo.git
```

--------------------------------

### git rebase non-interactive

Source: https://github.com/jredeker/opencode-shell-strategy/blob/trunk/shell_strategy.md

git rebase -i is interactive; use plain git rebase for non-interactive operation.

```bash
git rebase -i
```

```bash
git rebase
```

--------------------------------

### rm -f file

Source: https://github.com/jredeker/opencode-shell-strategy/blob/trunk/_autodocs/api-reference/shell_strategy.md

Suppresses errors and never prompts. Verify target before running destructive commands.

```bash
rm -f file
```

--------------------------------

### Final report and exit code logic (lines 145-160)

Source: https://github.com/jredeker/opencode-shell-strategy/blob/trunk/_autodocs/api-reference/test.sh.md

Shell script that computes the final exit code based on the number of failures and the PHASE variable. If failures are zero, it prints PASS and exits 0 (or 1 if PHASE is 'red' and no failures found). If failures exist, it prints FAIL and exits 1 (or 0 if PHASE is 'red' and failures found).

```sh
if [ "$failures" -eq 0 ]; then
  echo "PASS: 0 failures"
  if [ "$PHASE" = "red" ]; then
    echo "RED phase: expected failures but none found"
    exit 1
  fi
  exit 0
fi

echo "FAIL: $failures failures"
if [ "$PHASE" = "red" ]; then
  echo "RED phase: expected failures found"
  exit 0
fi
exit 1
```

--------------------------------

### git --no-pager diff

Source: https://github.com/jredeker/opencode-shell-strategy/blob/trunk/_autodocs/api-reference/shell_strategy.md

Shows git diff without pager.

```bash
git --no-pager diff
```

--------------------------------

### git pull --no-edit

Source: https://github.com/jredeker/opencode-shell-strategy/blob/trunk/_autodocs/api-reference/shell_strategy.md

Pulls without opening an editor for the merge message.

```bash
git pull --no-edit
```

--------------------------------

### git commit -m

Source: https://github.com/jredeker/opencode-shell-strategy/blob/trunk/_autodocs/api-reference/shell_strategy.md

Commits with an inline message to avoid opening an editor.

```bash
git commit -m "msg"
```

--------------------------------

### git log without pager

Source: https://github.com/jredeker/opencode-shell-strategy/blob/trunk/shell_strategy.md

git log uses a pager; use git --no-pager log to avoid less in non-interactive environments.

```bash
git log
```

```bash
git --no-pager log
```

--------------------------------

### git diff without pager

Source: https://github.com/jredeker/opencode-shell-strategy/blob/trunk/shell_strategy.md

git diff uses a pager; use git --no-pager diff to avoid less in non-interactive environments.

```bash
git diff
```

```bash
git --no-pager diff
```

--------------------------------

### git merge --no-edit

Source: https://github.com/jredeker/opencode-shell-strategy/blob/trunk/_autodocs/api-reference/shell_strategy.md

Merges a branch without opening an editor for the merge message.

```bash
git merge --no-edit branch
```

--------------------------------

### git commit non-interactive

Source: https://github.com/jredeker/opencode-shell-strategy/blob/trunk/shell_strategy.md

git commit without -m may invoke an editor; use -m to supply a message directly.

```bash
git commit
```

```bash
git commit -m "msg"
```

--------------------------------

### git pull non-interactive

Source: https://github.com/jredeker/opencode-shell-strategy/blob/trunk/shell_strategy.md

git pull may invoke an editor when a merge message must be edited; use --no-edit to keep the generated message.

```bash
git pull
```

```bash
git pull --no-edit
```

--------------------------------

### git merge non-interactive

Source: https://github.com/jredeker/opencode-shell-strategy/blob/trunk/shell_strategy.md

git merge may invoke an editor when a merge message must be edited; use --no-edit to keep the generated message.

```bash
git merge branch
```

```bash
git merge --no-edit branch
```
Tokens:
Raw