skills.rest
darkmatter
darkmatterOFFICIAL
Explore all skills by this author →
Website𝕏@_darkmatterlabsGitHub

caveman-review

Generates terse one-line code review comments for pull requests with exact line references and severity markers.

1|Updated Apr 27, 2026
Search Tags:#software engineering#code review#pull requests#diff review#pr comments#actionable feedback
One-click install
npx skills add https://github.com/darkmatter/skills --skill caveman-review-darkmatter
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: caveman-review
Source: https://github.com/darkmatter/skills/tree/main/docs/00-inbox/skills/caveman-review
Command: npx skills add https://github.com/darkmatter/skills --skill caveman-review-darkmatter

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

It turns verbose code review feedback into ultra-short, high-signal comments that are fast to scan, easy to paste, and focused on concrete changes.

Core Features & Use Cases

  • One-line review findings: Each comment is reduced to location, problem, and fix so authors can act immediately.
  • Consistent review style: Uses exact line references, optional severity markers, and explicit guidance instead of vague advice.
  • Pull request workflows: Ideal for reviewing diffs, multi-file changes, and quick review prompts where brevity matters more than discussion.

Quick Start

Ask for a caveman-style review of the attached diff and return only one-line comments with exact locations, the problem, and the fix.

Frequently Asked Questions about caveman-review

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I get concise code review comments for a pull request diff?▼

Terse code review comments are generated by reducing verbose feedback into one-line findings with exact line references, the problem, and a concrete fix. This produces high-signal PR comments that are fast to scan and ready to paste.

What is the best way to format actionable feedback for multi-file PR changes?▼

Actionable feedback for multi-file changes is formatted as one-line comments containing exact line locations, optional severity markers, and explicit fix guidance. This approach avoids vague advice and removes hedging or approval language from the review.

Can I use short PR comments without hedging in my engineering workflow?▼

Yes, short PR comments without hedging are generated for engineering workflows. Each comment is strictly limited to location, problem, and fix guidance, ensuring review feedback remains direct and focused on concrete code changes.

How do I write one-line review findings with exact line references?▼

One-line review findings are written by combining an exact line reference, a brief problem statement, and concrete fix guidance. Optional severity markers can be added to indicate priority without expanding the comment into a discussion.

Does this code review approach work for quick diff reviews instead of full discussions?▼

Yes, this approach is designed for quick diff reviews where brevity matters more than discussion. It outputs one-line comments focused on actionable changes, making it ideal for rapid multi-file review prompts.

Related Skills

Explore More Software Engineering Skills→
g-lokg-lok
1

caveman-review

Generate one-line code-review comments from pull request diffs.

Community
Intermediate
mujtaba3Bmujtaba3B
2

address-pr-feedback

Address pull request review comments one by one into code fixes.

Community
Advanced
warpdotdevwarpdotdev
292

security-review-pr

Identify security concerns in pull request diffs and merge findings into review.json.

Official
Advanced
jdonohoojdonohoo
15

nyquil

Rewrites Dart functions into concise one-line implementations with minimal comments.

Community
Basic