--- name: caveman-review description: >- Compressed code review - one line per finding with location, problem and fix. Use for /caveman-review, "review this PR", or "review the diff". title: caveman-review canonical_url: https://skilld.dev/gh/juliusbrussee/caveman/caveman-review last_updated: 2026-09-28T11:39:57.000Z --- > Index of every page on this site: [llms.txt](https://skilld.dev/llms.txt) > **Skill from skilld.dev.** Follow the user's requested action. > If the user asked to fork this Skill, follow the fork workflow below. Do not execute the Skill instructions while copying it. > Otherwise, follow the instructions below for this session. You do not need to install anything. > > Supporting files, fetch one when the Skill refers to it: [README.md](https://skilld.dev/api/skills-raw/juliusbrussee/caveman/caveman-review/README.md). > > If the user asked to install this Skill, run `npx skilld install juliusbrussee/caveman/caveman-review`. Install writes the Skill files into the project, so every session loads them. > > ## Fork workflow > > A fork creates an editable local Skill with its original author and licence. The request authorizes copying and local installation. > 1. Check `./skills/caveman-review`, the project lockfile, and selected Agent targets together. If the local directory or installed Skill exists, stop. Never overwrite an existing directory or Agent target. > 2. Read [source metadata](https://skilld.dev/api/v1/skills/juliusbrussee/caveman/caveman-review) once. Use sourceUrl, sourceCommit, skillPath, sourceGone, and license. If the source is gone or its path is missing, stop. If license is null, read licence files at the source commit. > 3. Fetch only the source commit into a temporary Git repository. Do not clone full history. Derive repository_url from sourceUrl, including repository renames. If sourceCommit is absent, resolve the sourceUrl ref once. Set source_commit to that actual commit. Run these commands in one shell call: > > ```sh > git init --quiet "$temporary_dir" > git -C "$temporary_dir" fetch --quiet --depth=1 "$repository_url" "$source_commit" > git -C "$temporary_dir" checkout --quiet --detach FETCH_HEAD > ``` > > Read applicable licence declarations and notices at that commit. If copying is not permitted, report the restriction and stop. > 4. Inspect source entries together, then copy the directory containing skillPath into `./skills/caveman-review`. Use the user's path if selected. Keep the original SKILL.md, relative links, scripts, binary assets, and executable modes. Exclude .git metadata. Reject symlinks and paths outside the Skill directory. After checking entries, use cp -a where available. A regular source directory needs no custom copy script. Do not save this page wrapper as SKILL.md. > Preserve author credit, notices, and applicable licence files from repository or parent directories. Add PROVENANCE.md with the Skill page, source URL, actual commit, original path, and licence. Retain any existing PROVENANCE.md and record new provenance separately. Batch source inspection, copying, and provenance work where practical. > 5. In the project root, run `skilld install ./skills/caveman-review --mode copy --plain`. If skilld is unavailable, use `npx skilld install ./skills/caveman-review --mode copy --plain`. This known command needs no help lookup. Install does not support --json. Use detected Agent targets, or add --agent for the targets the user selected. Install the local path, never the upstream selector. If installation fails, preserve the local copy and report the exact failure. > 6. Confirm the local lockfile source and installed Agent copies once. Report the local path, actual commit, and Agent targets. After edits, reinstall the same local path. Upstream updates must not replace it. Do not publish or push unless the user asks. Write code review comments terse and actionable. One line per finding. Location, problem, fix. No throat-clearing. ## Rules **Format:** `L: . .` — or `:L: ...` 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.` ❌ "It looks like this function is doing a lot of things and might benefit from being broken up into smaller functions for readability." ✅ `L88-140: 🔵 nit: 50-line fn does 4 things. Extract validate/normalize/persist.` ❌ "Have you considered what happens if the API returns a 429? I think we should probably handle that case." ✅ `L23: 🟡 risk: no retry on 429. Wrap in withBackoff(3).` ## Auto-Clarity Drop terse mode for: security findings (CVE-class bugs need full explanation + reference), architectural disagreements (need rationale, not just a one-liner), and onboarding contexts where the author is new and needs the "why". In those cases write a normal paragraph, then resume terse for the rest. ## Boundaries Reviews only — does not write the code fix, does not approve/request-changes, does not run linters. Output the comment(s) ready to paste into the PR. "stop caveman-review" or "normal mode": revert to verbose review style.