docs(agents): require Nushell or Python for shell glue

- limit POSIX shell to a single command with arguments
- route pipes, chaining, substitution, redirection, and ShellCheck/BashPitfalls cases to Nushell or Python
This commit is contained in:
Ryan Yin
2026-09-14 20:57:12 +08:00
parent 4d54df2008
commit 3412dfefec
+4 -5
View File
@@ -106,11 +106,10 @@ agents MUST ask which state to use before editing.
### Local ad-hoc commands
- Agents SHOULD prefer a direct executable with native options over hand-written glue, and keep
POSIX shell (e.g. Bash) to single-line ad-hoc glue only.
- Once a task needs anything ShellCheck or BashPitfalls warns about — e.g. quoting discipline, error
handling, structured parsing (JSON/CSV/regex), dates/floats, retries/timeouts, or cross-platform
flags — agents MUST move to Nushell or Python.
- Agents SHOULD prefer a direct executable with native options over hand-written glue.
- POSIX shell (e.g. Bash) is limited to invoking a single command with arguments. Any glue — pipes,
chaining (`;`, `&&`), substitution, or redirection — or anything ShellCheck or BashPitfalls warns
about MUST be done in Nushell or Python instead (e.g. `nu -c`, `python -c`).
- Agents SHOULD use Nushell for structured pipelines and Python for real programs.
### Project-owned scripts