Files
computer-playbook/docs/contributing/design/languages/shell.md
Environment TestandClaude Sonnet 4.6 83262816a3 docs(contributing): apply documentation.md rules across all staged files
- Move emojis after headline text (CONTRIBUTING.md, actions/, design/, tools/, tests/)
- Replace em dashes with colons, semicolons, or complete sentences throughout
- Add missing emojis to all headlines in exceptions.md, principles.md, services.md, shell.md, setup.md, pull-request.md, commit.md, act.md, docker.md, pr/README.md
- Update H1 titles to reflect renamed directories (actions/, design/)
- Fix broken relative links in workflow.md after directory moves
- Fix full-path link texts in services.md (style.css.md, javascript.js.md)
- Fix broken principles.md link to lint.md after testing/ → actions/testing/ move

Co-Authored-By: Claude Sonnet 4.6 <noreply@anthropic.com>
2026-04-10 21:06:17 +02:00

21 lines
897 B
Markdown

# Shell 🐚
Use this page for shell-script-specific guidance.
## Script Layout 📁
- You MUST store general `.sh` scripts for infinito.nexus administration under `scripts/`.
- You MUST keep shell entrypoints in `scripts/` so they stay easy to discover and reuse.
- You MUST keep role-local or component-specific shell helpers in their owning area, such as `roles/.../files/`, when they belong to a single role.
## Executable Bit 🔑
- You MUST set the executable bit on shell scripts that are meant to run directly.
- You MUST use `chmod +x` for those scripts so they can be invoked as executables.
- You MUST keep a shebang at the top of executable shell scripts.
## Notes 📝
- `scripts/tests/deploy/local/exec/container.sh` is a direct-entry shell script example.
- For shell entrypoints that are exposed through `make`, you SHOULD prefer a thin target that delegates to the script.