Agent skill

Code Review

by JiHong88 in JiHong88/suneditor

코드 리뷰 — 버그, 로직 오류, 성능 회귀, 수명 관리 및 프로젝트 규칙 위반 검출. An agent skill from JiHong88/suneditor.

MITAuto-check passedDevelopment

Install Code Review

skills CLI
$ npx skills add JiHong88/suneditor --skill code-review -a claude-code

Project install by default; add -g for ~/.claude/skills/.

GitHub CLI
$ gh skill install JiHong88/suneditor code-review --agent claude-code

Project scope by default; add --scope user for a personal install. Needs GitHub CLI 2.90.0 or later (public preview).

Manual copy
$ git clone --depth 1 https://github.com/JiHong88/suneditor.git skills-src && mkdir -p .claude/skills && cp -r skills-src/.agents/skills/code-review .claude/skills/code-review && rm -rf skills-src

Use ~/.claude/skills/ instead of .claude/skills for a personal install. The folder must contain SKILL.md.

Claude Code skills documentation · loads skills from .claude/skills/

Facts

Skill name
code-review
GitHub stars
2k
Token cost
~590 tokens
SKILL.md length
311 words
Files
1
Skills in repo
5
Repo updated
First seen
Licence
MIT

At a glance

코드 리뷰 — 버그, 로직 오류, 성능 회귀, 수명 관리 및 프로젝트 규칙 위반 검출. An agent skill from JiHong88/suneditor.

  • Works in 5 steps: Read AGENTS.md, applicable rules and… → Exclude test/dev/ files from review —… → Analyze for → …
  • Tasks that involve Code review
  • Calls git

What it does

Code Review is an agent skill from JiHong88/suneditor. 코드 리뷰 — 버그, 로직 오류, 성능 회귀, 수명 관리 및 프로젝트 규칙 위반 검출

Its SKILL.md is about 590 tokens, which your agent loads only when the skill is triggered. It is a single SKILL.md file with no bundled scripts.

It sits in Development, covering Code review. It works with Git. The repository describes itself as: A lightweight and powerful WYSIWYG editor in vanilla JavaScript. No dependencies. The licence is MIT.

When your agent uses it

  • Tasks that involve Code review

Example prompts

  • “/code-review”

Workflow steps

5 steps, taken from the first numbered list in SKILL.md.

  1. Read AGENTS.md, applicable rules and prompts/coding-rules.md. If arguments are provided, read those files. Otherwise inspect both git diff…
  2. Exclude test/dev/ files from review — they are local dev-only and not review targets.
  3. Analyze for
  4. Report findings with file path and line numbers.
  5. Do NOT fix anything — report only. Let the user decide what to fix.

What it can do on your machine

Read from SKILL.md and the folder at commit 9de619b. It shows what the files ask for, not the result of running them.

  • Tool permissions

    Pre-approves nothing: there is no allowed-tools line, so your agent's usual permission prompts apply.

    From allowed-tools in the SKILL.md frontmatter.

  • Runs code

    Shell commands in SKILL.md call:

    • git

    From the folder's file list and the shell code blocks in SKILL.md.

  • Network

    No URLs in SKILL.md. Its commands use git, which can reach the network depending on how they are called.

    From URLs in SKILL.md, links to its own repository left out.

  • Credentials

    Names no API keys, tokens, secrets or passwords.

    From names ending in _API_KEY, _TOKEN, _SECRET, _KEY or _PASSWORD in SKILL.md.

Context cost

Code Review loads about 590 tokens when it runs. Until then it costs about 15 tokens; SKILL.md has 311 words of instructions outside code blocks.

Always · name and description, kept in context so the agent knows when to use it
~15
When it runs · the whole SKILL.md, loaded when a task matches
~590

Estimates: characters ÷ 4, the usual rule of thumb; real counts depend on the model's tokenizer. Scripts and assets cost tokens only if the agent reads them.

Safety

Auto-check passed

The automated check found no risky patterns in SKILL.md.

Automated static check — not a guarantee. Review scripts before installing. It scans the text of SKILL.md for risky patterns (piping downloads into a shell, reading credential files, hidden Unicode, destructive commands); files beside SKILL.md are not scanned.

SKILL.md

The full file from JiHong88/suneditor at commit 9de619b, republished under its MIT licence (© JiHong88). 311 words, ~590 tokens.

Download SKILL.mdSave it as .claude/skills/code-review/SKILL.md (or your agent's skills folder).
name
code-review
description
코드 리뷰 — 버그, 로직 오류, 성능 회귀, 수명 관리 및 프로젝트 규칙 위반 검출

Review the specified file(s) or current git diff for bugs, logic errors, and dead code.

Target: $ARGUMENTS (file path, or blank for current diff)

Steps:

  1. Read AGENTS.md, applicable rules and prompts/coding-rules.md. If arguments are provided, read those files. Otherwise inspect both git diff and git diff --cached, plus relevant untracked files from git status --short. Do not alter the index.
  2. Exclude test/dev/ files from review — they are local dev-only and not review targets.
  3. Analyze for:
    • Logic bugs (off-by-one, null access, race conditions)
    • Dead code (unreachable branches, unused variables)
    • Missing edge cases in the changed path, including undo/cancellation/frame ownership
    • Avoidable repeated scans/serialization/layout on hot paths and work while the feature is inactive
    • Duplicate event registration, retained detached DOM, subscriptions/timers/observers/requests without effective cleanup
    • Reimplemented shared behavior, wrong history ownership, or import/API contract violations Read prompts/performance-guide.md for new features or performance-sensitive changes. Trace actual callers and cleanup before reporting a violation; legacy code is not automatically a template.
  4. Report findings with file path and line numbers.
  5. Do NOT fix anything — report only. Let the user decide what to fix.

Review guidelines — avoid false positives:

  • Null/guard checks: If a null check already exists upstream in the call chain (caller side), do NOT flag the callee for lacking its own null guard. Only flag if there is a realistic unguarded path.
  • Intentional patterns: If code looks intentional and consistent with surrounding patterns, do NOT report it as a bug. If unsure, note it as a confirmation question (e.g. "의도된 동작인지 확인: ...") rather than a bug.
  • Severity filtering: Report concrete incorrect behavior, demonstrable resource/performance regressions, or a specific project contract violation on the changed path. Include the triggering scenario and source evidence; label unmeasured cost concerns as such. Do not report style preferences, hypothetical future risks, or "would be nice" improvements.
  • staged/unstaged diff: Do not flag git staging state differences as findings.

© JiHong88, MIT. Rendered from Markdown: HTML in the file is shown as text, images as links, and headings moved down two levels. Raw file

Files

Just SKILL.md in .agents/skills/code-review of JiHong88/suneditor.

Open the folder on GitHubat commit 9de619b

Compare with similar skills

Code Review next to the 5 skills that share the most tags, products or categories with it. Stars are the repository's; “used in” counts other GitHub owners with a copy.

Code Review compared with similar skills
SkillStarsUsed inTokensAuto-checkLicenceRepo updated
Code Review this skillJiHong88/suneditor2k—~590Automated safety check: PassMIT
Code Review ChecklistshareAI-lab/learn-claude-code78k5 repos~1.1kAutomated safety check: PassMIT
Understand Diff AnalysisEgonex-AI/Understand-Anything86k1 repos~1.4kAutomated safety check: PassMIT
Open Code Review CLIalibaba/open-code-review44k—~3.1kAutomated safety check: PassApache-2.0
Hunk Diff Session Controlmodem-dev/hunk9.5k1 repos~3.4kAutomated safety check: PassMIT
Open Code Review Delegatealibaba/open-code-review44k—~2kAutomated safety check: PassApache-2.0

Similar skills

  • Code Review Checklist

    shareAI-lab/learn-claude-code

    Reviews code against a five-part checklist covering security, correctness, performance, maintainability and testing, and reports findings in a fixed format.

    78k GitHub starsUsed in 5 repos~1.1k tokens
    DevelopmentAuto-check passed
  • Understand Diff Analysis

    Egonex-AI/Understand-Anything

    Reads your git changes or a pull request against a prebuilt knowledge graph of the project to explain what changed, which components are affected and what is risky.

    86k GitHub starsUsed in 1 repo~1.4k tokens
    DevelopmentAuto-check passed
  • Open Code Review CLI

    alibaba/open-code-review

    Runs the ocr command-line tool to review Git changes, a commit or a branch comparison with an AI model, returning line-level comments and optionally applying fixes.

    44k GitHub stars~3.1k tokensUpdated 3 days ago
    DevelopmentAuto-check passed
  • Interacts with live Hunk diff review sessions via CLI. Inspects review focus, navigates files, hunks, and exact lines, reloads session contents, adds inline…

    9.5k GitHub starsUsed in 1 repo~3.4k tokens
    DevelopmentAuto-check passed
  • Open Code Review Delegate

    alibaba/open-code-review

    Has the host agent do the code review itself while the ocr CLI handles file selection and rule lookup, covering workspace changes, branch ranges or single commits.

    44k GitHub stars~2k tokensUpdated 3 days ago
    DevelopmentAuto-check passed
  • Code Review

    flutter/flutter

    Performs a comprehensive, multi-step code review of pull requests or local code changes, using iterative refinement (generation, critique, synthesis) to ensure high-quality, actionable feedback.

    179k GitHub stars~1.4k tokensUpdated today
    DevelopmentAuto-check passed

More from JiHong88/suneditor

  • Commit

    JiHong88/suneditor

    커밋 메시지를 자동 생성하고 커밋한다. An agent skill from JiHong88/suneditor.

    2k GitHub stars~715 tokensUpdated 3 days ago
    Auto-check passed
  • Post Edit

    JiHong88/suneditor

    코드 수정 후 범위에 맞는 lint, 타입 검사, 빌드 검증, 동작 및 성능 테스트 실행. An agent skill from JiHong88/suneditor.

    2k GitHub stars~829 tokensUpdated 3 days ago
    Auto-check: notes
  • Changes

    JiHong88/suneditor

    수동 코드 수정 후 changes.md에 누락된 변경사항 추가

    2k GitHub stars~240 tokensUpdated 3 days ago
    Auto-check passed
  • Release Note

    JiHong88/suneditor

    changes.md를 릴리즈 노트 형식으로 변환

    2k GitHub stars~275 tokensUpdated 3 days ago
    Auto-check passed

Works with

Categories

Questions about Code Review

What does Code Review do?

코드 리뷰 — 버그, 로직 오류, 성능 회귀, 수명 관리 및 프로젝트 규칙 위반 검출. An agent skill from JiHong88/suneditor. Code Review is an agent skill from JiHong88/suneditor.

When should I use Code Review?

Code Review fits situations like: tasks that involve Code review.

How do I install Code Review in Claude Code?

Run `npx skills add JiHong88/suneditor --skill code-review -a claude-code`. Or copy the skill folder (.agents/skills/code-review in JiHong88/suneditor) into .claude/skills/code-review in your project. Claude Code loads it when a task matches its description.

How do I install Code Review in Codex?

Run `npx skills add JiHong88/suneditor --skill code-review -a codex`. Or copy the skill folder (.agents/skills/code-review in JiHong88/suneditor) into .agents/skills/code-review in your project. Codex loads it when a task matches its description.

Can I use Code Review in Cursor, Gemini CLI or GitHub Copilot?

Cursor, Gemini CLI, GitHub Copilot and OpenCode also load SKILL.md folders. With the skills CLI, run `npx skills add JiHong88/suneditor --skill code-review -a cursor` (or -a gemini-cli, github-copilot or opencode for the others). To copy it by hand, put the folder in .cursor/skills/code-review, .gemini/skills/code-review, .github/skills/code-review and .opencode/skills/code-review in your project.

What does Code Review need to run?

Going by SKILL.md and its folder, Code Review needs the command-line tools its instructions call (git).

Does Code Review access the network?

SKILL.md contains no URLs. Its commands use git, which can reach the network depending on how they are called. This is read from the text; nothing was executed.

Is Code Review safe to install?

Our automated static check of SKILL.md found no risky patterns, such as piping downloads into a shell, reading credential files or hidden Unicode. It is not a guarantee. Review the folder before installing.

What licence does Code Review use?

Code Review is published under the MIT licence (the repository's licence). It allows redistribution, so the full SKILL.md is shown on this page.

How many tokens does Code Review use?

About 590 tokens (SKILL.md is roughly 2.4k characters). Agents keep only the skill's name and description in context until a task matches; then they load SKILL.md in full.

What are the alternatives to Code Review?

Skills that share tags, products or a category with Code Review: Code Review Checklist (shareAI-lab/learn-claude-code, 78k stars), Understand Diff Analysis (Egonex-AI/Understand-Anything, 86k stars), Open Code Review CLI (alibaba/open-code-review, 44k stars) and Hunk Diff Session Control (modem-dev/hunk, 9.5k stars). The comparison table on this page puts their stars, adoption, token cost, safety result and licence side by side.

Who maintains Code Review?

JiHong88 (a GitHub user) maintains it in JiHong88/suneditor, which has 2,018 GitHub stars. The repository holds 5 skills in this directory. The repository was last updated on October 6, 2026.

Source: JiHong88/suneditor on GitHub. Facts on this page come from the repository at the commit we read; the author's words are quoted as theirs.