Skip to content

Add critical rule 9: ensure DevRail Makefile is active #7

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Merged
matthew-on-git merged 1 commit into from
Mar 19, 2026
Merged

Add critical rule 9: ensure DevRail Makefile is active #7

Show file tree
Hide file tree
Changes from all commits
Commits
Show all changes
1 commit
Select commit
File filter

Filter by extension

Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
5 changes: 5 additions & 0 deletions .cursorrules
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -28,6 +28,11 @@ Critical Rules:
the relevant documentation (README, DEVELOPMENT.md, inline docs) in
the same commit or PR. Do not leave documentation out of sync with
code.
9. Ensure the DevRail Makefile is active. GNU Make prefers GNUmakefile
over makefile over Makefile. If the project has a GNUmakefile or
makefile, the DevRail Makefile will be silently ignored. Merge
project-specific targets into the DevRail Makefile, or add
`include Makefile` to the existing GNUmakefile.

Quick Reference:

Expand Down
5 changes: 5 additions & 0 deletions .opencode/agents.yaml
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -33,6 +33,11 @@ agents:
the relevant documentation (README, DEVELOPMENT.md, inline docs) in
the same commit or PR. Do not leave documentation out of sync with
code.
9. Ensure the DevRail Makefile is active. GNU Make prefers GNUmakefile
over makefile over Makefile. If the project has a GNUmakefile or
makefile, the DevRail Makefile will be silently ignored. Merge
project-specific targets into the DevRail Makefile, or add
`include Makefile` to the existing GNUmakefile.

Quick Reference:

Expand Down
1 change: 1 addition & 0 deletions AGENTS.md
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -13,6 +13,7 @@ See DEVELOPMENT.md for the complete reference.
6. **Use the shared logging library.** No raw `echo` for status messages. Use `log_info`, `log_warn`, `log_error`, `log_debug`, and `die` from `lib/log.sh`.
7. **Never suppress failing checks.** When a lint, format, security, or test check fails, fix the underlying issue. Never comment out code, add suppression annotations, disable rules, or mark CI jobs as allowed-to-fail to bypass a failing check.
8. **Update documentation when changing behavior.** When a change affects public interfaces, configuration, CLI usage, or setup steps, update the relevant documentation (README, DEVELOPMENT.md, inline docs) in the same commit or PR. Do not leave documentation out of sync with code.
9. **Ensure the DevRail `Makefile` is active.** GNU Make prefers `GNUmakefile` over `makefile` over `Makefile`. If the project has a `GNUmakefile` or `makefile`, the DevRail `Makefile` will be silently ignored. Merge project-specific targets into the DevRail `Makefile`, or add `include Makefile` to the existing `GNUmakefile`.

## Quick Reference

Expand Down
1 change: 1 addition & 0 deletions CLAUDE.md
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -13,6 +13,7 @@ See DEVELOPMENT.md for the complete reference.
6. **Use the shared logging library.** No raw `echo` for status messages. Use `log_info`, `log_warn`, `log_error`, `log_debug`, and `die` from `lib/log.sh`.
7. **Never suppress failing checks.** When a lint, format, security, or test check fails, fix the underlying issue. Never comment out code, add suppression annotations, disable rules, or mark CI jobs as allowed-to-fail to bypass a failing check.
8. **Update documentation when changing behavior.** When a change affects public interfaces, configuration, CLI usage, or setup steps, update the relevant documentation (README, DEVELOPMENT.md, inline docs) in the same commit or PR. Do not leave documentation out of sync with code.
9. **Ensure the DevRail `Makefile` is active.** GNU Make prefers `GNUmakefile` over `makefile` over `Makefile`. If the project has a `GNUmakefile` or `makefile`, the DevRail `Makefile` will be silently ignored. Merge project-specific targets into the DevRail `Makefile`, or add `include Makefile` to the existing `GNUmakefile`.

## Quick Reference

Expand Down
Loading