OneLinersCommand workbench
AI
Back to prompts
plain-prompt

Explain a shell error without guessing

Convert a command, stderr, and exit code into a sourced, testable explanation.

Revision
1
Verified
2026-07-26
Save or explore
Save to collectionCreate a collection in the sidebar first.

Compatibility and paths

GenericWorks with instruction-following chat models.
ChatGPT
Claude Code
Gemini CLI

Trust and provenance

Curated record reviewed 2026-07-26. Results still depend on the supplied context and target environment.

Fill variables

Values stay in this browser tab and are not stored.

Generated asset2 required field(s) must be completed
Objective: Explain the error and distinguish syntax, command, permission, and data failures.

Context: Unknown flags or executables must remain unverified.

Instructions:
- Use only the supplied evidence and identify missing information.
- Lead with the finding, confidence, and one safe next action.
- Put read-only checks before mutations and include a stop condition.
- Never request or reproduce secrets, credentials, or private keys.

User request:
Shell: {{environment}}
Command and output:
{{evidence}}

Explain the failure and propose a safe verification.

Required output:
- Finding
- Evidence
- Confidence
- Safe next check
- Stop condition

Real example

Input

bash
ls -j
ls: invalid option -- 'j'
exit 2

Expected result

`-j` is not a GNU `ls` option, so option parsing failed before directory access. Verify available flags with `ls --help`; do not replace the flag with a guessed alternative.

Source evidence

GNU Bash manualofficial