analyze-project
Use when starting work on an unfamiliar project or needing to understand a codebase - performs comprehensive analysis discovering architecture, patterns, dependencies, testing coverage, and improvement opportunities. Do NOT use on projects you already know well or for targeted questions about specific files - use direct exploration instead for focused queries.
npx skills add majiayu000/claude-skill-registry --skill pop-analyze-project-jrc1883-popkit-claude-2 --agent claude-code
Same command for any agent — swap --agent for codex, cursor, copilot.
Weekly change comes from our own snapshots, not the repository page — it measures attention, not adoption.
# Analyze Project ## Overview Perform deep analysis of a codebase to understand its architecture, patterns, dependencies, and opportunities for improvement. **Core principle:** Understand before changing. Map before navigating. **Trigger:** `/popkit:project analyze` command or when starting work on unfamiliar project ## Arguments | Flag | Description | | ---------------- | --------------------------------------------------------------------------- | | `--json` | Output structured JSON instead of markdown, save to `.claude/analysis.json` | | `--quick` | Quick summary only (5-10 lines) | | `--focus <area>` | Focus analysis: `arch`, `deps`, `quality`, `patterns` | ## Analysis Areas ### 1. Project Structure Directory structure, entry points, file counts by type. ### 2. Technology Stack Package managers, frameworks (Next.js, React, Vue, Express, FastAPI, Rust), databases (Supabase, Prisma, MongoDB, PostgreSQL). ### 3. Architecture Patterns Frontend (component structure, state management, routing), Backend (API design, service layer, database access), Common (error handling, logging, configuration). ### 4. Code Quality Linting config, TypeScript strictness, TODO/FIXME comments. ### 5. Te
- Overview
- Arguments
- Analysis Areas
- 1. Project Structure
- 2. Technology Stack
- 3. Architecture Patterns
- 4. Code Quality
- 5. Testing Coverage
- 6. Dependencies
- 7. CI/CD and DevOps
- Output Format
- Markdown Report
- JSON Output
- Skill/Agent Recommendations
What does the analyze-project skill do?
Use when starting work on an unfamiliar project or needing to understand a codebase - performs comprehensive analysis discovering architecture, patterns, dependencies, testing coverage, and improvement opportunities. Do NOT use on projects you already know well or for targeted questions about specific files - use direct exploration instead for focused queries.
How do I install it?
Run `npx skills add majiayu000/claude-skill-registry --skill pop-analyze-project-jrc1883-popkit-claude-2 --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.