skills.rest
serejaris
serejarisCOMMUNITY
Explore all skills by this author →
GitHub

cc-analytics

Analyze Claude Code history and Git data into weekly HTML reports.

215|26|Updated Dec 15, 2025
Search Tags:#git#analytics#claude-code#analyze#html-report#history.jsonl
One-click install
npx skills add https://github.com/serejaris/ris-claude-code --skill cc-analytics
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: cc-analytics
Source: https://github.com/serejaris/ris-claude-code/tree/main/skills/cc-analytics
Command: npx skills add https://github.com/serejaris/ris-claude-code --skill cc-analytics

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Claude Code usage across projects is often scattered and hard to summarize. This skill automatically compiles activity data into a single HTML report, helping you understand prompts, project activity, and commits over a chosen period.

Core Features & Use Cases

  • Usage analytics: aggregate prompts, sessions, and activity per project from ~/.claude/history.jsonl.
  • Git integration: pull remote URLs and per-project commit counts to contextualize activity.
  • Single HTML output: generate a terminal-style HTML report for easy sharing and archiving.
  • Use Case: a team lead runs weekly reports to monitor Claude Code adoption and project engagement.

Quick Start

  • Run the Python script included in this skill to generate the report from your local Claude Code history. The script reads history data from ~/.claude/history.jsonl and outputs a single HTML file (default: ~/claude-analytics.html).

Frequently Asked Questions about cc-analytics

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

FAQPage Schema
How do I generate a weekly analytics report for Claude Code usage across multiple repositories?▼

Claude Code usage analytics aggregates prompt and session activity from ~/.claude/history.jsonl alongside local Git commit counts, producing a single terminal-style HTML report that summarizes your weekly project engagement.

What data sources are needed to analyze Claude Code prompts and session history?▼

Analyzing Claude Code history requires the ~/.claude/history.jsonl file for prompt records and local Git repository access to pull remote URLs and per-project commit counts for the report.

Can I use this analytics tool to track Claude Code adoption for my team?▼

Yes, team leads can track Claude Code adoption by running weekly reports that compile prompt activity and Git commits across multiple repositories into a shareable HTML file for monitoring team engagement.

Does the Claude Code analytics report integrate Git commit information?▼

Yes, the report integrates Git information by pulling remote URLs and counting per-project commits to contextualize prompt and session activity within the generated HTML output.

What format is the Claude Code usage analytics report output in?▼

The analytics report is output as a single HTML file featuring a terminal-like aesthetic, defaulting to ~/claude-analytics.html, making it easy to share and archive.

Related Skills

Explore More Data & Analytics Skills→
miloswrathmiloswrath

speckit-git-remote

Extract the Git remote URL and parse owner and repository name.

Community
Basic
GrassHopper42GrassHopper42

gstack-openclaw-retro

Generate weekly engineering retrospective reports from git commit history and code quality metrics.

Community
Advanced
kivo360kivo360
1

moai-change-logger

Track and audit project changes across files, code, and repository history.

Community
Advanced
AJBcodingAJBcoding
4

d3-viz

Create custom interactive D3.js visualizations with data binding and responsive sizing.

Community
Intermediate