菜单
Java service standards for Bitso projects. Covers tech stack requirements, project organization, code review guidelines, MapStruct usage, and build verification practices. Use when creating new Java services or reviewing existing code.
用 Codex 或 Claude 帮你安装 复制这段 Prompt，粘贴到 Codex、Claude 或其他助手里，让它检查 Skill 页面并帮你完成安装。
基于 SOC 职业分类
RFC-39 compliant API best practices for Java services. Covers request/response patterns, error handling, pagination, versioning, and authentication standards. Use when designing or reviewing REST APIs in Java services.
RFC-29 compliant changelog management with Common Changelog format and Unreleased section extension. Validates changelog on commits, generates from git history, and ensures all merged PRs are documented. Use when setting up changelog workflows or retrofitting existing repositories.
Systematic workflow for CodeRabbit reviews - local CLI, PR threads, and commit attribution
Enforces consistent coding standards across the codebase including naming conventions, code organization, and documentation requirements. Use when writing new code, reviewing pull requests, or refactoring existing code.
Database integration patterns for Java services using jOOQ and Flyway. Covers code generation, read/write splitting, migration guidelines, and version compatibility. Use when setting up or maintaining PostgreSQL integration.
Version catalog strategy, dependency management, BOMs, and version constraints for Java/Gradle projects. Covers version centralization, never-downgrade policy, bundle patterns, resolution strategies, and compatibility matrices.
| name | java-standards |
| description | Java service standards for Bitso projects. Covers tech stack requirements, project organization, code review guidelines, MapStruct usage, and build verification practices. Use when creating new Java services or reviewing existing code. |
| compatibility | Java projects using Gradle with Spring Boot |
| metadata | {"version":"1.0.0","technology":"java","category":"standards","tags":["java","standards","code-review","project-structure","mapstruct"]} |
Java service standards for Bitso projects.
📚 references/ - Detailed documentation
| Component | Version | Notes |
|---|---|---|
| Java | 21 (LTS) | Current LTS version |
| Gradle | 9.2.1 | Recommended for all projects |
| Spring Boot | 3.5.9 | Latest (min 3.5.9) - preparing for Spring Boot 4 |
| Database Access | jOOQ | For accessing PostgreSQL |
| Databases | PostgreSQL, Redis | Primary data stores |
| Inter-service Communication | gRPC | Standard protocol |
| Object Mapping | MapStruct | For DTO/domain mapping |
For Spring Boot upgrades, use /upgrade-to-recommended-versions.
Projects should be organized with domain-based modules:
root-project/
├── build.gradle
├── settings.gradle
├── docs/ # Documentation
├── bitso-libs/ # Library modules
│ ├── <subdomain>/ # Domain logic
│ └── <subdomain-proto>/ # Protobuf definitions
└── bitso-services/ # Service modules
└── <domain>/ # Spring Boot application
After updating Java or Groovy code, verify changes:
# Run tests to verify changes
./gradlew test 2>&1 | grep -E "FAILED|Error" || echo "All tests passed"
# Or run full build with tests
./gradlew build 2>&1 | grep -E "FAILED|Error" || echo "Build successful"
If problems are found, fix them before committing.
| Reference | Description |
|---|---|
| references/services.md | Tech stack, project structure, dependency management, MapStruct |
| references/code-review.md | Java 21 standards, coding style, var keyword usage |
| references/build-verification.md | Build commands and verification practices |
| Skill | Purpose |
|---|---|
| gradle-standards | Gradle configuration |
| grpc-services-rfc-33 | gRPC service implementation |
| database-integration | jOOQ and Flyway |