Agent skill · data analytics · sickn33
analyze-project
Forensic root cause analyzer for Antigravity sessions. Classifies scope deltas, rework patterns, root causes, hotspots, and auto-improves prompts/health.
Why this skill is useful
Adds a comprehensive root cause analysis framework with specific methodologies and evidence-based recommendations that enhance AI's diagnostic capabilities.
What it needs
About 7k tokens when loaded. Last updated 2026-08-07. 44,571 stars on the source repository.
What this skill does
/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 agent error from repo friction Every diagnosis must include evidence and confidence Confidence levels: High = direct artifact/timestamp evidence Medium = multiple supporting signals Low = plausible inference, not directly proven Evidence precedence: artifact contents > timestamps > metadata summaries > inference If evidence is weak, say so --- Step 0.5: Session Intent Classification Classify the primary session intent from objective + artifacts: DELIVERY DEBUGGING REFACTOR RESEARCH EXPLORATION AUDITANALYSIS Record: sessionintent sessionintentconfidence Use intent to contextualize severity and rework shape. Do not judge exploratory or research sessions by the same standards as narrow delivery sessions. --- Step 1: Discover Conversations 1. Read available conversation summaries from system context 2. …
How to use it
Reference it in AdaL, Claude Code, Cursor or any coding agent — nothing to install:
@skills sickn33/analyze-project