Code Review
Use when reviewing a branch, PR, diff, or work-in-progress changes - two-axis review of coding standards compliance and spec fidelity with concise actionable findings
Install
npx skills add PanPanFR/oh-my-openkilo --skill code-reviewgit clone --depth 1 https://github.com/PanPanFR/oh-my-openkilo.git /tmp/oh-my-openkilo
mkdir -p ~/.claude/skills
cp -r /tmp/oh-my-openkilo/skills/code-review ~/.claude/skills/code-reviewPersonal skills live in ~/.claude/skills. Use .claude/skills in a project folder to share a skill with your team.
From the SKILL.md
Two-axis review of the diff between `HEAD` and a fixed point the user supplies: - **Standards** — does the code conform to this repo's documented coding standards? - **Spec** — does the code faithfully implement the originating issue / spec? Both axes run as **parallel sub-agents** (or sequential in single-session) so they don't pollute each other's context, then this skill aggregates their findings. Findings format: one line per finding: `<file>:<line>: <severity> <problem>. <fix>.` Severity: `🔴 bug` (broken behavior) / `🟡 risk` (fragile/race/leak) / `🔵 nit` (style/naming, cap at 5) / `❓ q` (genuine question). The issue tracker should have been provided to you — if `docs/agents/issue-tracker.md` is missing, default to the local-markdown tracker. ## Process ### 1. Pin the fixed point Whatever the user said is the fixed point — a commit SHA, branch name, tag, `main`, `HEAD~5`, etc. If they didn't specify one, ask for it. Capture the diff command once: `git diff <fixed-point>...HEAD` (three-dot, so the comparison is against the merge-base). Also note the list of commits via `git log <fixed-point>..HEAD --oneline`. Before going further, confirm the fixed point resolves (`git rev-parse <fixed-point>`) and the diff is non-empty. A bad ref or empty diff should fail here — not inside two parallel sub-agents. ### 2. Identify the spec source Look for the originating spec, in this order:
Details
- Skill name
code-review- Repository
- PanPanFR/oh-my-openkilo
- Path
skills/code-review/SKILL.md- License
- MIT
- Repo updated
- 2 November 2026
FAQ
What does the Code Review skill do?
Use when reviewing a branch, PR, diff, or work-in-progress changes - two-axis review of coding standards compliance and spec fidelity with concise actionable findings
How do I install the Code Review skill?
skills CLI (Claude Code, Cursor, Codex and more): npx skills add PanPanFR/oh-my-openkilo --skill code-review. Skills go in ~/.claude/skills (personal) or .claude/skills (project), and Claude loads them automatically when a task matches the description.
Is Code Review popular?
It lives in PanPanFR/oh-my-openkilo, which has 9 GitHub stars and 1 forks.
Related skills
Adaptive
9PanPanFR/oh-my-openkilo
Instructions to make or update an app's UI so that it adapts to different Android devices including phones, tablets, foldables, laptops, desktop, TV, Auto, and XR. It includes how to handle different window sizes, pointing devices (such as mouse) and text entry devices (such as keyboard) using the Compose MediaQuery API, and how to preserve UI, navigation, scroll, and media playback state across configuration changes (such as folding/unfolding a foldable, rotating a device, or resizing a window). It also covers multi-pane layouts using Navigation3 Scenes, adaptive UI components (such as button
Agentmemory
9PanPanFR/oh-my-openkilo
Index for agentmemory internals: how it is wired into a host agent, its architecture and ports, configuration flags, capture hooks, MCP tool surface, and REST fallback. Use when installing or debugging agentmemory itself, when a memory tool name or parameter is unclear, or when capture is not recording. For normal recall and save work, use agentmemory-ops instead.
Agentmemory History
9PanPanFR/oh-my-openkilo
Read past work: resume the last session, recap recent sessions, list agent-linked commits, trace a line back to the session that wrote it, or compact the current conversation for handoff. Use when the user says "where were we", "resume", "recap", "session history", "what did we do", "why is this code here", "who wrote this", or "handoff".
Git Commit
9PanPanFR/oh-my-openkilo
Use when user asks to commit changes, mentions "/commit", "commit message", or stages changes - conventional commit message generation from diff, type/scope auto-detection, intelligent staging, git safety
Caveman Review
9PanPanFR/oh-my-openkilo
Compressed code review - one line per finding with location, problem and fix. Use for /caveman-review, "review this PR", or "review the diff".
Artifact Hygiene
9flurdy/agent-skills
Run a local-only, read-only advisory audit of publishable working-tree files and unpublished branch history with redaction-safe findings.
Browse the most popular Claude skills, all git & code review skills, or write your own with the skills generator.