메뉴
Use when reviewing a PIDA branch, diff, or PR. Focus on bugs, regressions, missing tests, API contract drift, persistence risks, and operational issues before style comments.
Codex 또는 Claude로 설치 이 Prompt를 복사해 Codex, Claude 또는 다른 어시스턴트에 붙여 넣으면 Skill 페이지를 검토하고 설치를 진행할 수 있습니다.
SOC 직업 분류 기준
Use when committing or pushing PIDA changes. Plans safe commit groups, chooses Java 21 validation commands, enforces explicit confirmation, and remembers the repo's pre-commit ktlint behavior.
Use when adding or changing a PIDA API endpoint. Covers controller and DTO patterns, ApiResponseAdvice wrapping, Swagger annotations, and the minimum test and docs checks expected in this repo.
Use when you want to invoke PIDA project-scoped custom agents from the repository root. Gives ready-to-run Spawn-based command templates and prompt patterns for feature_mapper, ci_triager, api_reviewer, db_core_specialist, code_reviewer, and commit_push_guard, with Korean output by default.
Use when changing PIDA persistence or cache layers. Covers Entity, JpaRepository, CoreRepository, transaction helpers, soft delete filters, Redis cache placement, and geospatial patterns.
Use for validating or triaging build, test, lint, and JDK issues in PIDA. Covers Java 21, Gradle module selection, ktlint hook behavior, and CI parity for the core-api build.
| name | pida-code-review |
| description | Use when reviewing a PIDA branch, diff, or PR. Focus on bugs, regressions, missing tests, API contract drift, persistence risks, and operational issues before style comments. |
| metadata | {"short-description":"Review PIDA changes for real risks"} |
Use this skill when the user asks for a review, PR review, regression scan, or pre-merge check in PIDA.
./AGENTS.md for module boundaries and validation defaults.core-api: endpoint path and verb, auth, request validation, ApiResponseAdvice, ApiExceptionAdvice, Swagger annotationscore-api: also flag DTO files that bundle multiple unrelated top-level public classes when they should be split by concerncore-domain: facade or service boundaries, null handling, transaction assumptions, branching logicdb-core and redis: query filters, soft delete, repository contracts, cache invalidation, lock semanticsclients: request or response DTO compatibility, configuration properties, retry or error handlingreferences/review-checklist.md when you need the module-by-module checklist or review output shape.