skills.rest
mataanin
mataaninCOMMUNITY
Explore all skills by this author →
GitHub

review-stats

Analyze review-analytics.json with jq to generate cross-tool analytics reports.

1|Updated Mar 11, 2026
Search Tags:#analytics#analyze#reviews#cross-tool#agreement#token-usage
One-click install
npx skills add https://github.com/mataanin/multi-llm --skill review-stats-mataanin
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: review-stats
Source: https://github.com/mataanin/multi-llm/tree/main/skills/review-stats
Command: npx skills add https://github.com/mataanin/multi-llm --skill review-stats-mataanin

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Consolidates scattered review results from multiple tooling runs into a single, easy-to-read analytics report.

Core Features & Use Cases

  • Cross-tool aggregation: Correlates findings, agreements, and actions across all review tools.
  • Deep analytics: Produces totals, averages, tool-run rates, and token usage trends.
  • Use Case: Product teams can identify which tools consistently flag issues and where disagreements occur to prioritize fixes.

Quick Start

Load review-analytics.json and run the analyzer to generate the report.

Frequently Asked Questions about review-stats

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

FAQPage Schema
How do I aggregate review analytics across multiple LLM tools?▼

To aggregate review analytics across multiple LLM tools, load a review-analytics.json file and run the analyzer. It computes totals, averages, agreement, token usage, and trends to consolidate scattered results into a single report.

What is the best way to analyze token usage trends from code and PR reviews?▼

Analyzing token usage trends from code and PR reviews requires consolidating outputs into a review-analytics.json file. The analyzer processes this data using jq to compute token usage trends and tool-run rates across all tools.

Can I measure agreement and disagreements between different code review tools?▼

Yes, you can measure agreement between different code review tools. The analyzer correlates findings and actions across all tools, producing a report that highlights where disagreements occur to help product teams prioritize fixes.

Does the cross-tool review analyzer require a specific input format?▼

Yes, the cross-tool review analyzer requires a review-analytics.json file as input. It uses jq to dynamically derive tool lists and compute metrics like averages and agreement rates from this structured JSON data.

How do I generate a cross-tool review analytics report for plan reviews?▼

To generate a cross-tool review analytics report for plan reviews, load your review-analytics.json file and run the analyzer. It dynamically derives tool lists and calculates metrics for plan, code, and PR reviews in a single pass.

Related Skills

Explore More Data & Analytics Skills→
xberg-ioxberg-io
26

tool-calling

Define LLM functions and manage tool calls for structured JSON outputs.

Official
Intermediate
aaronjmarsaaronjmars
17

cost-report

Summarize API token usage and costs from CSV logs into detailed reports.

Community
Intermediate
liangdabiaoliangdabiao
42

tariff-calculator-amazon

Calculate import tariffs and landed costs for Amazon sellers using Python scripts.

Community
Advanced
FriendlyInternetFriendlyInternet
10

test-review

Propose and review test cases before code implementation.

Official
Intermediate