Brain-up/brn / .claude/skills/verify
verify
VerifiedRun the backend verification loop after Kotlin/Spring code changes — Kotlin style + unit tests via `gradlew verify`, plus integration tests when repos/migrations changed — and drive fixes until green. Use after editing backend code or when the user asks to verify/check the build.
Verify
The routine for confirming a backend change is correct. Fix the implementation to satisfy the checks; never weaken the checks to fit the implementation.
Steps
-
Scope the change. Note which files/modules changed. If you touched repositories, Flyway migrations (
src/main/resources/db/migration), or any*ITtest, mark that integration verification is required. -
Fast feedback while iterating (optional). For a quick loop on one area, run the narrowest useful target first, e.g.
gradlew test --tests "com.epam.brn.service.SomeServiceTest". -
Run the gate.
gradlew verify— this isktlintCheck+ unittest, no Docker. Do not treat the task as done until it exits 0. -
On failure, find the root cause. Read the actual failure (assertion, compile error, or ktlint rule). Fix the implementation. Only edit a test if the test itself is provably wrong — then state explicitly what you changed and why. Never delete/skip/
@Disableda test just to go green. -
Repeat steps 3–4 until
gradlew verifypasses. -
Style. Run
gradlew ktlintFormatbefore finishing; the ktlint gate fails the build otherwise. Re-rungradlew verifyif it reformatted anything. -
Integration (only if step 1 flagged it). Ensure Docker is running, then
gradlew integrationTest. These use a Postgres Testcontainer and are slow — run them once at the end, not on every edit.
Conventions to respect
- Test stack is fixed: JUnit 5 + MockK + kotest-assertions. Do not introduce
Mockito, AssertJ, Kluent,
kotlin.test, or JUnitAssertions(see CLAUDE.md). gradlew verifyis a local pre-PR gate, not a replacement for CI/Sonar.
Related skills
| Skill | Stars | Updated | Works with | Status | Install |
|---|---|---|---|---|---|
| finishing-a-development-branchobra/superpowersUse when implementation is complete, all tests pass, and you need to decide how to integrate the work | Stars: 319k | Updated | Claude CodeCodex | Verified | Install |
| systematic-debuggingobra/superpowersUse when encountering any bug, test failure, or unexpected behavior, before proposing fixes | Stars: 319k | Updated | Claude CodeCodex | Verified | Install |
| test-driven-developmentobra/superpowersUse when implementing any feature or bugfix, before writing implementation code | Stars: 319k | Updated | Claude CodeCodex | Verified | Install |
| skill-creatoranthropics/skillsCreate new skills, modify and improve existing skills, and measure skill performance. Use when users want to create a skill from scratch, edit, or optimize an existing skill, run evals to test a skill, benchmark skill performance with variance analysis, or optimize a skill's description for better triggering accuracy. | Stars: 196k | Updated | Claude CodeCodex | Verified | Install |