Menu
Quick review of the current diff for bugs, logic errors, convention violations, and test gaps
Instalar com Codex ou Claude Copie este prompt, cole no Codex, Claude ou outro assistente e deixe que ele revise a página da skill e instale para você.
Baseado na classificação ocupacional SOC
Scaffold a new feature module with the appropriate layers and MESA conventions
Scaffold a new Strata interactor with interface, implementation, fake, and test
Add a new screen to an existing feature module with StateHolder, UI, factories, and tests
Add missing test cases, targeting a specific file or all changed files on the branch
Bump library versions in gradle.properties and prepare release notes
Diagnose and fix an error from a build failure, stack trace, or error message
| name | review |
| description | Quick review of the current diff for bugs, logic errors, convention violations, and test gaps |
| disable-model-invocation | true |
| argument-hint | [--staged | --uncommitted] |
Quick feedback on the current diff. Focus on catching bugs, logic errors, and convention violations. Keep output concise — this is a development pulse check, not a pre-merge audit.
Scope: $ARGUMENTS
Determine which diff to review:
--staged → git diff --cached (only staged changes)--uncommitted → git diff HEAD (only uncommitted changes)git diff main (all changes on the branch vs main, committed and uncommitted)Also run git status to identify new untracked files included in the changes.
Read the diff output AND the full content of each changed file so you can assess whether the changed code is correct in context.
Read each changed file and look for actual problems. Do NOT present an exhaustive checklist — only report issues you find. Look for:
!!, missing null checks)when branches for sealed interfacesremember / rememberSaveable usageIf no issues are found, say so briefly.
Verify MESA conventions are followed. Present as a concise pass/fail list — only include items relevant to the changed code:
TrapezeStateHolderLazy<T>wrapEventSink()@AssistedInject with factory pattern for StateHoldersStrataResultStrataSubjectInteractor triggered in UI/Logic layer, not initstrataLaunch used for coroutine workapi/ clean, presentation/ doesn't touch data/)Skip items that don't apply to the changed files.
For each changed or new source file, briefly note missing or incomplete test coverage. Keep it to one or two lines per gap — just identify what's missing:
FooStateHolder")Delete event not tested in BarStateHolderTest")Only report gaps. Do NOT list what IS covered or confirm adequate coverage. If there are no gaps, just say "No test gaps found." — do not enumerate the tests that exist.
Do not suggest running other skills or provide detailed instructions on how to write the tests.
Keep the report compact:
One or two sentences on what changed and overall quality.
List problems found in Step 2, grouped by severity:
If none, say "No issues found."
Show the pass/fail list from Step 3. Omit items marked N/A.
List only gaps from Step 4. Do not list what is already covered. If no gaps, say "No test gaps found."