warden

Use when keeping a member private when a test wants to call it directly; testing a class whose helper is private/protected/internal and the test cannot reach it; deciding how to test logic that currently lives behind a `private`/`protected` modifier; reviewing a diff that widens an access modifier with a justification referencing tests.

Use when handling an error you do not know how to recover from in the current scope; writing a `catch` / `except` / `.catch()` block that does nothing or only logs; reviewing a diff that adds a try/catch around new code without rethrow or remediation; deciding what to do with a Promise/Task whose failure path has no obvious owner.

Use when adding a null/range/format check inside an internal helper that already receives a typed argument; deciding where to validate input that crosses a trust boundary (HTTP handler, CLI args, queue message, deserializer); reviewing a diff that scatters defensive guards through the call graph below the entry point; writing parsing/coercion logic that turns external data into a domain type.

Use when writing a test that verifies a mock was called instead of the effect the call produced; reaching for a spy/stub/inspector to peek at internal state from a test; reviewing a test that breaks every time the production code is refactored; deciding what to assert about a function whose contract is "given X, the world looks like Y".

Use when writing a comment that paraphrases the line of code immediately below it; adding a docstring to a function whose name and signature already say everything; reviewing a diff that adds explanatory comments to make obvious code "easier to read"; deciding whether a non-obvious decision (workaround, constraint, invariant) needs a comment.

1 hook across 1 event