Write unit, integration, and slice tests for Spring Boot 3 applications. Use when writing unit tests, integration tests, or slice tests for Spring Boot 3 applications.
インストールする前に、エージェントに与えられる指示の中身を確認できます。
[BE-TEST-01] Parameterized Tests for Equivalent Cases: Prefer @ParameterizedTest (@CsvSource, @MethodSource) when methods have multiple equivalent inputs or boundary permutations. Distinct scenarios may stay separate test methods. Reviewers must not demand parameterized rewrites without a behavioral gap.[BE-TEST-02] Ban on Brittle DB Mock String Matching: Do not use string-matching mocks for raw SQL queries. Test pure domain calculations directly, or use Testcontainers for database repository verification.[BE-TEST-03] Ban on Shallow Assertions: Never assert only assertThat(result).isNotNull() without inspecting domain fields, status codes, and invariants.[BE-TEST-04] Ban on Pass-Through Interface Mocks: Repositories and service handlers must test contract compliance and error mapping. Ban 1:1 pass-through mock echoing without contract assertions.[BE-TEST-05] Bug-First Regression Lock: Every PR fixing a bug ticket or with title fix(...) must introduce a test reproducing the defect prior to the fix.returns 404) ([BE-TEST-05]).[BE-TEST-01]).[BE-TEST-02]): Use Testcontainers for DB/Queues. Avoid H2/Embedded.[BE-TEST-03]): Use AssertJ (assertThat) over JUnit assertions; avoid shallow checks.[BE-TEST-04]): Use @MockBean for downstream dependencies in Slice Tests; avoid pass-through mock echoing.See implementation examples for WebMvcTest slice tests and Testcontainers integration tests.
[BE-TEST-01] Stylistic parameterized rewrites: Do not demand parameterized refactoring of passing tests without a behavioral gap.[BE-TEST-02] Brittle DB mock string matching: Do not match raw SQL strings in mocks; use Testcontainers.[BE-TEST-03] Shallow assertions: Never assert only assertThat(result).isNotNull() without inspecting domain fields or status codes.[BE-TEST-04] Pass-through mock echoing: Ban 1:1 pass-through mock echoing without contract assertions.[BE-TEST-05] Bug fix without reproduction test: Ban bug fixes without a regression test.まだレビューはありません。使ってみた感想をお寄せください。
概要と使いどころ
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.
日本語の概要は準備中です。原文の説明を表示しています。
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.
日本語の概要は準備中です。原文の説明を表示しています。
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.
日本語の概要は準備中です。原文の説明を表示しています。
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.
日本語の概要は準備中です。原文の説明を表示しています。
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.
日本語の概要は準備中です。原文の説明を表示しています。
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.
日本語の概要は準備中です。原文の説明を表示しています。