Caveman Review

>.

You say
Buy it · $39 Read it before you buy $39 Written by JuliusBrussee · unverified publisher
Context cost
975 tokensestimated from the bundle, loaded when it triggers
Bundle
2 files · 3.9 kBtext throughout, nothing executable
Licence
MITpaid listing
Last change
no release on file
Servers it uses
Noneruns standalone

What it does

Ultra-compressed code review comments. Cuts noise from PR feedback while preserving the actionable signal. Each comment is one line: location, problem, fix. Use when user says "review this PR", "code review", "review the diff", "/review", or invokes /caveman-review. Auto-triggers when reviewing pull requests.

Installed, it changes the agent in these ways.

What this skill changes about the agent is not written down here yet. The listing was collected from its source, and the description is in its own SKILL.md.

Workflow

Runs a procedure end to end.

collaboration

The skill itself

This is the whole product. A skill is instructions the model reads, so there is nothing behind the listing you cannot see first — the front matter loads with every session, and the body below it loads when the skill triggers.

SKILL.md2.7 kB · 55 lines
--- name: caveman-review description: > Ultra-compressed code review comments. Cuts noise from PR feedback while preserving the actionable signal. Each comment is one line: location, problem, fix. Use when user says "review this PR", "code review", "review the diff", "/review", or invokes /caveman-review. Auto-triggers when reviewing pull requests. ---
10Write code review comments terse and actionable. One line per finding. Location, problem, fix. No throat-clearing.
11
12## Rules
13
14**Format:** L<line>: <problem>. <fix>. — or <file>:L<line>: ... when reviewing multi-file diffs.
15
16**Severity prefix (optional, when mixed):**
17- 🔴 bug: — broken behavior, will cause incident
18- 🟡 risk: — works but fragile (race, missing null check, swallowed error)
19- 🔵 nit: — style, naming, micro-optim. Author can ignore
20- ❓ q: — genuine question, not a suggestion
21
22**Drop:**
23- "I noticed that...", "It seems like...", "You might want to consider..."
24- "This is just a suggestion but..." — use nit: instead
25- "Great work!", "Looks good overall but..." — say it once at the top, not per comment
26- Restating what the line does — the reviewer can read the diff
27- Hedging ("perhaps", "maybe", "I think") — if unsure use q:
28
29**Keep:**
30- Exact line numbers
31- Exact symbol/function/variable names in backticks
32- Concrete fix, not "consider refactoring this"
33- The *why* if the fix isn't obvious from the problem statement
34
35## Examples
36
37❌ "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."
38
39L42: 🔴 bug: user can be null after .find(). Add guard before .email.
40
41❌ "It looks like this function is doing a lot of things and might benefit from being broken up into smaller functions for readability."
42
43L88-140: 🔵 nit: 50-line fn does 4 things. Extract validate/normalize/persist.
44
45❌ "Have you considered what happens if the API returns a 429? I think we should probably handle that case."
46
47L23: 🟡 risk: no retry on 429. Wrap in withBackoff(3).
48
49## Auto-Clarity
50
51Drop 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.
52
53## Boundaries
54
55Reviews 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.
In the file
SKILL.md432 words
Files2
LicenceMIT
Why you can read it

Nothing in a skill executes. The client loads the text and the model follows it, so a skill can be audited the way a runbook is — by reading it.

What it costs in context

Skills are not billed by the call. They are paid for in context: every token the instructions occupy is a token your code, your diff and your conversation cannot use. Here is what this one takes and when it takes it.

≈90
always loaded
The name and description, so the model knows the skill exists and when to reach for it.
885
on trigger
The instruction body and 1 supporting file, read only when the skill fires.
0.49%
of a 200k window
Ten skills this size would take about 5% of the window before you open a file.
050k100k150k200k context window

975 tokens, estimated from the bundle at four bytes to the token, held for the rest of the session once it triggers. Small enough to keep loaded permanently without thinking about it.

Servers bill, skills cost

A server charges by the month. A skill charges once per session, in context, and then keeps charging it for as long as the session lives.

Before and after

The same question, put to the same model twice: once as it comes, and once with these instructions loaded.

No worked example has been published for this skill yet.

Adoption
Installsnone yet
Ratingno reviews yet

The procedure it runs

The procedure has not been published here. It is in the skill’s own SKILL.md, which its author has not sent to the marketplace yet.

Prose, not code

These steps are written for a model to follow, not executed by a runtime. It can still be told to skip one, and it will say so when it does.

Servers it uses

None. This skill calls no MCP servers at all.

Everything it needs is in the instructions, so it works in a project with nothing connected — the model reads the file and changes how it works with what it can already reach.

It writes no files and reaches no network. All it changes is how the model reasons and writes.

What it asks for
Writes filesno
Network accessno

Read from the allowed-tools line of this skill’s own SKILL.md. A skill grants no permissions of its own — it can only ask for tools your client already has.

What it will not do

Every skill is narrow, and the useful ones say where they stop. These are the jobs this one is the wrong tool for.

What this skill is not for has not been published here. Nothing is implied by that: it is a section the author has not filled in.

What is in the bundle

2 files, 3.9 kB on disk. A bundle is text throughout: the instructions the model reads, plus the templates it fills in.

  • README.md1.2 kB
  • SKILL.md2.7 kB
What is not in it

No dependencies and nothing executable: a skill is text the agent reads, so the bundle is 2 files you can review in full before installing. The MIT licence covers the templates and examples as well as the instructions.

Install

Installing copies the bundle into your project. Nothing runs at install time — the files sit on disk until the model reads them.

$39 once
Caveman Review · MIT · JuliusBrussee
one-time
Price$39 once
LicenceMIT — the author’s, unchanged by this purchase
Paid throughStripe, once, on the card you add at the checkout
Keeps workingfor good — the files are yours once they are on disk
Updatesevery update its author ships, delivered through this account

You can read the whole bundle before paying — the SKILL.md above is the product, not a preview of it. What the money buys is the delivery: the folder packaged and handed to your machine by key, every update its author ships, and our support if it does not do what this listing says. The terms of use are MIT, set by the author and unchanged by buying it here.

Payment runs through Stripe, on a page like this one rather than a redirect. Once there is an account it joins the same mcprush invoice as everything else you run, so there is never a second card to enter.

Which clients pick it up on their own

A skill is a folder of text. A client with a skills folder reads it without being told; everywhere else the same text works, it is just handed to the model rather than found.

Claude Code.claude/skills/
Claude Desktop
ChatGPT
Cursor.cursor/skills/
VS Code.github/skills/
Codex CLI.agents/skills/
Gemini CLI.gemini/skills/
Grok.grok/skills/
Zed.agents/skills/
Windsurf.windsurf/skills/
Agent SDK.claude/skills/
HTTP / API
This release
Versionnot versioned
Publishedno release date on file
Price$39
Referencejuliusbrussee/caveman-review

Versions

Its author publishes no version number, so there is nothing here to pin to: what you install is the folder as it stands today. Instructions change more often than APIs do — a skill can be rewritten entirely without anything it depends on moving.

v
  • No earlier releases have been published to the marketplace.
Pinning

Nothing to pin to: this skill carries no version number of its own. What you install is what the folder holds on the day you install it.

Reviews

no reviews yet · no installs yet

Nobody has reviewed this skill yet. The rating is the mean of the reviews written here, so there is none until somebody writes the first.

Who can post

Only accounts that have had the skill installed for fourteen days, so a review is written after living with it rather than after reading it. Publishers may reply once.

Who wrote it

JU
JuliusBrussee

Publishes on mcprush.

0 servers listed3 skills listednot claimed
Profile
Publisher
Servers0