code-review
Code Review Skill
Overview
Structured code review from git diffs. Analyzes changes for correctness, security, complexity, maintainability, and language-specific best practices, then presents findings either inline or as a persistent report.
Core principle: Diff in → severity-tagged findings out, scoped strictly to what changed.
Announce at start: "I'm using the code-review skill to review the requested changes."
Commands
| Command | Skill | Output | When to use |
|---|---|---|---|
/code-review (or implicit trigger) |
code-review |
Findings shown in conversation; no file | Quick interactive review |
/code-review-md |
code-review-md |
Markdown file at .reviews/<date>_<sha>.md |
Persistent record, share via git |
/code-review-html |
code-review-html |
Markdown file + self-contained HTML | Browser-readable report with badges, syntax highlighting, sidebar nav |
Command Examples
More from chann/skills
code-review-md
Use when the user asks to save a code review to a file, write a markdown review report, persist review findings, or generate a review file in `.reviews/`. Trigger on phrases like "review my changes and save", "write the code review", "리뷰 결과 파일로 저장", "마크다운 리뷰 보고서", "/code-review-md". For interactive (no-file) review use the `code-review` skill; for HTML output use `code-review-html`.
8code-review-html
Use when the user asks for a styled HTML code review report, a browser-readable review, or both markdown + HTML output. Trigger on phrases like "/code-review-html", "HTML 리뷰 보고서", "styled review report", "review with badges/sidebar". For markdown-only output use `code-review-md`; for in-conversation review use `code-review`.
8long-task
Use when the user asks to build a project end-to-end, run autonomous multi-hour or multi-day development, or orchestrate multi-milestone work without human intervention. Trigger phrases include "build this whole project", "implement this end-to-end", "do this autonomously", "run a long task", "long-running agent", "build it from scratch and don't ask", or the explicit `/long-task` command. Also use for lifecycle subcommands such as `/long-task status`, `/long-task pause`, `/long-task resume`, `/long-task clear`, and `/long-task complete`.
5git-commit
Use when the user asks to commit changes, organize commits, write commit messages, or split working-tree changes into Conventional Commits. Trigger on phrases like "commit my changes", "커밋해줘", "커밋 분리", "make commits", "/git-commit", or whenever the user wants to turn current changes into Conventional Commit-style commits. For commit + push use `git-commit-push`; for rewriting non-Conventional commit history use `git-commit-rewrite`.
5git-commit-push
Use when the user asks to commit working-tree changes AND push to the remote. Trigger on phrases like "commit and push", "커밋하고 푸시해줘", "/git-commit-push", "push my commits". Runs the git-commit workflow, then `git push` (never `--force`). For commit-only use `git-commit`; for history rewrite use `git-commit-rewrite`.
5git-merge-to-dev
Use when the user asks to merge the current branch into the dev branch (`dev`, falling back to `develop`) and delete the merged source branch. Trigger on phrases like "merge to dev", "dev에 머지", "develop에 합쳐줘", "merge this into dev and delete it", "/git-merge-to-dev". Switches to dev/develop, merges the source branch, then runs `git branch -d` on the source. For `main` use `git-merge-to-main`; to bulk-clean already-merged branches use `git-branch-cleanup`.
5