Menu
Diagnose and fix an error from a build failure, stack trace, or error message
Install with Codex or Claude Copy this prompt, paste it into Codex, Claude, or another assistant, and let it review the skill page and install it for you.
Based on SOC occupation classification
Quick review of the current diff for bugs, logic errors, convention violations, and test gaps
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
| name | fix |
| description | Diagnose and fix an error from a build failure, stack trace, or error message |
| disable-model-invocation | true |
| argument-hint | <error message, stack trace, or description> |
Diagnose and fix the provided error. This could be a build error, runtime crash, test failure, or a description of unexpected behavior.
Input: $ARGUMENTS
Analyze the input to determine:
If the input is a description rather than an error output, search the codebase for the relevant code.
Read the file(s) referenced in the error. If no file is referenced:
git diff main) that may have introduced the issueRead enough surrounding context to understand the code's intent — not just the failing line.
Identify the root cause. Common categories:
@AssistedInject / @AssistedFactory wiring@ContributesBinding or @ContributesIntoSetwaitForIdle, incorrect matchers)when blockApply the minimal fix that resolves the root cause. Do not refactor surrounding code or make unrelated improvements.
If the fix requires changes across multiple files (e.g., a renamed interface), update all affected files.
After applying the fix:
./gradlew :<module>:compileDebugKotlin to verify it compilesReport what was wrong and what was changed.