Add file first guidance for CLI and LLM inputs
Capture the repository preference that shell facing tools should consume files when they support them instead of large inline strings. Add explicit guidance for prompt files, temporary files, and git commit message files so future automation avoids quoting bugs and stays aligned with the vm run harness and commit workflows.
This commit is contained in:
parent
88e633c6c4
commit
671723a0ef
1 changed files with 4 additions and 0 deletions
|
|
@ -35,6 +35,10 @@
|
|||
- Prefer small, direct Go code and standard library solutions.
|
||||
- Keep shell scripts strict with `set -euo pipefail`.
|
||||
- Use `gofmt` for Go formatting.
|
||||
- When a CLI accepts either an inline string or a file input, always prefer the file-based form.
|
||||
- For shell commands and AI/LLM tooling, prefer passing files as input whenever the CLI allows it.
|
||||
- Create temporary files as needed to follow the file-first rule.
|
||||
- Examples: use `git commit -F <file>` instead of `git commit -m <message>`, and use prompt files instead of inline prompt strings when invoking LLM CLIs.
|
||||
|
||||
## Testing Guidance
|
||||
|
||||
|
|
|
|||
Loading…
Add table
Add a link
Reference in a new issue