Best-Practice Library
220 reviewable checks across 15 languages, bundled into 32 ready-to-run policies.
Policies
A policy is a curated bundle of checks. Start with a baseline policy for a low-noise rollout, move up to a full language policy when you want broader coverage, then layer an architecture doctrine on top when your repo commits to one. Language policies include a foundation policy for shared cross-language concerns.
Baseline policies
High-signal starter policies for low-noise onboarding. Each baseline language policy includes the baseline foundation.
Cross-language foundation · 19 checks
20 checks · includes baseline-shared-foundation
20 checks · includes baseline-shared-foundation
20 checks · includes baseline-shared-foundation
20 checks · includes baseline-shared-foundation
20 checks · includes baseline-shared-foundation
20 checks · includes baseline-shared-foundation
20 checks · includes baseline-shared-foundation
20 checks · includes baseline-shared-foundation
20 checks · includes baseline-shared-foundation
20 checks · includes baseline-shared-foundation
20 checks · includes baseline-shared-foundation
20 checks · includes baseline-shared-foundation
20 checks · includes baseline-shared-foundation
20 checks · includes baseline-shared-foundation
Full language policies
Broader coverage for repositories with substantial code in a language. Each full language policy includes the shared foundation.
Cross-language foundation · 63 checks
82 checks · includes shared-foundation
69 checks · includes shared-foundation
77 checks · includes shared-foundation
71 checks · includes shared-foundation
71 checks · includes shared-foundation
65 checks · includes shared-foundation
66 checks · includes shared-foundation
71 checks · includes shared-foundation
79 checks · includes shared-foundation
72 checks · includes shared-foundation
66 checks · includes shared-foundation
71 checks · includes shared-foundation
66 checks · includes shared-foundation
69 checks · includes shared-foundation
Architecture doctrines
Opt-in overlays for a specific architecture. Enable one on top of your language policy when your repo commits to that doctrine.
Browse by domain
Boundary validation, error contracts, compatibility and idempotent mutations.
Timeouts, retries, idempotency, resource lifecycles and graceful failure.
Boundaries, dependency direction, encapsulation and explicit entrypoints.
Health signals, safe automation, telemetry and production defaults.
Deterministic, isolated tests that assert outcomes through supported interfaces.
Hot-path data access, quadratic work, async blocking and latency signals.
Atomic mutations, schema evolution, provenance and validated upstream data.
Input validation, authn/z, injection, secrets and safe data handling.
Public APIs, behavior changes and release notes stay documented.