Adversarial code review that tries to disprove a change is safe. Produces counterexamples, not vibes. Use when the user wants adversarial, hostile, or red-team review, or asks you to break, attack, disprove, or exploit the change.
Run an explicitly requested PR-to-deployment loop: publish a PR, reach Greptile 5/5, merge, and verify deployment. Use only when the user asks for the full lifecycle.
Effect v4 logging and observability for APIs and backends. Use for structured logs and logger layers; typed error and Cause boundaries; request context and log spans; or distributed tracing integration.
Behavior-preserving cleanup of a working-tree or explicit base/head diff. Use after implementation or when asked to simplify current or committed changes.
Create, restyle, or present reviewed standalone HTML technical reports in a cohesive editorial system. Use for new reports, visual restyles, or corrected copies with tracked changes; report-producing skills may invoke it for standalone HTML presentation.
TypeScript structure through narrow domain modules and explicit dependency graphs. Use when designing or refactoring module boundaries, public APIs, domain types, imports, or Effect service architecture.