Loading...
Loading...
Found 127 Skills
Use when the user asks to review code, review changes, review a commit, review a PR, audit code quality, check for security issues, or generate a code review report. Trigger on phrases like "review my changes", "코드 리뷰", "check my code", "review the last commit", "what do you think of this diff", "compare branches", "code audit" — even if they don't say "code review" explicitly. For persistent file output use `code-review-md` (markdown) or `code-review-html` (markdown + HTML).
Post-implementation plan verification. Cross-references plans against actual changes for completeness and accuracy.
Review and understand freshly AI-generated code. Scans the current repo's uncommitted/branch changes and builds a Claude-style light-themed two-column webpage — the left side shows the project folder tree of changed files, the right side displays the syntax-highlighted diff of the selected file (with additions/deletions clearly distinguished from unchanged code), along with a sidebar that presents, for each code segment, the related unit requirement and plain-language code explanation. Trigger with commands like "/understand", "code review this change", "explain the newly generated code", "check this change"
Analyzes git diffs or staged changes and generates narrative commit messages that explain WHY a change was made, not just what changed — following Conventional Commits format. Use when asked to "write a commit message", "generate a commit", "describe my changes", "what should I commit this as", "commit this", "summarize my diff", or "help me commit". Works with git diff output, staged files, or plain descriptions of changes.
Review a merge request or branch. Compares a branch against main/master, summarizes changes, highlights concerns, and provides actionable feedback. Use for PR reviews or before merging.
Produces a single-story walkthrough of AI-authored code changes from runtime trigger to final behavior, weaving changed and unchanged code into one narrative with annotated diffs, trade-offs, alternatives, and risk analysis. Use when asked to "explain what changed", "walk me through this diff", "summarize agent edits", "show how this feature works", or "explain this implementation step by step".
Review a git diff or explicit file scope for reuse, code quality, efficiency, clarity, and standards issues, then optionally apply safe Codex-driven fixes. Use when the user asks to "simplify code", "review changed code", "check for code reuse", "review code quality", "review efficiency", "simplify changes", "clean up code", "refactor changes", or "run simplify".
Review changes starting from a fixed point (commit, branch, tag, or merge-base) along two axes: Standards (Does the code comply with the coding standards documented in this repository?) and Spec (Does the code meet the requirements from the source issue/PRD?). The two reviews run in parallel sub-agents and report side by side. This applies when users want to review a branch, PR, in-progress changes, or request a "review since X".
Open the diffity diff viewer in the browser to see your changes
Analyse code changes since the last docs update and refresh the project's documentation files. Use when code has changed and documentation needs to be updated, after implementing new features, or before a milestone commit.
Review code changes against accepted ADRs for compliance violations
Use when a change needs an independent code review before it moves on - a finished task, a feature branch, a pull request, or work-in-progress changes since a given ref - in any programming language. Pins the exact diff, gathers intent and constraints, and dispatches a read-only reviewer that returns separate verdicts and evidence-backed findings.