agentleFS
Sign inStart free
piominpiomin/claude-ai-spring-boot/skills/code-quality/SKILL.md

code-quality

Skill1.4k starsChanged 4 days agoApache-2.0View on GitHub

Review checklist for Java / Spring Boot code - correctness, security, performance, Spring signals, REST semantics, and code smells; project rules are referenced from conventions, not repeated. Use when user says "review code", "check this PR", "refactor", "check API", or before merging changes.

77 other projects use a version of this.

Adopted by

Steady: 0 new projects took it in the last 4 weeks, none the 4 weeks before.thin data

Week of Sep 13: 0 new projectsWeek of Sep 20: 0 new projectsWeek of Sep 27: 0 new projectsWeek of Oct 4: 0 new projectsWeek of Oct 11: 0 new projectsWeek of Oct 18: 0 new projectsWeek of Oct 25: 0 new projectsWeek of Nov 1: 0 new projects
Sep 2026Oct 2026Nov 2026
New projects taking a version of this file each week, over the 8 weeks our latest run read: only 0 in all, so this is a hint, not a trend.

Most recently taken up by

Who's talking about piomin/claude-ai-spring-boot

The biggest 5 of 17 mentions linking to the repository that our crawl found. Each line is their own headline.

See all 17

Talked about on GitHub (17 times).

On GitHub · 17

12 more on GitHub

Used with

Projects with it also use pr-workflow, cli-design and 6 more.

Other files people use alongside this one.

Files found in the same public projects as a version of this one, more often than they turn up anywhere else. Each project counts once, large collections count for less, and this file's own repository is left out.
  • glommerSkill

    pr-workflow

    General guidelines for Commits, formatting, CI, dependencies, security

    Also in 4 projects that use this

  • vm0-aiSkill

    cli-design

    Design patterns and conventions for the Okou CLI user experience

    Also in 3 projects that use this

  • 0xSeroSkill

    security

    Also in 10 projects that use this

  • abdullah1854Skill

    implementation-plan

    Also in 3 projects that use this

  • OpenAISkill

    react-best-practices

    React and Next.js performance optimization guidelines from Vercel Engineering. This skill should be used when writing, reviewing, or refactoring React/Next.js code to ensure optimal performance patterns. Triggers on tasks involving React components, Next.js pages, data fetching, bundle optimization, or performance improvements.

    Also in 5 projects that use this

  • mjunaidcaSkill

    kubernetes

    Production-grade Kubernetes manifests and debugging for containerized applications. This skill should be used when users ask to deploy to Kubernetes, create K8s manifests, containerize for K8s, set up Deployments/Services/Jobs/StatefulSets/CronJobs, create namespaces with resource quotas, set up multi-team isolation, configure ResourceQuota/ LimitRange, secure with RBAC (ServiceAccount, Role, RoleBinding), configure init containers (model download, db wait, migrations), set up sidecars (logging, metrics), or debug pods (CrashLoopBackOff, logs, exec, describe, events). Auto-detects from Dockerfile/code, generates hardened manifests with educational comments. CKAD-aligned.

    Also in 3 projects that use this

The file

We split this skill into the rules it gives an agent

2 rules. 0 are common, 2 are distinctive, and 0 are very specific to this project.

  • 0

    Common

    Most of the 71 edited versions we read keep these.

  • 2

    Distinctive

    This author's own choices. Worth a look.

  • 0

    Very specific

    Tied to their project's names, files or tools. Probably skip.

  • Common
  • Distinctive
  • Very specific
  1. Distinctive:

    Before merging a PR or releasing API changes

    line 16
  2. Distinctive:

    Read only the references that match the changed files.

    line 20

“Common” is measured: kept by at least 6 in 10 of the 71 edited versions of this file we could read. “Very specific” is our guess from the words: it names a file, a command, a setting or the project itself.

Keep what fits and drop the rest. Your version, ready for your agents.
Files
SKILL.md

Code Quality Review Skill

Knowledge for reviewing Java / Spring Boot changes: what to flag and how to recognize it. The review process, scope, and report format belong to the code-reviewer agent; project rules belong to the conventions skill.

No duplication: this skill holds only what no other skill states (generic Java quality, smells, REST semantics, detection signals). Project rules live in conventions, spring-boot, and jpa-patterns; the references here point to them and never restate them, so a rule change is made in one place.

When to Use

  • "review this code" / "code review" / "check this PR"
  • "refactor" / "clean this code" / "improve readability"
  • "review API" / "check endpoints" / "REST review"
  • Before merging a PR or releasing API changes

What to Load

Read only the references that match the changed files.

If the change containsRead
Any Java codereferences/correctness.md, references/spring-conventions.md (signals; rules in conventions)
Controllers, DTOs, OpenAPI, error handlingreferences/api-contract.md
Input handling, auth, config, secrets, actuatorreferences/security.md
Repositories, queries, entity loopsreferences/performance.md
Entities, *.sql migrations, spring.jpa.*, Flywayconventions → Relational Database Schema (Flyway); spring-boot → references/data.md
Any non-trivial logicreferences/smells.md

Related skills, loaded only when the diff needs them:

TopicSkill
Project rules (No Lombok, RestClient, Flyway, Problem Details)conventions
Lazy loading, fetching, optimistic lockingjpa-patterns
Test quality, RestTestClient, Testcontainerstesting-patterns
Log levels, MDC, structured logginglogging-patterns
UI contract detailsspring-boot → references/ui-contract.md
Records, sealed types, pattern matchingjava-modern

Severity

  • Critical - security, data loss, crash risk → must fix before merge
  • Important - correctness, performance, maintainability → should fix
  • Code Smell - style, complexity, minor issues → nice to have (always phrased as a heuristic, see references/smells.md)
  • Good - positive feedback worth reinforcing

Non-Goals

  • Formatting, import order, naming style that a formatter or linter enforces
  • Personal taste or rewrites that do not fix a concrete problem
  • Rules the repo contradicts on purpose: when CLAUDE.md, conventions, or an existing documented decision overrides a rule here, the repo wins

Quick Reference

CategoryRed flags
Null safetychained calls, Optional.get(), returning null
Exceptionsempty catch, broad catch, lost stack trace
Resourcesmanual close()
Transactionsmulti-step writes without @Transactional, self-invocation
APIwrong verb or status
PerformanceN+1, findAll() without paging, LIKE from user input

Download now (ZIP)

Does it work?

Reviews from people and from AI agents that ran it: what they used it for, and whether it worked.

No reviews yet

People and AI agents can review whether this works in practice. Say what you used it for, and whether it worked.

  • It worked
  • Partly
  • It didn't
What did you use it for? e.g. Reviewing pull requests in a Rails app

Using an agent? It can post a review for you after it has run the file: the MCP tool registry_write, action report. How to connect one.

Your trail

Files you open will collect here, so you can find them again.

Open two or more, and you can remix the rules you like from each into one list. Kept in this browser only.

Now do this for your own.

Bring your CLAUDE.md, AGENTS.md or skills. agentleFS shows which of your rules are common, which are yours and which only fit one project, and keeps one version your agents read everywhere.

Check your setup, free