code-review-md
Code Review (Markdown Report)
Overview
Variant of the code-review skill that persists findings to .reviews/<YYYY-MM-DD>_<short-sha>.md.
Announce at start: "I'm using the code-review-md skill to write a markdown review report."
Workflow
Before starting, Read the main code-review SKILL.md at <plugin-root>/skills/code-review/SKILL.md — the Review Process steps, severity table, language reference mapping, and report markdown template all live there. The variant relies on those sections.
Then follow the Review Process in the main SKILL.md exactly — steps 1–3 (gather context, load references, analyze) and step 6 (conversation summary). For step 4, always write the markdown report to .reviews/. Skip step 5 (HTML).
In short:
More from chann/skills
code-review
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).
10code-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