local-reviews

Discover, parse, and summarize hidden per-file local review JSON files.

1|Updated Mar 17, 2026
One-click install
npx skills add https://github.com/aneveux/claude-garden --skill local-reviews
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: local-reviews
Source: https://github.com/aneveux/claude-garden/tree/main/plugins/thorn/skills/local-reviews
Command: npx skills add https://github.com/aneveux/claude-garden --skill local-reviews

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Local development often leaves review annotations scattered across files as hidden .reviews.json markers. This skill provides a systematic way to discover, parse, and address those reviews to maintain code quality.

Core Features & Use Cases

  • Discover and parse hidden per-file reviews stored as .<source>.reviews.json files.
  • Correlate reviews to their source context, detect staleness against HEAD, and summarize findings.
  • Act on feedback by presenting, addressing, or cleaning up reviews in your project.

Quick Start

Start by instructing the tool to locate all local reviews and summarize them across your project.

Frequently Asked Questions about local-reviews

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

FAQPage Schema
How do I find and manage local code review annotations stored as JSON files?

Scan your project to discover hidden per-file JSON review files (.<source>.reviews.json) and parse their contents to manage local code review annotations systematically across your codebase.

What is the best way to check if local review comments are stale against the current Git HEAD?

Correlate parsed local reviews against your Git HEAD to detect staleness, ensuring review comments match the latest source context and identifying outdated feedback that needs addressing.

How do I generate a summary of local code reviews across a project?

Aggregate parsed per-file JSON review data across your project to generate actionable summaries, presenting all local review findings in a consolidated overview for easier triage.

Can I clean up outdated local review files without losing valid feedback?

Address and clean up local review files after verifying their staleness and source context correlation, preserving valid user data while removing resolved or obsolete review annotations from your codebase.

Does this code review workflow require any external dependencies?

No external dependencies are required; the workflow operates entirely on local JSON review files, parsing and correlating them against your source code without needing additional plugins or external services.

Why are my local review comments not correlating to the correct source context?

Review comments stored in hidden per-file JSON files may lose their source context correlation if the underlying code has changed since the review was created, triggering a staleness check failure against HEAD.