Know that this file is intended for you, specifically. Within this document, you will discover: REPO RULES™, REQUIRED WORKFLOWS™, and PAST PERSPECTIVES™, to guide and inform you.
Abide by these rules and you shall take your place in the hall of heroes.
Warning
NEVER use --force with any git operation. Instead, HALT and alert the user that force must be used, explain why and how you got yourself into this situation. Ask them to run the command themselves.
Warning
Never rebase. Instead, just do a regular merge. Rebase often ends in a state of thrashing/confusion because of the way you git rebase it inevitably leaves you stuck at an interactive prompt, complaining that a git lock file was not released properly. To avoid this mess, merge and commit after resolving conflicts. Rebase also often requires a force push, which is FORBIDDEN.
Warning
Just make a new commit. Amend often requires force pushing, which is FORBIDDEN.
Important
Keeping our code extremely high quality is crucial. You MUST NOT use NOLINT to avoid clang-tidy warnings/errors. Fix the root cause.
Important
Never use --no-verify when making git commits or pushes. If you're tempted, HALT and alert the user, instead. It is FORBIDDEN for you to use this option. You must require the user do it for themselves.
Important
We all have but one context. Don't leave a mess behind for future agents to deal with. Stop robbing them of their context's potential. Ask yourself: if not me, then who? See a mess? Clean it up.
Note: The following voice is fictionalised satire for style guidance. The canonical rules live in docs/guides/C_STYLE_GUIDE.md.
See docs/guides/C_STYLE_GUIDE.md for the full letter and STRICTNESS_GOD_TIER doctrine.
The root .clang-tidy configuration is authoritative. See the full settings in docs/guides/C_STYLE_GUIDE.md.
Follow the tidy → integrate → tidy loop described in docs/guides/WORKFLOW.md. That document preserves the Ten Tubular Waves playbook and the virtues/warnings table.
The following logs are debriefs, left behind by those who walked the repo before your time–agents who, at the end of their contexts, used their last breathes to ensure that this information would be passed on, to you. Mad respect. Read these and understand what your ancestors worked on.
Log each session debrief to DEBRIEF.json, using one JSON object per line (JSON Lines format).
- Review the schema in docs/guides/DEBRIEF_FORMAT.md.
- Always append a new line; never rewrite existing entries.
- Use UTC-8 (PST) timestamps unless the maintainer specifies otherwise.
Historical debriefs live in DEBRIEF.json; consult that file for prior context.