a-pavithraa/springboot-skills-marketplace / plugins/springboot-architecture/skills/spring-boot-team-harness
spring-boot-team-harness
VerifiedUse when a team wants every developer's coding agent (Claude Code or Codex) to follow the same rules and coding conventions on a Maven or Gradle Spring Boot 4 repository: setting up AGENTS.md, coding standards, guardrails, shared agent settings, or build and CI checks that agents must pass before code merges. It adds ./mvnw verify or ./gradlew build gates that fail on null-safety bugs (NullAway with JSpecify), module-boundary breaches (Spring Modulith), unknown or deprecated Boot property keys, Spring mistakes that compile (ArchUnit) and unformatted code, Claude Code and Codex hooks that run those gates before a turn ends, and a CI workflow.
assets/project/REVIEW.md
View on GitHub# Review guide
Read this before reviewing a change, whether you are a person or an agent. It lists only what the code doesn't show.
## Failures: report every break of these
<!-- The rules a reviewer can't infer from the code, one line each, for example:
1. Patient data is audited before it is returned, and a failed audit returns 503 and no data.
2. 404 means "no record"; 503 means "we could not ask". Never show an outage as "nothing found".
Add a line each time a review misses a bug that one would have caught. -->
## Risk
- High: security configuration, sign-in and access checks, database migrations, `{{BUILD_FILE}}`, CI workflows.<!-- Add the packages where a bug is expensive. --> Read the callers and the tests of what changed, and check each rule above that the change touches.
- High: `management.tracing.sampling.probability` raised in shipped config (it can overwhelm the trace store), `server.shutdown=immediate` (it drops requests during deploys), and `include-parameter-values` turned on (it puts personal data in spans).
- High: a log line, exception message or `addKeyValue` that holds personal data or a credential.<!-- observability:begin --> `LogLeakCheck` catches emails and credentials on tested paths; names, phone numbers and untested paths need a reader.<!-- observability:end -->
- High: a `catch` that returns a default or a success response without logging, or a 5xx built by hand in a controller.<!-- failure-filter:begin --> `HandledFailureFilter` only sees exceptions that reach an `@ExceptionHandler`.<!-- failure-filter:end -->
- Medium: a log line inside a loop or on every request at INFO or above, an expected client error logged as ERROR, or the same failure logged again on its way up.<!-- observability:begin --> The Log lines by level panel shows the effect.<!-- observability:end -->
- Medium: a security failure with no log line: failed sign-ins and refused access should leave a WARN.
- Medium: an ID or free text as a metric tag, which creates one series per value. Put it in a span instead. A `@KafkaListener` or `KafkaTemplate` without `observationEnabled`, which ends the trace at the topic.
- Low: docs, changes to tests only, frontend copy and styling. A quick pass is enough.
## Don't report
- Formatting and import order: {{FORMATTER}} checks them.
- What the build already fails on: NullAway, `CodeRulesTests` and the other rule tests.
- Naming and comment style, unless they hide a bug.
## Report
Give every finding a file and line. Mark findings in code the change didn't touch as pre-existing. End with the number of findings, or "No issues found".
Related skills
| Skill | Stars | Updated | Works with | Status | Install |
|---|---|---|---|---|---|
| reverse-engineer-anythingmorluto/reaReverse engineer native, managed, Electron/JavaScript, packaged, firmware, and browser targets with REA, and build agent environments (AgentEnv bundles) of web applications from a live instance or a capture, and of Linux desktop apps with a task from a request. Use shipped-artifact or requested runtime evidence to explain features, compare versions, decompile code, or guide a reconstruction. Skip REA for ordinary source-repository architecture analysis. | Stars: 472k | Updated | Claude CodeCodex | Verified | Install |
| diagnosing-superpowersobra/superpowersUse when a superpowers session went wrong and your human partner wants to know why — repeated work, ignored plans, stumbles, poor results, a skill that didn't fire, "it took too long", "why is it so expensive", "what is it doing" — or wants to build a bug report for the superpowers maintainers, for the current session or a past one identified by id or path, on any harness. | Stars: 322k | Updated | Claude CodeCodex | Verified | Install |
| dispatching-parallel-agentsobra/superpowersUse when facing 2+ independent tasks that can be worked on without shared state or sequential dependencies | Stars: 322k | Updated | Claude CodeCodex | Verified | Install |
| executing-plansobra/superpowersUse when executing an implementation plan in the current session as the implementer yourself — your human partner chose inline execution, or no subagent tool is available | Stars: 322k | Updated | Claude CodeCodex | Verified | Install |