القائمة
Thorough pre-merge audit — dependency graph, correctness, conventions, security, test coverage, and improvement suggestions
التثبيت باستخدام Codex أو Claude انسخ هذا Prompt والصقه في Codex أو Claude أو مساعد آخر ليراجع صفحة Skill ويثبّتها لك.
استنادا إلى تصنيف SOC المهني
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 | prepare-pr |
| description | Thorough pre-merge audit — dependency graph, correctness, conventions, security, test coverage, and improvement suggestions |
| disable-model-invocation | true |
| argument-hint |
Perform a thorough pre-merge audit of the current changes. Start from the diff, then follow the dependency graph to understand how the changes fit into the broader system. Check correctness, security, MESA conventions, test coverage, and suggest improvements.
Scope: $ARGUMENTS
Get all changes on the branch compared to main:
git diff main to capture all committed and uncommitted changes on the branchAlso run git status to identify new untracked files.
Read the diff output AND the full content of every changed file.
Starting from the changed files, trace connections to understand the full impact:
build.gradle.kts files for dependency declarations when module boundaries are relevantThe goal is to understand how the changes integrate with everything that touches them — not to review the entire codebase, but to verify nothing is broken or inconsistent at the boundaries.
Present findings with checkboxes as you go:
!!, missing null checks)when branches)remember and rememberSaveable used correctly in ComposablesrememberSaveable stateFor a deeper security audit, run /security-check.
Present findings with checkboxes as you go:
TrapezeStateHolder, not Android ViewModelsLazy<T>wrapEventSink() in StateHolderT preserved but screen instance never stored in StateHolder@AssistedInject with factory; screen args extracted in factory, not in StateHolderTrapezeNavigator used correctly; navigation results follow the popWithResult / rememberNavigationResult patternTrapezeMessageManager, not side channelsStrataResult, not raw exceptionsStrataSubjectInteractor triggered in UI/Logic layer (e.g., LaunchedEffect), not in initstrataLaunch used for coroutine work (defaults to Dispatchers.Default)StrataResult extensions used idiomatically (onSuccess, onFailure, fold, map, etc.)api/ modules have no internal dependenciespresentation/ depends on api/ and domain/, not data/domain/ depends on api/ and data/, not presentation/presentation/ importsdomain/ or api/domain/ or api/, implementations in data/domain/ or api/ (except Parcelable for Screen)@ContributesBinding used for interface bindings@ContributesIntoSet used for factory multibindings@AssistedInject / @AssistedFactory used correctly for runtime paramssrc/test/){Name}StateHolder.kt has {Name}StateHolderTest.kt (BehaviorSpec + Turbine){Name}Interactor.kt / {Name}UseCase.kt has {Name}Test.kt (BehaviorSpec){Name}Repository.kt has {Name}Test.kt (BehaviorSpec)fakes/ subpackagesrc/androidTest/){Name}Ui.kt has {Name}UiTest.kt (JUnit4 + robot pattern)robot/{Name}UiRobot.kt existstestdata/{Name}UiTestData.kt existsFlag any gaps.
Beyond issues, suggest improvements that are directly relevant to the changed code:
remember, etc.)Present a structured report:
Brief overview of the changes and overall assessment (ready to merge, needs work, etc.).
Show all completed checklists from Steps 3-5 with pass/fail/not-applicable indicators.
Must fix before merge. Include file path and line references.
Should fix. Style issues, potential problems, missing patterns.
For each file missing tests or test cases:
/add-tests @<filepath> to generate themImprovement opportunities. These are optional but recommended.