skills.rest
OpenElementsLabs
OpenElementsLabsOFFICIAL
Explore all skills by this author →
WebsiteGitHub

project-analyze

Generate and update four project-specific documentation files from a codebase.

Updated Mar 7, 2026
Search Tags:#automation#architecture#documentation#codebase#analyze#project-docs
One-click install
npx skills add https://github.com/OpenElementsLabs/claude-base --skill project-analyze-openelementslabs
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: project-analyze
Source: https://github.com/OpenElementsLabs/claude-base/tree/main/claude-project-base/skills/project-analyze
Command: npx skills add https://github.com/OpenElementsLabs/claude-base --skill project-analyze-openelementslabs

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Analyze the current project and generate or update the project-specific documentation files (features, tech stack, structure, architecture). Use this skill when setting up claude-project-base in a new project, or when the project has changed significantly and the documentation needs to be refreshed.

Core Features & Use Cases

  • Generate the four project-specific docs: project-features.md, project-tech.md, project-structure.md, and project-architecture.md to provide Claude Code with persistent context.
  • Update existing documentation to reflect changes in the repository, ensuring consistency with the current codebase.
  • Assess and summarize the project's structure, tech stack, and architectural relationships to accelerate onboarding and future maintenance.

Quick Start

Run the project-analyze skill from the repository root to generate or update the four project-specific documentation files.

Frequently Asked Questions about project-analyze

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

FAQPage Schema
How do I auto-generate project documentation for my codebase?▼

You can auto-generate project documentation by running the analyzer from the repository root, which produces four specific docs covering features, tech stack, structure, and architecture for persistent Claude Code context.

What is the best way to document codebase architecture automatically?▼

The best way to document codebase architecture automatically is by analyzing the repository to assess and summarize architectural relationships, generating a dedicated architecture file alongside feature, tech, and structure docs.

When do I need to regenerate repository documentation?▼

You should regenerate repository documentation when the project has changed significantly, ensuring existing feature, tech, structure, and architecture docs are refreshed to reflect current codebase config and maintain consistency.

Does project documentation generation require specific dependencies?▼

Project documentation generation requires no specific dependencies, allowing you to run the analyzer directly on a new project using the base setup to assess the codebase and generate the four project-specific docs.

How to update existing project docs to reflect codebase changes?▼

Update existing project docs to reflect codebase changes by running the analyzer to validate current config and architecture, automatically refreshing the generated feature, tech, structure, and architecture documentation files.

Related Skills

Explore More Software Engineering Skills→
oaustegardoaustegard
137

versioning-skills

Initialize Git repositories and commit changes for skill directories.

Community
Basic
daviswhiteheaddaviswhitehead

codebase-docs-search

Search codebase documentation for relevant patterns and learnings.

Community
Intermediate
nanorepublicananorepublica
61

Global Tech Stack

Validate code against centralized global tech stack standards.

Community
Basic
xiduzoxiduzo
7

wtf.steer-tech

Generate a TECH.md with stack, architecture patterns, constraints, and ADRs.

Community
Advanced