project-analysis

Analyze software project structure, complexity, and health metrics with Node.js scripts.

5|1|Updated Jan 7, 2026

Search Tags:#code quality #architecture #maintainability #project analysis #code complexity #code health

Ready to run

npx skills add https://github.com/htafolla/StringRay --skill project-analysis-htafolla

💬 Prompt for ChatGPT / Claude Chat▼

Please help me install this Agent Skill.
Skill: project-analysis
Source: https://github.com/htafolla/StringRay/tree/main/ci-test-env/.opencode/skills/project-analysis
Command: npx skills add https://github.com/htafolla/StringRay --skill project-analysis-htafolla

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes scripts (resource) components.

What problem does it solve?

This Skill addresses the challenge of gaining a deep, objective understanding of a software project's structure, complexity, and overall health without manual code inspection.

Core Features & Use Cases

Project Structure Analysis: Visualizes and analyzes file organization, directory hierarchy, and module distribution.
Complexity Assessment: Evaluates code metrics, maintainability scores, and identifies potential technical debt.
Pattern Identification: Detects common architectural and code patterns, including anti-patterns.
Health Assessment: Provides a comprehensive overview of project quality with actionable improvement recommendations.
Use Case: A new team lead can use this skill to quickly assess the health and complexity of a legacy project they've just inherited, identifying areas needing immediate attention.

Quick Start

Use the project-analysis skill to assess the complexity and health of the current project.

Frequently Asked Questions about project-analysis

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

FAQPage Schema

How do I analyze my codebase for complexity and maintainability issues?▼

You can analyze codebase complexity and maintainability by running automated Node.js scripts that parse project files to compute code metrics, evaluate health scores, and identify potential technical debt areas needing immediate attention.

What is the best way to assess the health of a legacy project I just inherited?▼

The best way to assess project health is using automated code inspection to evaluate structural organization, detect architectural patterns and anti-patterns, and generate actionable improvement recommendations for the inherited codebase.

Can I detect architectural patterns and anti-patterns in my project structure?▼

Yes, you can detect common architectural patterns and anti-patterns by executing scripts that parse your project files, analyzing directory hierarchy, file organization, and module distribution to reveal the underlying codebase structure.

Does project analysis require any specific environment or dependencies to run?▼

Project analysis requires a Node.js environment to execute the necessary scripts for parsing files and computing metrics, but the skill itself has no external dependencies to install before running the inspection.

How do I identify technical debt and areas needing immediate attention in my code?▼

You identify technical debt by computing code metrics and maintainability scores through automated inspection, which highlights complex modules and architectural issues that require immediate attention to improve overall code health.

What limitations should I expect when evaluating code health for a large project?▼

When evaluating code health, limitations depend on the Node.js parsing capabilities and the automated inspection scripts' ability to accurately compute metrics across diverse architectural patterns and complex directory hierarchies within the project.