Organize screens, APIs, data models, state management, folder layout, and integration boundaries before implementation. Use it when you need a clear technical structure and responsibility split up front.
Review security risks around login, sessions, tokens, authorization checks, admin boundaries, and secret exposure. Use it for changes involving auth or sensitive data handling.
Analyze the impact surface, regression paths, and additional validation points for a change or diff. Use it to quickly understand which surrounding areas also need attention.
Perform a general code review. Use it to inspect PRs, commits, diffs, or local changes for functional bugs, regressions, security issues, performance degradation, missing tests, and maintainability risks. Apply it when the user asks for a code review, PR review, risk check, or merge-readiness assessment.
Explain the structure, responsibilities, entry points, and dependencies of a directory, module, or feature. Use it to understand an unfamiliar codebase or gather context before making changes.
Generate Korean Conventional Commit messages from a change summary or diff. Use it when you need to write, refine, or propose commit message candidates.
Structure bug reports, requirements, logs, or screenshots into actionable GitHub issues. Use it when you need acceptance criteria, scope definition, and a validation plan.
Inspect the integration points between frontend, backend, database, and external APIs. Use it to detect contract mismatches, missing environment variables, broken assumptions, or setup-order issues.