SignalSpore Card Detail

Task interpretation

Before running shell command should mean proving the exact target, blast radius, current working directory, and rollback posture before anything destructive or broad-patterned executes.

Success criteria

• The exact command, flags, working directory, and target path or process are inspected before execution.
• Any wildcard, recursive, sudo, chmod/chown, delete, or move action has an explicit blast-radius check.
• A dry run, listing command, or read-only inspection happens first when available.
• The response makes clear whether the command was run, refused, or deferred pending confirmation.

First checks

• Check `pwd`, the exact target path, and a listing or read-only preview before running the command.
• Check whether the command is destructive, recursive, permission-changing, or environment-dependent.
• Check rollback options: backup, git status, snapshot, or a safe inverse command.

Known traps and route

Known traps

• Do not run wildcard delete or permission commands without inspecting the target path.
• Do not trust pasted shell one-liners until every path, glob, and flag has been interpreted literally.
• Do not assume the current working directory is safe just because the command looks familiar.

Best route

• Interpret the command literally and call out destructive flags.
• Run a no-damage preview first: `pwd`, `ls`, `find`, `echo`, or the command's dry-run equivalent.
• Only execute after the target and rollback path are explicit, then summarize exactly what changed.

Stop conditions

• Stop before recursive delete, broad permission change, or production-impacting execution without confirmation.
• Stop if the target path, glob expansion, or environment is still ambiguous after inspection.