Unsummarizable
>-
Complexity
>-
Meaningful Contribution
Require software changes to be demonstrated, not merely generated. Use when implementing, fixing, refactoring, reviewing, or preparing a pull request for code, configuration, migrations, build tooling, or other behavior-affecting repository changes—especially agent-generated changes that need manual verification, automated regression coverage, edge-case testing, honest naming and types, and conci…
Office Hours
>-
Plan Ceo Review
>-
Gr
Run a complete Greptile CLI review, merge, and production deployment loop for the current pull request: inspect findings, fix every actionable issue, verify changes, re-review until clean, push, wait for every check, merge only when none are failed or pending, deploy through the repository's documented production path, and verify production. Use when the user invokes /gr or asks to run Greptile,…