Agent skill · Code Review & Quality

analyze-project

Forensic root cause analyzer for Antigravity sessions. Classifies scope deltas, rework patterns, root causes, hotspots, and auto-improves prompts/health.

majiayu000github.com/majiayu000GitHub ↗
claude-codeMIT
Install
npx skills add majiayu000/claude-skill-registry --skill analyze-project --agent claude-code

Same command for any agent — swap --agent for codex, cursor, copilot.

Facts
Files in the skill folder: 2
SKILL.md size: 12 KB
Bundled scripts: none
Version: 1.0
Path: skills/analysis/analyze-project/SKILL.md
Open the folder on GitHub →
Where it comes from
Stars: 534
Language: HTML

Weekly change comes from our own snapshots, not the repository page — it measures attention, not adoption.

From the SKILL.md

# /analyze-project — Root Cause Analyst Workflow Analyze AI-assisted coding sessions in `~/.gemini/antigravity/brain/` and produce a report that explains not just **what happened**, but **why it happened**, **who/what caused it**, and **what should change next time**. ## Goal For each session, determine: 1. What changed from the initial ask to the final executed work 2. Whether the main cause was: - user/spec - agent - repo/codebase - validation/testing - legitimate task complexity 3. Whether the opening prompt was sufficient 4. Which files/subsystems repeatedly correlate with struggle 5. What changes would most improve future sessions ## When to Use - You need a postmortem on AI-assisted coding sessions, especially when scope drift or repeated rework occurred. - You want root-cause analysis that separates user/spec issues from agent mistakes, repo friction, or validation gaps. - You need evidence-backed recommendations for improving future prompts, repo health, or delivery workflows. ## Global Rules - Treat `.resolved.N` counts as **iteration signals**, not proof of failure - Separate **human-added scope**, **necessary discovered scope**, and **agent-introduced scope** - Separate

What's inside
Steps it walks through
  1. Goal
  2. When to Use
  3. Global Rules
  4. Step 0.5: Session Intent Classification
  5. Step 1: Discover Conversations
  6. Step 2: Extract Session Evidence
  7. Core artifacts
  8. Metadata
  9. Version snapshots
  10. Additional signals
  11. Step 3: Prompt Sufficiency
  12. Step 4: Scope Change Classification
  13. Step 5: Rework Shape
  14. Step 6: Root Cause Analysis
Ships with 1 file
  • metadata.json
More from claude-skill-registry
All skills →
About this skill
What does the analyze-project skill do?

Forensic root cause analyzer for Antigravity sessions. Classifies scope deltas, rework patterns, root causes, hotspots, and auto-improves prompts/health.

How do I install it?

Run `npx skills add majiayu000/claude-skill-registry --skill analyze-project --agent claude-code` — it drops the skill into your project so the agent can pick it up. Swap the --agent value for codex, cursor or copilot if you use one of those.

Where does this skill come from?

From majiayu000/claude-skill-registry, a repository with 534 stars. We read it straight from the repository tree rather than a submitted listing, so what you see here is what is actually published.

Is a popular skill a good skill?

Not necessarily. Stars measure attention, not adoption — a repository can trend for a week and be abandoned. That is why we show the weekly change from our own snapshots next to the total, instead of a single flattering number.

Keep going