32:I[902115,["/_next/static/immutable/chunks/26xcb9yuv4-q9.js","/_next/static/immutable/chunks/1iv8g77zll1c3.js","/_next/static/immutable/chunks/05ibr6udxyg_a.js"],"InstallCommand"] 33:I[434085,["/_next/static/immutable/chunks/26xcb9yuv4-q9.js","/_next/static/immutable/chunks/1iv8g77zll1c3.js","/_next/static/immutable/chunks/05ibr6udxyg_a.js"],"CollapsibleReadme"] 34:T548,

Ask whether you are familiar with the exact command form you are about to run, not only the base command name.
Treat it as familiar only if you can explain:
- what it will do
- what target, path, or object it will touch
- what the important flags or subcommands change
Run it directly if you can answer those questions clearly.
Check help first if you cannot.
Use this order:
- <cmd> --help
- <cmd> <subcommand> --help
- the tool's built-in help form
- man <cmd>
- type <cmd> or command -v <cmd> when the help path is unclear; if it is a shell builtin, use shell help

Do not use a hard whitelist. Judge familiarity on the exact command you are about to run.

Examples

Run directly when familiar: pwd, ls src, git status
Check first when unfamiliar: find ... -exec ..., git rebase --rebase-merges, docker run ... --filter ...
Resolve builtins explicitly: if unsure about cd or export, run type cd and then help cd

help-me

Help Me

Overview

Decision Tree