skills.rest
tomw200082-collab
tomw200082-collabCOMMUNITY
Explore all skills by this author →
GitHub

caveman-review

Generates one-line code review comments with location, severity, problem, and fix.

Updated May 8, 2026
Search Tags:#code review#feedback#pull request#diff#severity#terse#review comments
One-click install
npx skills add https://github.com/tomw200082-collab/gt-factory-os-production-brain --skill caveman-review-tomw200082-collab
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: caveman-review
Source: https://github.com/tomw200082-collab/gt-factory-os-production-brain/tree/main/.claude/skills/caveman-review
Command: npx skills add https://github.com/tomw200082-collab/gt-factory-os-production-brain --skill caveman-review-tomw200082-collab

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve? PR review feedback is often buried in hedging, filler phrases, and restated diff content, forcing authors to dig for the actionable point. This Skill compresses every finding into a single line so reviewers communicate faster and authors act immediately. ## Core Features & Use Cases - One-line findings: Each comment follows the format L<line>: <severity> <problem>. <fix>. with exact line numbers and backticked symbols. - Severity tagging: Uses 🔴 bug, 🟡 risk, 🔵 nit, and ❓ question prefixes to signal priority at a glance. - Auto-clarity mode: Automatically switches to full paragraphs for CVE-class security findings, architectural disagreements, and onboarding contexts, then resumes terse output. - Use Case: Paste a multi-file pull request diff and receive paste-ready review comments like L42: 🔴 bug: user can be null after .find(). Add guard before .email. ## Quick Start Ask the assistant to review this PR diff using caveman-review and output one-line comments with severity tags.

Frequently Asked Questions about caveman-review

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

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

Use the format L<line>: <severity> <problem>. <fix>. with one line per finding. Include exact line numbers, backticked symbol names, and a concrete fix while dropping phrases like "I noticed that" or "you might want to consider".

What severity levels should code review comments use?▼

This Skill uses four levels: 🔴 bug for broken behavior, 🟡 risk for fragile code like missing null checks, 🔵 nit for style issues the author can ignore, and ❓ question for genuine inquiries rather than disguised suggestions.

When should code review feedback not be terse?▼

Terse mode should be dropped for CVE-class security findings needing full explanation and references, architectural disagreements requiring rationale, and onboarding contexts where a new author needs the reasoning behind a change.

Can this tool approve or request changes on a pull request?▼

No. It only outputs review comments ready to paste into the PR. It does not approve, request changes, write code fixes, or run linters.

How do I turn off terse review mode?▼

Say "stop caveman-review" or "normal mode" to revert to verbose review style. The Skill also auto-expands individual findings when the context demands a full explanation.

Related Skills

Explore More Software Engineering Skills→
DDTullyDDTully

caveman-review

Generate one-line code review findings with location, problem, and fix.

Community
Intermediate
langfuselangfuse
34.0k

linear-bug-triage

Deduplicate measured bug evidence and create or comment Linear triage issues.

Official
Intermediate
Devsoul2026Devsoul2026
150

requesting-code-review

Automate pre-commit verification with static analysis, tests, and lint checks.

Community
Advanced
stacklokstacklok
2.0k

pr-inline-review

Submit inline review comments and code suggestions to GitHub Pull Requests via gh CLI.

Official
Intermediate