skills.rest
mifunedev
mifunedevOFFICIAL
Explore all skills by this author →
Website𝕏@mifunedevGitHub

caveman-review

Generate compact caveman-style PR review notes with severity tags and file:line citations.

28|3|Updated Mar 27, 2026
Search Tags:#github#generate#code-review#pr-review#review-notes#caveman-style
One-click install
npx skills add https://github.com/mifunedev/openharness --skill caveman-review-mifunedev
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: caveman-review
Source: https://github.com/mifunedev/openharness/tree/main/.claude/skills/caveman-review
Command: npx skills add https://github.com/mifunedev/openharness --skill caveman-review-mifunedev

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Produces PR review notes in a caveman style: terse, fragmentary, and easy to skim, drastically reducing review time by focusing on actionable findings and avoiding fluff. The format enforces one finding per line, with explicit severity tags and verbatim file:line references to keep traceability intact.

Core Features & Use Cases

  • One finding per line, leading with severity: BLOCK / WARN / NIT.
  • Fragment phrasing with condensed language; cite file:line verbatim for quick context.
  • Useful for fast, consistent code reviews on GitHub, GitLab, or any PR workflow.

Quick Start

Invoke caveman-review on a PR or path to generate concise, line-scoped review notes.

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 code review notes for a GitHub PR?▼

To generate terse PR review notes, process code changes to produce per-file findings with severity tags and verbatim file:line references. This enforces one finding per line for quick skimming.

What is caveman-style PR review and how does it format findings?▼

Caveman-style PR review formats findings as terse, fragmentary phrases on one line each. It applies leading severity tags like BLOCK, WARN, or NIT alongside verbatim file:line citations for traceability.

Can I use this PR review format across different repositories and languages?▼

Yes, this PR review format applies across repositories and languages. It generates per-file findings using deterministic formatting, preserving code snippets and file:line references regardless of the codebase.

How do I get per-file findings with severity tags for a code change?▼

To get per-file findings with severity tags, invoke the review process on a PR or path. It outputs deterministic, line-scoped notes with leading BLOCK, WARN, or NIT tags and verbatim citations.

Does this code review tool work with GitLab or only GitHub PR workflows?▼

This code review tool works with GitHub, GitLab, or any PR workflow. It generates consistent, line-scoped review notes with severity tags and file:line references across platforms.

Why use fragmentary phrasing instead of full sentences in PR review notes?▼

Fragmentary phrasing in PR review notes drastically reduces review time by focusing on actionable findings and avoiding fluff. It enforces condensed language with one finding per line for easy skimming.

Related Skills

Explore More Software Engineering Skills→
nillenille

Code Review

Review code diffs for correctness, security, and conventions.

Community
Advanced
CommunityToolkitCommunityToolkit
619

pr-review-response

Generate replies to GitHub PR review comment threads via the GitHub API.

Official
Intermediate
albertoiruruetaalbertoirurueta

dotnet-code-quality

Run Roslyn analyzers on .NET/C# projects and generate SARIF logs.

Community
Advanced
fmflurryfmflurry
171

caveman-review

Generate terse one-line code review findings from pull request diffs.

Community
Intermediate