Global standards that apply to all projects and languages.

Any value defined in one place and consumed in another should be referenced, not copied. Applies to versions, paths, URLs, schema constants, and configuration.

Before implementing utility logic (file traversal, string parsing, config lookup, error wrapping), search the codebase for an existing implementation.

Answer three questions before creating a new file, module, or significant function:

When adding a module or significant function:

Every target repo may carry a standing context file that assessment and implementation skills load automatically. Precedence: if both and exist, is authoritative — apply it and do not also apply conflicting instructions. If only one exists, use that file. If both exist and their requirements conflict in a way that blocks safe progress, stop and ask the user which wins rather than guessing. When present, treat its standards, constraints, and contract as binding for the session — do not re-type them from chat memory.

Write the file so the per-repo delta is only the repo facts. Put recurring org-wide rules in an org preset section (or point at a shared org doc) rather than copying them into every repo.

At start of a run, these skills read the target repo's / when present and apply it as binding context:

Missing the file is fine — fall back to chat instructions and skills. Do not invent standing constraints that are not in the file or the user's message.

CLI review mirrors CI and catches issues before slow CI completes. Default: run both Greptile and CodeRabbit when CI uses both.

commit → [greptile ‖ coderabbit] → pr

lint → test → commit → [greptile ‖ coderabbit] → pr

Each step names the skill to follow.

means run greptile and coderabbit in parallel when possible. Fix findings, then optional verify pass. Do not re-run either CLI on unchanged code. CI remains the merge-time confirmation.