Automated summary
Provides deep analysis of project codebases including lines of code, dependencies, architecture, and git history for documentation and portfolio generation.
Strengths
- Comprehensive code statistics by language
- Git analytics with contributor insights
- Dependency and security vulnerability analysis
- Architecture detection with framework and pattern identification
Limitations
- Requires external tools like tokei or cloc to be installed
- May not detect custom or less common frameworks
- Historic git analysis depends on commit message quality
Use when you need a detailed project profile for documentation, onboarding, or portfolio showcasing.
Do not use for real-time monitoring or when you need live changes tracking.
Security analysis
SafeThe skill uses only read-only utilities (tokei, cloc, tree) and Git commands for analysis (git log, etc.). Although the allowed-tool 'Bash(git:*)' permits any Git operation, the skill's intent and instructions are strictly non-destructive and do not exfiltrate data or disable safety features.
No concerns found
How this analysis is madeExamples
Analyze the current project and give me a summary./analyze --full --output report.mdAnalyze the project located at ~/projects/my-appname: project-analyzer description: | Deep analysis of project codebases - LOC, dependencies, architecture, git history. Generates comprehensive project profiles for documentation and portfolio.
Triggers: "analyze project", "project stats", "codebase analysis", "/analyze" version: 1.0.0 author: Claude Code allowed-tools:
- Bash(git:*)
- Bash(tokei:*)
- Bash(cloc:*)
- Bash(tree:*)
- Read
- Glob
- Grep
Project Analyzer
Deep analysis of project codebases for documentation and portfolio generation.
Capabilities
Code Statistics
- Lines of code by language
- File count and distribution
- Comment density
- Code complexity metrics
Dependency Analysis
- Direct dependencies
- Dev dependencies
- Outdated packages
- Security vulnerabilities
Git Analytics
- Total commits
- Contributors
- Activity timeline
- Commit frequency patterns
Architecture Detection
- Framework identification
- Design patterns used
- Module structure
- API surface
Usage
# Analyze current project
/analyze
# Analyze specific project
/analyze --project ~/projects/my-app
# Generate full report
/analyze --full --output report.md
Output Format
project:
name: my-project
path: /path/to/project
created: 2025-10-15
last_activity: 2026-01-19
code:
total_lines: 45230
languages:
Python: 28450
TypeScript: 12340
YAML: 2100
Markdown: 2340
files: 234
git:
total_commits: 847
contributors: 3
first_commit: 2025-10-15
last_commit: 2026-01-19
commit_frequency: 12/week
stack:
frameworks: [FastAPI, Next.js, LangChain]
databases: [PostgreSQL, Qdrant]
infrastructure: [Docker, Vercel]
health:
test_coverage: 78%
doc_coverage: 65%
dependency_freshness: 89%
Integration
Feeds into:
knowledge-forgefor Obsidian notesportfolio-forgefor static site generation
Requirements
Install analysis tools:
# Code statistics (choose one)
brew install tokei # Fast, Rust-based
brew install cloc # Comprehensive, Perl-based
# For tree visualization
brew install tree
From the file to a first result
The download contains exactly the content displayed on this page. This copy may differ from the latest version in the source repository.
View the source and supporting filesThis download contains SKILL.md only. Any scripts, references, templates and dependencies are not included. Get the required files from the source, preserving their directory structure, before continuing.
1. Download the file
Download SKILL.mdFrom the root of a test project, save the file as .skill-downloads/project-analyzer-mmbizjas/SKILL.md, or use the command below. This folder is for inspecting the skill before installation.
Command for macOS/Linux or WSL: requires a POSIX shell and curl. On Windows without WSL, use the download button and create the folder manually.
mkdir -p '.skill-downloads/project-analyzer-mmbizjas' && curl --fail --show-error --location 'https://skills-guides.com/api/skills/project-analyzer-mmbizjas/download' --output '.skill-downloads/project-analyzer-mmbizjas/SKILL.md.part' && mv '.skill-downloads/project-analyzer-mmbizjas/SKILL.md.part' '.skill-downloads/project-analyzer-mmbizjas/SKILL.md'2. Check prerequisites
Read SKILL.md before using it. If it references scripts or external services, inspect them and prepare the required access in your test environment.
Original excerpt: Requirements
Install analysis tools:
# Code statistics (choose one)
brew install tokei # Fast, Rust-based
brew install cloc # Comprehensive, Perl-based
# For tree visualization
brew install tree
The platforms on this page are catalog indications. The paths below follow tool documentation; they do not prove this skill has been run in those tools. No minimum tool version is confirmed for this listing.
3. Load the skill
After inspection, copy the complete folder into your project using one of the commands below, then open a new tool session. The command stops if a folder with the same name already exists: compare the files before replacing it.
Claude Code
test -f '.skill-downloads/project-analyzer-mmbizjas/SKILL.md' && test -s '.skill-downloads/project-analyzer-mmbizjas/SKILL.md' && mkdir -p '.claude/skills' && test ! -e '.claude/skills/project-analyzer' && cp -R '.skill-downloads/project-analyzer-mmbizjas' '.claude/skills/project-analyzer'OpenSkills
OpenSkills must already be installed. The local install/read procedure is checked with OpenSkills 1.5.0, which requires Node.js ≥ 20.6.0. Catalog slugs are not resolved automatically.
Official OpenSkills installationopenskills install './.skill-downloads/project-analyzer-mmbizjas'openskills read 'project-analyzer-mmbizjas'Reading should display the installed file content and its base directory. It does not run the skill or install its dependencies.
For an agent that reads AGENTS.md, then sync the index. This command changes AGENTS.md: review the diff before using it.
openskills syncManual method or another tool: attach SKILL.md to a conversation, or open it in an agent that can read files. Include any required supporting resources. No universal folder is recognized by every tool.
4. Try a first task
Use a short, synthetic input: an API endpoint, a small document or an interface brief. In a new conversation, attach the file or give the agent its path, then adapt this request:
Read .skill-downloads/project-analyzer-mmbizjas/SKILL.md and apply its instructions to this example: [describe a test input]. Identify any missing files, dependencies or access. Produce the result requested by the skill without inventing data or running unreviewed scripts.Expected result: output matching the skill instructions, or a precise list of missing prerequisites. A read confirmation alone does not validate a first use. If an external resource is unavailable, that path remains untested.
React Hook Form Best Practices
Development
Master React Hook Form: avoid anti-patterns, manage subscriptions, and handle reset, dirty state, and controlled inputs correctly.
Emotion to Mantine Migration
Development
Migrate Emotion styled-components to Mantine components with style props and CSS modules. Use when converting .styled.tsx files or removing @emotion imports.
Scope Creep Detector
Development
Analyzes git diffs against a stated intent to detect scope creep, unrelated files, broad PRs, and oversized changes, then suggests keep, split, or justify actions.