|
| 1 | +agents: |
| 2 | + - name: devrail |
| 3 | + description: DevRail development standards |
| 4 | + instructions: | |
| 5 | + This project follows DevRail development standards. |
| 6 | + See DEVELOPMENT.md for the complete reference. |
| 7 | +
|
| 8 | + Critical Rules: |
| 9 | +
|
| 10 | + 1. Run `make check` before completing any story or task. Never mark work |
| 11 | + done without passing checks. This is the single gate for all linting, |
| 12 | + formatting, security, and test validation. |
| 13 | + 2. Use conventional commits. Every commit message follows the |
| 14 | + `type(scope): description` format. No exceptions. |
| 15 | + 3. Never install tools outside the container. All linters, formatters, |
| 16 | + scanners, and test runners live inside |
| 17 | + `ghcr.io/devrail-dev/dev-toolchain:v1`. The Makefile delegates to |
| 18 | + Docker. Do not install tools on the host. |
| 19 | + 4. Respect `.editorconfig`. Never override formatting rules (indent style, |
| 20 | + line endings, trailing whitespace) without explicit instruction. |
| 21 | + 5. Write idempotent scripts. Every script must be safe to re-run. Check |
| 22 | + before acting: `command -v tool || install_tool`, `mkdir -p`, guard |
| 23 | + file writes with existence checks. |
| 24 | + 6. Use the shared logging library. No raw `echo` for status messages. Use |
| 25 | + `log_info`, `log_warn`, `log_error`, `log_debug`, and `die` from |
| 26 | + `lib/log.sh`. |
| 27 | +
|
| 28 | + Quick Reference: |
| 29 | +
|
| 30 | + - Run `make check` to validate all standards |
| 31 | + - Run `make help` to see available targets |
| 32 | + - Run `make build` to build the Hugo site |
| 33 | + - Run `make serve` to start the local development server |
| 34 | + - All tools run inside the dev-toolchain container |
0 commit comments