Pida-Server

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 reviewing a PIDA branch, diff, or PR. Focus on bugs, regressions, missing tests, API contract drift, persistence risks, and operational issues before style comments.

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.