Test Python services with pytest, async coverage, monkeypatch, and boundary-focused fakes. Use when writing Python tests, fixtures, async tests, regression tests, or dependency-isolated verification.
The English summary is being prepared. Showing the original description.
See how to installReview the instructions the agent will receive before you install.
[BE-TEST-01] Parametrized Tests for Equivalent Inputs: Prefer pytest.mark.parametrize for equivalent inputs and boundary permutations. Distinct scenarios may stay separate.[BE-TEST-02] Ban on Brittle SQL String Matching: Test pure domain calculations directly or use fakes/testcontainers; do not regex-match SQL strings in mocks.[BE-TEST-03] Ban on Shallow Assertions: Never assert only assert result without inspecting domain attributes and invariants.[BE-TEST-04] Ban on Pass-Through Seam Mocks: Repositories and adapters must test contract compliance and error mapping; ban 1:1 pass-through mock echoing.[BE-TEST-05] Bug-First Regression Lock: Every PR fixing a bug ticket or with title fix(...) must introduce a failing test reproducing the defect before fixing it.pytest and pytest-asyncio for async boundaries.[BE-TEST-05]).pytest.mark.parametrize for equivalent inputs; distinct scenarios may stay separate ([BE-TEST-01]).[BE-TEST-02], [BE-TEST-04]).[BE-TEST-03]).[BE-TEST-05]).[BE-TEST-04]).[BE-TEST-03]).[BE-TEST-01] Stylistic parametrize rewrites: Do not demand parameterized rewrites of passing tests without a behavioral gap.[BE-TEST-02] SQL regex matching: Do not regex-match SQL strings in mocks.[BE-TEST-03] Shallow assertions: Never assert only assert result; always verify domain attributes and invariants.[BE-TEST-04] Pass-through seam mocks: Ban 1:1 mock echoing without contract assertions.[BE-TEST-05] Bug fix without reproduction test: Ban bug fixes without a reproduction test.No reviews yet. Tell others what you thought.
No login needed. Share how it worked for you, ask a question, or note where it did not run.
No comments yet. Be the first to write one.
Upgrade an Android project to Android Gradle Plugin (AGP) 9. Use when migrating to AGP 9, updating Gradle build files, migrating to built-in Kotlin, or adopting the new AGP DSL.
The English summary is being prepared. Showing the original description.
Apply Clean Architecture layering, modularization, and Unidirectional Data Flow in Android projects. Use when setting up project structure, placing code in layers, configuring feature/core modules, or implementing UDF patterns; defer Compose state and ViewModel/StateFlow implementation to their specific skills.
The English summary is being prepared. Showing the original description.
Implement WorkManager and background processing correctly on Android. Use when creating Worker classes, scheduling tasks, choosing between WorkManager and Foreground Services, or setting up Hilt in workers; defer FCM and notification delivery to android-notifications.
The English summary is being prepared. Showing the original description.
Build high-performance declarative UI with Jetpack Compose. Use when writing Composable functions, optimizing recomposition, hoisting state, or working with LazyColumn and side effects; defer deep-link and navigation routing to android-navigation.
The English summary is being prepared. Showing the original description.
Migrate an Android XML View to Jetpack Compose following a structured 10-step workflow. Use when converting XML layouts to Compose, setting up Compose in an existing View-based project, or incrementally adopting Compose.
The English summary is being prepared. Showing the original description.
Write correct coroutine scopes, lifecycle collection, and dispatcher injection in Android production code. Use for suspend functions, coroutine scopes, and dispatcher mechanics; defer ViewModel StateFlow/LiveData architecture, Fragment lifecycle recipes, persistence/notifications, and unit-test recipes to their specific skills.
The English summary is being prepared. Showing the original description.