# Themes

This page captures practical ways teams tune review behavior and interpretation standards.

## What to Tune First [Permalink for this section](/content/livereview/git-lrc/docs/customize/themes/#what-to-tune-first/index.html)

1. Severity interpretation policy
2. Sensitive pattern policy (credentials, secrets, PII)
3. Cost-risk policy (cloud-heavy operations)
4. Critical-path policy (auth, billing, migrations)

## Lightweight Team Policy Template [Permalink for this section](/content/livereview/git-lrc/docs/customize/themes/#lightweight-team-policy-template/index.html)

Use this as a baseline in your internal docs:

```
Critical areas: auth, payments, access control, migrations
Always-review changes: permission checks, input validation, logging statements
Escalate when: behavior changes without explicit intent notes
Block until fixed: credential leakage, sensitive data logging
```

## Practical Review Cadence [Permalink for this section](/content/livereview/git-lrc/docs/customize/themes/#practical-review-cadence/index.html)

- Small diffs: 1 to 2 iterations
- Medium diffs: 2 to 4 iterations
- Large diffs: split before final vouch when possible

## Why This Matters [Permalink for this section](/content/livereview/git-lrc/docs/customize/themes/#why-this-matters/index.html)

Launch feedback repeatedly highlighted confidence and consistency concerns. A lightweight policy makes review output actionable and less subjective.