23 lines
765 B
Markdown
23 lines
765 B
Markdown
# Shared rules
|
|
|
|
## Process
|
|
|
|
0. Before editing, work on a feature branch. Never work directly on master.
|
|
1. Write and commit a failing test before changing module behavior.
|
|
2. Implement the behavior and confirm the test passes.
|
|
3. Run `nix fmt` and `nix flake check` before committing implementation.
|
|
4. Do not push anything.
|
|
|
|
## Code style
|
|
|
|
- Keep lines at or below 80 columns when practical.
|
|
- Use explicit, descriptive names.
|
|
- Explore existing patterns before editing.
|
|
- Never use em dashes in code, comments, or documentation.
|
|
|
|
## Git commits
|
|
|
|
- Use present-tense, imperative, lowercase subjects of three to six words.
|
|
- Keep commits focused and add a wrapped body only when needed.
|
|
- Do not add AI coauthor metadata.
|
|
- Use descriptive kebab-case branch names.
|