Flooding-Server-V2

Creates a new git branch following the project's branch naming convention. Use this skill whenever the user wants to start new work, create a branch, switch to a new branch.

Generate PR title and body from commits since the base branch, then create the PR on GitHub following the project PR template exactly.

Check PR review comments, reflect valid feedback into code, commit, push, then reply to each comment with the resolving commit hash.

Create Git commits following Flooding project conventions. Splits changes into logical units with correct type prefix and Korean description.

Run a structured checklist over changed files — Kotlin style, JPA/transaction correctness, naming conventions, test coverage, and security basics. Produces a ✓/⚠/✗ report.

Run KtLint formatting on all Kotlin source files via Gradle. Use when .kt files need formatting or after bulk edits.

Kotest + MockK testing patterns for this project — BehaviorSpec structure, mock creation, stubbing, argument capture, and exception assertions. Reference when writing or reviewing test code.

Architecture reference for Flooding project — Controller/Service/Repository layer responsibilities, @Transactional strategy, ExpectedException usage, entity conventions, and response wrapping.

Implement a new API endpoint end-to-end — Repository → Service interface → Service impl → Controller, following Flooding project conventions.

Create a new JPA entity following Flooding project conventions — table naming, @field: annotation prefix, FetchType.LAZY, EnumType.STRING, and enum class patterns.

Conduct an in-depth structured interview with the user to uncover non-obvious requirements, tradeoffs, and constraints, then produce a detailed implementation spec file.

Verify security vulnerabilities — hardcoded secrets, SQL injection, JWT validation, sensitive logging, and authorization checks. Run before merging any auth or API-related changes.

Run tests and report results. Determines test scope based on context and analyzes failures in detail.