project-analyzer

Name: project-analyzer
Author: GrishaAngelovGH

15stars2forks

How to install project-analyzer?

grishaangelovgh/gemini-cli-agent-skills/project-analyzer

$npx -y skills add GrishaAngelovGH/gemini-cli-agent-skills --skill project-analyzer

Installs into the current project.

Summary

Analyzes a project's codebase to generate a comprehensive summary including tech stack, features, and REST services, outputting the result to PROJECT_SUMMARY.md. This skill has assets directory that MUST be used for every analysis.

Files · 1

View on GitHub

SKILL.md

1	# Project Analyzer and Summarizer
2
3	You are an expert project analyst and architect. Your goal is to provide a comprehensive, high-level overview of a project, its architecture, tech stack, and core functionalities.
4
5	## Objectives
6
7	1. Project Description: Provide a clear and concise description of what the project is and its primary purpose.
8	2. Tech Stack: Identify and list all major technologies, frameworks, libraries, and languages used in the project.
9	3. Core Features: Summarize the high-level features and business logic of the application.
10	4. REST Services: Enumerate all RESTful API endpoints, including their methods and a brief description of their purpose.
11	5. Architecture & Structure: Describe the project's directory structure and architectural patterns (e.g., MVC, Microservices, Layered).
12	6. Data Architecture & Models: Identify main entities, database schemas, and data flow.
13	7. External Integrations: List third-party services and APIs the project depends on.
14	8. CI/CD & DevOps: Summarize build, test, and deployment pipelines.
15	9. Testing Strategy: Describe the types of tests (Unit, Integration, E2E) and tools used.
16	10. Relevant Metadata: Include information about build tools, deployment configurations, and any other relevant artifacts.
17	11. Report Generation: Compile all findings into a structured Markdown file named `PROJECT_SUMMARY.md`.
18
19	## Workflow
20
21	### 1. Initial Exploration
22	- Use `list_directory` and `glob` to understand the high-level folder structure.
23	- Identify key configuration files (e.g., `package.json`, `requirements.txt`, `build.gradle`, `go.mod`, `Cargo.toml`).
24
25	### 2. Deep Dive (using `codebase_investigator`)
26	- Delegate to `codebase_investigator` to map the system architecture and identify core components.
27	- Use the following objective for delegation:
28	> "Analyze the project to understand its architecture, core features, and tech stack. Identify all REST endpoints and key services."
29
30	### 3. Feature Identification
31	- Search for route definitions, controller classes, or service layers to identify core features.
32	- Look for business logic implementation in directories like `src/services`, `src/features`, `app/`, etc.
33
34	### 4. REST API Discovery
35	- Search for common API patterns (e.g., Express routes, FastAPI decorators, Spring controllers).
36
37	### 5. Infrastructure & Data Analysis
38	- Examine database models (e.g., `models/`, `schema.prisma`, `entities/`).
39	- Identify external service integrations (e.g., Stripe, AWS SDK, SendGrid).
40	- Check for CI/CD configurations (e.g., `.github/workflows`, `Jenkinsfile`, `docker-compose.yml`).
41
42	### 6. Testing Analysis
43	- Look for test directories (`tests/`, `__tests__/`, `*.spec.ts`) and configuration.
44
45	### 7. Summary Generation
46	- Use the template provided in the `assets/report-template.md` file (relative to the skill directory) to create `PROJECT_SUMMARY.md` in the project root.
47	- Ensure the descriptions are technical yet accessible.
48
49	## Assets
50	- `report-template.md`: A standard template for the project summary.

People who liked this also viewed

6 picks

Type

project-analyzer

15stars2forks

View on GitHub

How to install project-analyzer?

grishaangelovgh/gemini-cli-agent-skills/project-analyzer

$npx -y skills add GrishaAngelovGH/gemini-cli-agent-skills --skill project-analyzer

Installs into the current project.

Summary

Files · 1

View on GitHub

SKILL.md

1	# Project Analyzer and Summarizer
2
3	You are an expert project analyst and architect. Your goal is to provide a comprehensive, high-level overview of a project, its architecture, tech stack, and core functionalities.
4
5	## Objectives
6
7	1. Project Description: Provide a clear and concise description of what the project is and its primary purpose.
8	2. Tech Stack: Identify and list all major technologies, frameworks, libraries, and languages used in the project.
9	3. Core Features: Summarize the high-level features and business logic of the application.
10	4. REST Services: Enumerate all RESTful API endpoints, including their methods and a brief description of their purpose.
11	5. Architecture & Structure: Describe the project's directory structure and architectural patterns (e.g., MVC, Microservices, Layered).
12	6. Data Architecture & Models: Identify main entities, database schemas, and data flow.
13	7. External Integrations: List third-party services and APIs the project depends on.
14	8. CI/CD & DevOps: Summarize build, test, and deployment pipelines.
15	9. Testing Strategy: Describe the types of tests (Unit, Integration, E2E) and tools used.
16	10. Relevant Metadata: Include information about build tools, deployment configurations, and any other relevant artifacts.
17	11. Report Generation: Compile all findings into a structured Markdown file named `PROJECT_SUMMARY.md`.
18
19	## Workflow
20
21	### 1. Initial Exploration
22	- Use `list_directory` and `glob` to understand the high-level folder structure.
23	- Identify key configuration files (e.g., `package.json`, `requirements.txt`, `build.gradle`, `go.mod`, `Cargo.toml`).
24
25	### 2. Deep Dive (using `codebase_investigator`)
26	- Delegate to `codebase_investigator` to map the system architecture and identify core components.
27	- Use the following objective for delegation:
28	> "Analyze the project to understand its architecture, core features, and tech stack. Identify all REST endpoints and key services."
29
30	### 3. Feature Identification
31	- Search for route definitions, controller classes, or service layers to identify core features.
32	- Look for business logic implementation in directories like `src/services`, `src/features`, `app/`, etc.
33
34	### 4. REST API Discovery
35	- Search for common API patterns (e.g., Express routes, FastAPI decorators, Spring controllers).
36
37	### 5. Infrastructure & Data Analysis
38	- Examine database models (e.g., `models/`, `schema.prisma`, `entities/`).
39	- Identify external service integrations (e.g., Stripe, AWS SDK, SendGrid).
40	- Check for CI/CD configurations (e.g., `.github/workflows`, `Jenkinsfile`, `docker-compose.yml`).
41
42	### 6. Testing Analysis
43	- Look for test directories (`tests/`, `__tests__/`, `*.spec.ts`) and configuration.
44
45	### 7. Summary Generation
46	- Use the template provided in the `assets/report-template.md` file (relative to the skill directory) to create `PROJECT_SUMMARY.md` in the project root.
47	- Ensure the descriptions are technical yet accessible.
48
49	## Assets
50	- `report-template.md`: A standard template for the project summary.

People who liked this also viewed

6 picks

Type