skills.rest
Tyler-R-Kendrick
Tyler-R-KendrickCOMMUNITY
Explore all skills by this author →
GitHub

caveman-review

Generate concise, severity-tagged code review comments for pull requests.

1|Updated Jul 12, 2026
Search Tags:#static analysis#code review#pull request#software quality#developer productivity
One-click install
npx skills add https://github.com/Tyler-R-Kendrick/slm-training --skill caveman-review-tyler-r-kendrick
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: caveman-review
Source: https://github.com/Tyler-R-Kendrick/slm-training/tree/main/.agents/skills/caveman-review
Command: npx skills add https://github.com/Tyler-R-Kendrick/slm-training --skill caveman-review-tyler-r-kendrick

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This Skill eliminates the noise and fluff often found in code reviews, providing developers with immediate, actionable feedback that highlights bugs and risks without the need for polite filler.

Core Features & Use Cases

  • Terse Formatting: Enforces a strict one-line format per finding, including location, problem, and fix.
  • Severity Tagging: Uses clear emoji-based prefixes to distinguish between critical bugs, risks, nits, and questions.
  • Context-Aware: Automatically switches to a more detailed explanation for security-critical findings or architectural disagreements while maintaining brevity for standard code improvements.

Quick Start

Invoke the caveman-review skill by asking the assistant to review the current pull request diff using the caveman style.

Frequently Asked Questions about caveman-review

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

FAQPage Schema
What is ultra-compressed code review and how does it work?▼

Ultra-compressed code review provides rapid, high-signal feedback on code diffs by enforcing a strict one-line format per finding, using severity-prefixed emoji syntax to distinguish critical bugs, risks, nits, and questions.

Can I use this for detailed static analysis of security-critical findings?▼

Yes, for security-critical findings or architectural complexity, the review automatically switches to a more detailed explanation while maintaining brevity for standard code improvements.

Does the code review output include severity tagging for bugs and risks?▼

Yes, the code review output includes clear emoji-based severity prefixes to distinguish between critical bugs, risks, nits, and questions for immediate triage.

What is the best way to filter noise and fluff from automated PR comments?▼

The best way to filter noise is to enforce a terse formatting rule that strips polite filler, requiring a strict one-line format per finding that includes the location, problem, and fix.

Are there limitations to using one-line code review formats for complex diffs?▼

Yes, while the one-line format is enforced for brevity, the approach automatically expands detailed explanations when findings involve security vulnerabilities or architectural disagreements to ensure necessary context is not lost.

Related Skills

Explore More Software Engineering Skills→
jchildreejchildree
1

caveman-review

Generate single-line code review comments with severity levels.

Community
Intermediate
gsarmaonlinegsarmaonline

review-comments

Analyze pull request review comments and resolve failing GitHub Actions checks.

Community
Advanced
samChang72samChang72
1

code-review

Automates code reviews to detect bugs, style violations, and performance issues in submissions via static analysis tools.

Community
Intermediate
achmfachmf

caveman-review

Parse pull request diffs and output one-line bug, risk, and style suggestions.

Community
Basic