gsd-scan

Name: gsd-scan
Availability: InStock
Author: rkz91

Scan focused codebase areas and generate planning documents in .planning/codebase/.

264|11|Updated Apr 25, 2026

Search Tags:#automation #architecture #codebase #quality #mapping #scan

Ready to run

npx skills add https://github.com/rkz91/coco --skill gsd-scan-rkz91

💬 Prompt for ChatGPT / Claude Chat▼

Please help me install this Agent Skill.
Skill: gsd-scan
Source: https://github.com/rkz91/coco/tree/main/systems/gsd/skills/gsd-scan
Command: npx skills add https://github.com/rkz91/coco --skill gsd-scan-rkz91

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Identify codebase issues and architectural risks quickly.

Core Features & Use Cases

Lightweight codebase scan focusing on a defined area to surface architecture, quality, and risk signals.
Generates targeted planning documents in .planning/codebase/ for downstream work.
Use Case: Focus on the frontend module to surface component coupling issues and compile a quick risk report.

Quick Start

Analyze a codebase area to surface architectural and quality gaps and produce planning documents.

Frequently Asked Questions about gsd-scan

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

FAQPage Schema

How do I scan a codebase to identify architectural risks and quality issues?▼

A codebase scan for architecture issues runs a lightweight mapper on a focused area to surface risk signals and generate targeted planning documents. It quickly identifies quality gaps and architectural risks for reviews or downstream work.

What is the best way to generate a quick risk report for a specific module?▼

Generating a quick risk report for a specific module is done by running a lightweight scan focused on that area. It surfaces component coupling issues and architectural risks, then compiles the results into planning documents for immediate review.

Can I use this codebase scan to focus only on the frontend module?▼

Yes, you can apply the codebase scan specifically to the frontend module. The lightweight mapper targets defined areas to surface component coupling issues and compile a quick risk report for that focused context.

Where are codebase scan results stored for downstream planning?▼

Codebase scan results are stored as targeted planning documents in the .planning/codebase/ directory. The scan workflow executes mapping on focused areas and saves outputs there for reviews and architecture concerns.

What are the limitations of using a lightweight scan for codebase mapping?▼

The limitation of a lightweight scan is that it targets only focused codebase areas rather than deep exhaustive analysis. It is designed for rapid insights and targeted planning documents, not comprehensive quality enforcement across the entire codebase.