standards

# Standards — focused engineering guidance Load the smallest set of standards justified by the caller's files, language, and risks. Do not preload the entire reference corpus. ## Prompt ```text Check standards for the changed files in fleet-router PR #214: cli/internal/auth/token.go and cli/internal/auth/token_test.go, Go, a security-sensitive change. Load only the matching references and report cited findings with path and line plus checked and not-checked scope. ``` ## It's working if - The report loads `common-standards.md` plus only the matching Go reference, never the full reference corpus. - Every finding cites a path and line, e.g. `cli/internal/auth/token.go:18`. - The response discloses `checked` and `not_checked` scope explicitly, even when `not_checked` is empty. - `git diff --stat` shows no test, gate, or fixture file changed; standards reports findings only. ## Procedure 1. Record the supplied paths, language, change type, and risk cues. 2. Load `common-standards.md` plus only the matching language or checklist references. 3. Compare the supplied artifact to those sources. 4. Return cited findings with path and line when possible, plus checked and not-checked scope. 5. Stop. This skill provides context and findings. It does not edit, validate, retry, approve, commit, release, deliver, or decide continuation. ## Load-bearing conventions for produced code (MEASURED) When the caller is about to WRITE code (not only review it), surface the matching la...