Caveman review
Skill yigityildiz0/universal-ai-skill-library/skills/common/caveman-review
Produce concise code-review findings with exact locations, evidence, impact, and a concrete fix while retaining necessary rationale for high-risk issues. Use only when the user explicitly invokes $caveman-review or asks for a Caveman-style review. Do not trigger for ordinary review requests.From its SKILL.md
npx -y skills add yigityildiz0/universal-ai-skill-library --skill caveman-reviewAssembled from the repository path, not quoted from the project. Check it against their README if it does not work.
3 things to look at
- 27 days oldThe repository was created 27 days ago. New is not bad, but a brand new repository carrying a familiar-sounding name is the shape a typosquat arrives in, and there has been no time for anyone else to find a problem with it.
- no licenseNo license file was found in the repository. Code published without one is not open source by default, so using it at work is a question for whoever answers licensing questions where you are.
- 1 stars1 stars. Stars are a popularity signal and not a quality one, but at this level it is likely that nobody has read this closely except its author, and you would be relying on your own review.
SKILL.md
1.5 KB, 268 tokens by cl100k_base, as published. Nobody here has run it
Caveman Review
Review first; compress only the presentation. Do not change code, post comments, approve, or request changes unless the user separately authorizes that action.
Workflow
- Inspect the full relevant diff and surrounding code.
- Verify each finding is introduced or exposed by the change.
- Rank findings by impact and confidence.
- Omit praise, narration, and speculative nits.
Finding format
Use:
[P1] path/to/file:L42 - Null user reaches email access. Guard before dereference.
P0: immediate, broad catastrophic impact.P1: high-priority correctness, security, or data-loss defect.P2: normal actionable defect.P3: low-priority but real issue.
Include exact file, tight line range, failing condition, consequence, and actionable fix. If location is unavailable, name the exact symbol.
Clarity overrides
Use a normal paragraph when a one-line comment would hide:
- exploitability, privacy impact, or a security boundary;
- migration, compatibility, or data-loss consequences;
- architectural tradeoffs or uncertainty;
- reproduction steps needed to establish the defect.
Lead with findings. If none exist, say so and name any untested residual risk.
What ships with it
Read from the repository
Just SKILL.md. No reference files, no scripts.