shreyT19
- 3 skills
- 0 followers
- 21 hours ago last updated
- ▌ Pr Brief · shreyt19Reviewer-oriented brief of an incoming PR. Fetches PR metadata + diff, invokes interrogate (what the code does) and blast-radius (downstream impact), optionally why (historical rationale for legacy touched code), then composes a plain-English brief with TL;DR, what-changes, why-needed, downstream impact, and watch-points for review. Use BEFORE reviewing when a teammate sends a PR and you need to understand it. Handoff to `quick-review` / `medium-review` / `advanced-review` after for judgment.
- ▌ Quick Review · shreyt19Fast plain-English sanity check of a git diff. Read every hunk, spot only obvious breakage (broken imports, dangling refs, signature mismatches, syntax), summarize what changed and why in ~30 seconds. Does NOT run tests, hunt smells, or pull spec. Use when user asks for "quick review", "glance at this", "does this look ok", or a fast diff explanation before committing or requesting deeper review. For thorough review, use `medium-review` or `code-review` (advanced) instead.
- ▌ Medium Review · shreyt19Middle-tier code review. Orchestrates blast-radius (impact scoping) + interrogate (deep-read touched files) + own judgment pass, then formats output using principle-minimize-reader-load style. Use when user asks for a "medium review", "proper review", or wants more than quick-review but less than the full two-axis code-review. Takes ~2 min. For fast sanity check use `quick-review`; for exhaustive two-axis review use `code-review`.