Precedent

Match work to what the project already does. The precedent is the pattern the surrounding files establish, not a style guide and not your priors, so a finding without a cited sibling is an invention. An explicit convention outranks emergent precedent, so defer wherever one answers the question: conventions-go, conventions-markdown, conventions-mermaid, conventions-python, conventions-sql, and the project's GLOSSARY.md for domain terms. If only a legacy CONTEXT.md exists, use it and warn with ⚠️ to rename it to GLOSSARY.md. This skill owns what no guide writes down: the patterns a codebase grew.

Scope. A file path or glob audits those files. --uncommitted, or "what I'm working on", audits the files from git status --porcelain. With no argument, ask which path to check.