full-scan

Name: full-scan
Availability: InStock
Author: hproof

Automates macro-level codebase scanning to map modules and generate a project structure document.

Updated Mar 18, 2026

Search Tags:#codebase #project-analysis #game-development #code-scan #architecture-documentation #module-detection

Ready to run

npx skills add https://github.com/hproof/claude-market-gamedev --skill full-scan-hproof

💬 Prompt for ChatGPT / Claude Chat▼

Please help me install this Agent Skill.
Skill: full-scan
Source: https://github.com/hproof/claude-market-gamedev/tree/main/plugins/code-analyzer/skills/full-scan
Command: npx skills add https://github.com/hproof/claude-market-gamedev --skill full-scan-hproof

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Macro-scale codebase scanning to map modules and layers and produce a structured project overview for architecture planning.

Core Features & Use Cases

Macro-level project scanning to identify module types (third-party libraries, core/infra modules, and business modules) and the overall layered boundaries.
Automated generation of a project structure document with module distribution and boundary definitions, suitable for architecture reviews.
If deeper analysis is needed, use module-analyzer for detailed internals while keeping the macro view separate.

Quick Start

Run the full-scan on your repository to generate the macro project map and structure document.

Frequently Asked Questions about full-scan

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

FAQPage Schema

How do I map modules and layers in a large codebase for architecture documentation?▼

You can map modules by running a macro-level codebase scan that classifies core, infrastructure, and business modules. This generates a structured project structure document defining module distribution and layered boundaries for architecture planning.

What is the best way to generate a project structure document for team handoffs?▼

Generating a project structure document for team handoffs is best handled by automating macro-level codebase scanning. This identifies module types and overall layered boundaries, producing a structured project overview that clarifies architecture for new team members.

How does macro-level code scanning identify third-party libraries and business modules?▼

Macro-level code scanning identifies third-party libraries and business modules by applying glossary rules to classify module types. It evaluates the codebase to distinguish external dependencies from core infrastructure and business logic, defining the overall layered boundaries.

Can I use this macro code scan for game development architecture reviews?▼

Yes, you can use this macro code scan for game development architecture reviews. It automates project structure mapping to identify module types and layer boundaries, outputting structured documentation that supports architecture evaluation and planning in game development projects.

When do I need a separate module analyzer instead of a full codebase scan?▼

You need a separate module analyzer when deeper analysis of internal module details is required. A full codebase scan provides a macro view of module types and boundaries, while a detailed module analyzer inspects the internal logic without cluttering the macro architecture overview.

Does the project structure document include boundary definitions for architecture planning?▼

Yes, the project structure document includes boundary definitions for architecture planning. The automated scanning process ensures macro-level module classification using glossary rules and outputs structured documentation detailing module distribution and the overall layered boundaries of the codebase.