This skill should be used when the user wants to "review code", "check code quality", "run code review", or needs local code quality verification before git push. Runs lint, typecheck, and code review on changed files.
This skill should be used when the user wants to "validate a command", "review my command", "check command quality", "audit slash command", or needs evaluation of their Claude Code custom command against best practices.
This skill should be used when the user wants to "commit", "make a commit", "save changes", "git commit", "커밋", "커밋 해줘", "변경사항 저장", or needs to create a git commit following Conventional Commit format. Also triggers when the user asks to commit after finishing implementation work (e.g., "done, commit this", "작업 끝났어 커밋해줘"). Automatically analyzes staged/unstaged changes and generates a one-line conventional commit message.
This skill should be used when the user wants to "make a pr", "create a pr", "create pull request", "open pr", or needs to generate a pull request with title and body from current branch changes.
This skill should be used when the user wants to "reflect on instructions", "analyze claude config", "analyze codex config", "review agent setup", or needs analysis and improvement suggestions for Claude Code or Codex instructions and configuration.
This skill should be used when the user wants to "respond to review", "리뷰 대응", "PR 리뷰 반영", "리뷰 코멘트 처리", "address review comments", or needs to process PR review feedback by analyzing comments, deciding accept/reject, modifying code, and posting responses.
This skill should be used when the user wants to "retrospect", "review session", "look back", or needs to analyze the current session and suggest more efficient collaboration methods.