LLM Integration Code Review Patterns

Stack-specific rules loaded by dh:code-reviewer when prompt files, model selection logic, or evaluation harness code are detected.

Prompt Hygiene

System prompt must be separated from user content — mixing them in a single string removes the security boundary
System prompts must not include user-controlled content unless that content is explicitly sanitized and bounded
Prompt templates must use structured variable substitution, not string concatenation — f-strings with raw user input are a blocking finding
Long prompts should be stored in dedicated files, not inline strings — inline multi-line strings are acceptable only below 10 lines

Model tier must match task complexity — using Opus for tasks that Haiku can handle is a blocking finding (cost regression)
Using Haiku for tasks requiring multi-step reasoning, architecture decisions, or complex judgment is a blocking finding (quality regression)
Model selection must be documented with the rationale — model = "haiku" # retrieval only, no reasoning required
Model names must not be hardcoded as full version strings — use the tier alias (sonnet, haiku, opus) so upgrades require one change