junjuny0227/nest-blog-api

backend-architecture

Plan and review nest-blog-api NestJS module structure, dependency injection, entity design, and API contract scope. Use for any module creation, cross-module dependency decision, or architecture scope question.

원문 언어: 영어

code-review

Review nest-blog-api changed files using dynamically discovered .claude/rules, NestJS module conventions, DTO validation, service/controller boundaries, security basics, and validation results. Use for code review requests, staged diff review, pre-PR review,…

원문 언어: 영어

commit

Create actual nest-blog-api Git commits by inspecting changed files, splitting logical units, staging the right files, and running git commit with project Conventional Commit messages. Use when the user explicitly asks to commit, make a commit, split commits,…

원문 언어: 영어

module-flow

Implement nest-blog-api NestJS modules: controllers, services, DTOs, entities, guards, and module registration. Use whenever a task touches request handling, business logic, data persistence, or DTO validation.

원문 언어: 영어

orchestrator

Coordinate the nest-blog-api agent team for backend features, bug fixes, refactors, module implementation, API design, database schema, QA, code review, debugging, branch names, actual commits, PR creation, and PR review comment replies. Use this skill for…

원문 언어: 영어

quality-gate

Verify nest-blog-api changes with npm run lint, npm run build, npm run test, module registration coherence, DTO validation coverage, service exception handling, and integration boundary review. Use after implementation, during reviews, for reruns, and…

원문 언어: 영어

review-pr

Collect nest-blog-api GitHub PR review comments, assess each comment against project rules, apply valid fixes when safe, optionally commit and push fixes, and post Korean replies with gh api. Use only when the user explicitly asks to address PR review…

원문 언어: 영어

systematic-debugging

Investigate nest-blog-api bugs, build failures, test failures, runtime errors, validation issues, and unexpected behavior by finding root cause before fixes. Use whenever debugging, test failure, build failure, regression, or unclear behavior is mentioned.

원문 언어: 영어

write-pr

Create an actual GitHub pull request for nest-blog-api from the current branch. Gathers commits and diff, generates a Korean PR title/body following the repository template, selects labels, asks for title confirmation, then runs gh pr create. Use only when…

원문 언어: 영어