Caveman Review

Compressed code review - one line per finding with location, problem and fix. Use for /caveman-review, "review this PR", or "review the diff".

9 stars 1 forksGit & Code Review

Install

skills CLI (Claude Code, Cursor, Codex and more)
npx skills add PanPanFR/oh-my-openkilo --skill caveman-review
Manual install
git 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/caveman-review ~/.claude/skills/caveman-review

Personal skills live in ~/.claude/skills. Use .claude/skills in a project folder to share a skill with your team.

From the SKILL.md

Write code review comments terse and actionable. One line per finding. Location, problem, fix. No throat-clearing.

## Rules

**Format:** `L<line>: <problem>. <fix>.` — or `<file>:L<line>: ...` when reviewing multi-file diffs.

**Severity prefix (optional, when mixed):**
- `šŸ”“ bug:` — broken behavior, will cause incident
- `🟔 risk:` — works but fragile (race, missing null check, swallowed error)
- `šŸ”µ nit:` — style, naming, micro-optim. Author can ignore
- `ā“ q:` — genuine question, not a suggestion

**Drop:**
- "I noticed that...", "It seems like...", "You might want to consider..."
- "This is just a suggestion but..." — use `nit:` instead
- "Great work!", "Looks good overall but..." — say it once at the top, not per comment
- Restating what the line does — the reviewer can read the diff
- Hedging ("perhaps", "maybe", "I think") — if unsure use `q:`

**Keep:**
- Exact line numbers
- Exact symbol/function/variable names in backticks
- Concrete fix, not "consider refactoring this"
- The *why* if the fix isn't obvious from the problem statement

## Examples

āŒ "I noticed that on line 42 you're not checking if the user object is null before accessing the email property. This could potentially cause a crash if the user is not found in the database. You might want to add a null check here."

āœ… `L42: šŸ”“ bug: user can be null after .find(). Add guard before .email.`
Read the full skill on GitHub

Details

Skill name
caveman-review
Path
skills/caveman-review/SKILL.md
License
MIT
Repo updated
2 November 2026

FAQ

What does the Caveman Review skill do?

Compressed code review - one line per finding with location, problem and fix. Use for /caveman-review, "review this PR", or "review the diff".

How do I install the Caveman Review skill?

skills CLI (Claude Code, Cursor, Codex and more): npx skills add PanPanFR/oh-my-openkilo --skill caveman-review. Skills go in ~/.claude/skills (personal) or .claude/skills (project), and Claude loads them automatically when a task matches the description.

Is Caveman Review popular?

It lives in PanPanFR/oh-my-openkilo, which has 9 GitHub stars and 1 forks.

Related skills

Adaptive

9

PanPanFR/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

Mobile Development

Agentmemory

9

PanPanFR/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.

AI, LLMs & Agents

Agentmemory History

9

PanPanFR/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".

AI, LLMs & Agents

Code Review

9

PanPanFR/oh-my-openkilo

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

Git & Code Review

Pilot Github Bridge

9

TeoSlayer/pilot-skills

Bridge GitHub webhook events as Pilot Protocol events. Use this skill when: 1. You need to receive GitHub events in Pilot agents 2. You want to trigger agent actions on repository events 3. You're building CI/CD workflows with Pilot agents Do NOT use this skill when: - You need direct GitHub API access (use gh CLI instead) - GitHub webhooks are not configured - The daemon is not running

Git & Code Review

Git Commit

9

PanPanFR/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

Git & Code Review

Browse the most popular Claude skills, all git & code review skills, or write your own with the skills generator.