skills.rest
Chris-Maskey
Chris-MaskeyCOMMUNITY
Explore all skills by this author →
WebsiteGitHub

caveman-review

Compress pull request review findings into one-line comments with location, problem, and fix.

Updated Apr 17, 2026
Search Tags:#code review#pull request#github#diff#terse#review automation
One-click install
npx skills add https://github.com/Chris-Maskey/opencode-config --skill caveman-review-chris-maskey
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: caveman-review
Source: https://github.com/Chris-Maskey/opencode-config/tree/main/skills/caveman-review
Command: npx skills add https://github.com/Chris-Maskey/opencode-config --skill caveman-review-chris-maskey

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Long, noisy pull request reviews dilute actionable feedback and slow down remediation. Caveman-review compresses review findings into terse, copy-pasteable comments that surface the fixable signal immediately.

Core Features & Use Cases

  • Terse one-line findings: Each comment is a single line containing location, problem, and fix to reduce cognitive load.
  • Structured format & severity: Supports exact line/file references and optional severity prefixes (bug, risk, nit, q).
  • Context-aware exceptions: Expands into full explanations for security, architectural disagreements, or onboarding contexts.
  • Use Cases: Rapid triage of large diffs, reviewer automation for CI bots, and focused feedback during code review rounds.

Quick Start

Ask the assistant to "review this PR" or paste a diff and request caveman-review style one-line comments.

Frequently Asked Questions about caveman-review

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

FAQPage Schema
How do I generate terse one-line code review comments for a pull request?▼

To generate terse one-line code review comments, trigger the review automation by asking the assistant to review the PR or pasting a diff. It produces ultra-compressed comments summarizing exact file locations, problems, and fixes to reduce cognitive load during triage.

What is the best way to automate PR reviews for large diffs without losing actionable feedback?▼

Automating PR reviews for large diffs is best handled by compressing findings into single-line comments with structured severity prefixes like bug, risk, or nit. This surfaces fixable signals immediately and speeds up remediation without diluting the review.

Can I use structured severity prefixes in automated GitHub code review comments?▼

Yes, you can use structured severity prefixes in GitHub code review comments. The format supports prefixes like bug, risk, nit, and q, enforcing exact line and file references to keep automated feedback organized and actionable.

Does the one-line review format support full explanations for security findings?▼

The one-line review format supports full explanations for security findings. It applies context-aware exceptions to expand into detailed explanations when encountering security issues, architectural disagreements, or onboarding contexts.

How do I apply single-line review formatting rules to multi-file diffs?▼

To apply single-line review formatting rules to multi-file diffs, paste the diff and request the review style. The automation processes single-file or multi-file diffs, enforcing exact line references and terse formatting across all findings.

Related Skills

Explore More Software Engineering Skills→
sltc-devsltc-dev

link-diff

Fetch code diffs from GitHub and GitLab pull request and commit URLs.

Community
Basic
MoonLadderStudiosMoonLadderStudios
12

pr-resolver

Orchestrate GitHub pull request resolution with bounded retries and structured artifacts.

Official
Advanced
eliottbusinesseliottbusiness

requesting-code-review

Automate pre-commit code review with static analysis and security scanning.

Community
Advanced
rvdbreemenrvdbreemen
199

caveman-review

Generate one-line code review comments with line numbers and fixes.

Community
Basic