no-temp-scripts

To keep artifacts in-repo, enforce strict workspace storage policies that prohibit writing to /tmp or /var/tmp. This ensures all scripts and intermediate files remain inside the repository for full traceability, diffing, and reproducibility.

Agent workflows create hidden scratch files outside the repository when in-repo storage enforcement is absent. Prohibiting external temp file creation and directing all artifacts to the workspace improves visibility and aligns with organizational dev-standards.

The best way to enforce in-repo storage for code generation and build hooks is to strictly prohibit external temp file creation. Directing all artifacts to the repository ensures visibility, auditability, and reproducibility across development tasks.

Prohibiting temp files improves code review and reproducibility by ensuring all data processing artifacts stay inside the repository. This allows users to easily read, diff, and review intermediate files instead of losing them in system temp directories.

Avoid using system temp directories like /tmp whenever you need strict traceability and alignment with dev-standards. Storing intermediate scripts in the workspace instead ensures visibility during code review and prevents accidental loss of hidden scratch files.