Topic: claude-code
35,830 skills in this topic.
-
solid-principles
SOLID principles checklist with Java examples. Use when reviewing classes, refactoring code, or when user asks about Single Responsibility, Open/Closed, Liskov, Interface Segregation, or Dependency Inversion.
decebals/claude-code-java 495
-
api-contract-review
Review REST API contracts for HTTP semantics, versioning, backward compatibility, and response consistency. Use when user asks "review API", "check endpoints", "REST review", or before releasing API changes.
decebals/claude-code-java 495
-
java-migration
Guide for upgrading Java projects between major versions (8→11→17→21→25). Use when user says "upgrade Java", "migrate to Java 25", "update Java version", or when modernizing legacy projects.
decebals/claude-code-java 495
-
spring-boot-patterns
Spring Boot best practices and patterns. Use when creating controllers, services, repositories, or when user asks about Spring Boot architecture, REST APIs, exception handling, or JPA patterns.
decebals/claude-code-java 495
-
maven-dependency-audit
Audit Maven dependencies for outdated versions, security vulnerabilities, and conflicts. Use when user says "check dependencies", "audit dependencies", "outdated deps", or before releases.
decebals/claude-code-java 495
-
architecture-review
Analyze Java project architecture at macro level - package structure, module boundaries, dependency direction, and layering. Use when user asks "review architecture", "check structure", "package organization", or when evaluating if a codebase follows clean architecture principles.
decebals/claude-code-java 495
-
changelog-generator
Generate changelogs from git commits. Use when user says "generate changelog", "update changelog", "what changed since last release", or before preparing a new release.
decebals/claude-code-java 495
-
clean-code
Clean Code principles (DRY, KISS, YAGNI), naming conventions, function design, and refactoring. Use when user says "clean this code", "refactor", "improve readability", or when reviewing code quality.
decebals/claude-code-java 495
-
concurrency-review
Review Java concurrency code for thread safety, race conditions, deadlocks, and modern patterns (Virtual Threads, CompletableFuture, @Async). Use when user asks "check thread safety", "concurrency review", "async code review", or when reviewing multi-threaded code.
decebals/claude-code-java 495
-
security-audit
Java security checklist covering OWASP Top 10, input validation, injection prevention, and secure coding. Works with Spring, Quarkus, Jakarta EE, and plain Java. Use when reviewing code security, before releases, or when user asks about vulnerabilities.
decebals/claude-code-java 495
-
logging-patterns
Java logging best practices with SLF4J, structured logging (JSON), and MDC for request tracing. Includes AI-friendly log formats for Claude Code debugging. Use when user asks about logging, debugging application flow, or analyzing logs.
decebals/claude-code-java 495
-
test-quality
Write high-quality JUnit 5 tests with AssertJ assertions. Use when user says "add tests", "write tests", "improve test coverage", or when reviewing/creating test classes for Java code.
decebals/claude-code-java 495
-
performance-smell-detection
Detect potential code-level performance smells in Java - streams, collections, boxing, regex, object creation. Provides awareness, not absolutes - always measure before optimizing. For JPA/database performance, use jpa-patterns instead.
decebals/claude-code-java 495
-
git-commit
Generate conventional commit messages for Java projects. Use when user says "commit", "create commit", "commit changes", or after completing code changes that need to be committed.
decebals/claude-code-java 495
-
issue-triage
Triage and categorize GitHub issues with priority labels. Use when user says "triage issues", "check issues", "review open issues", or during regular maintenance of GitHub issue backlog.
decebals/claude-code-java 495
-
java-code-review
Systematic code review for Java with null safety, exception handling, concurrency, and performance checks. Use when user says "review code", "check this PR", "code review", or before merging changes.
decebals/claude-code-java 495
-
design-patterns
Common design patterns with Java examples (Factory, Builder, Strategy, Observer, Decorator, etc.). Use when user asks "implement pattern", "use factory", "strategy pattern", or when designing extensible components.
decebals/claude-code-java 495
-
bkend-data
bkend.ai database — CRUD, column types, filtering, sorting, relations, indexing.
Triggers: bkend table, CRUD, column, filter, sort, relation, 테이블, 데이터.
popup-studio-ai/bkit-claude-code 491
-
bkit-templates
PDCA document templates — Plan, Design, Analysis, Report with consistent structure.
Triggers: template, plan document, design template, 템플릿, 문서 양식.
popup-studio-ai/bkit-claude-code 491
-
audit
View audit logs, decision traces, and session history for AI transparency.
Triggers: audit, log, decision trace, history, 감사 로그, 결정 추적.
popup-studio-ai/bkit-claude-code 491
-
bkend-cookbook
bkend.ai project tutorials (todo to SaaS) and common error troubleshooting.
Triggers: bkend tutorial, cookbook, troubleshooting, 튜토리얼, 에러 해결.
popup-studio-ai/bkit-claude-code 491
-
bkit-rules
Core rules for bkit — PDCA methodology, level detection, agent triggering, quality standards.
Triggers: bkit rules, core rules, methodology, 핵심 규칙, PDCA 규칙.
popup-studio-ai/bkit-claude-code 491
-
bkend-storage
bkend.ai file storage — upload (presigned URL), download (CDN), visibility levels, buckets.
Triggers: bkend file, upload, download, presigned URL, storage, 파일 업로드, 스토리지.
popup-studio-ai/bkit-claude-code 491
-
bkend-quickstart
bkend.ai onboarding — MCP setup, resource hierarchy, tenant/user model, first project.
Triggers: bkend quickstart, onboarding, setup, MCP, 시작하기, 온보딩.
popup-studio-ai/bkit-claude-code 491