caveman-review
The caveman-review skill generates concise, one-line code review comments for pull requests. It enforces a strict format of location, problem, and fix to reduce noise in feedback.
Is caveman-review safe to install?
Safe to install: our audit of caveman-review's source files found 0 shell commands, 0 external URLs, no file writes (none risk). Every command and URL listed appears verbatim in the skill's source. The skill performs text processing and formatting based on provided code diffs. It does not execute shell commands, access the network, or modify local files.
How we audit skills: our security review methodology.
Who is this skill for?
Developers and reviewers who prefer terse, actionable feedback on code changes.
What can you do with it?
- Generating one-line code review comments for pull requests.
- Categorizing feedback by severity using prefixes like bug, risk, nit, and q.
- Providing specific line numbers and concrete fix suggestions in code reviews.
How good is this skill?
Quality score: 5/10. The skill documentation is clear, provides specific formatting rules, and includes helpful examples for users.
What does the skill file contain?
Write code review comments terse and actionable. One line per finding. Location, problem, fix. No throat-clearing. ## Rules **Format:** `L<line>: <problem>. <fix>.` ā or `<file>:L<line>: ...` when reviewing multi-file diffs. **Severity prefix (optional, when mixed):** - `š“ bug:` ā broken behavior, will cause incident - `š” risk:` ā works but fragile (race, missing null check, swallowed error) - `šµ nit:` ā style, naming, micro-optim. Author can ignore - `ā q:` ā genuine question, not a suggestion **Drop:** - "I noticed that...", "It seems like...", "You might want to consider..." - "This ...
Frequently asked questions
How does the skill format comments?
It uses the format L<line>: <problem>. <fix>. or <file>:L<line>: <problem>. <fix>.
Can the skill automatically approve pull requests?
No, the skill only generates text comments and does not perform actions like approving or requesting changes.
Does the skill always use the terse format?
No, it reverts to verbose mode for security findings, architectural disagreements, or when the user requests normal mode.
Related skills
agentspace
324.0KDevelopers and AI agent users who need to share, monitor, or collaborate on agent-generated files and workspaces in real-time
Agentspace provides a mechanism to share local agent files, logs, and artifacts via a live browser-accessible URL. It enables remote viewing, commenting, and editing of specified local paths through the ascli command-line tool.
lark-workflow-meeting-summary
219.7KUsers who need to summarize meeting minutes, generate weekly reports, or review meeting history within the Lark ecosystem
The lark-workflow-meeting-summary skill provides a structured workflow for agents to aggregate meeting minutes from Lark VC, generate summaries, and create or update reports in Lark Docs.
caveman-commit
214.4KDevelopers who want to maintain clean, terse, and informative git commit histories
The caveman-commit skill generates concise commit messages following the Conventional Commits specification. It prioritizes the reasoning behind changes over the description of the changes themselves.
notion-api
52.2KDevelopers and AI agents requiring programmatic access to Notion workspaces
This skill provides instructions for interacting with the Notion REST API. It enables agents to read, create, update, and delete Notion pages, databases, blocks, and comments using curl and jq.