gsd-scan

Scans a codebase to generate focused assessment documents in .planning/codebase/.

264|11|Updated Apr 25, 2026
One-click install
npx skills add https://github.com/coco-research/coco --skill gsd-scan-coco-research
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: gsd-scan
Source: https://github.com/coco-research/coco/tree/main/systems/gsd/skills/gsd-scan
Command: npx skills add https://github.com/coco-research/coco --skill gsd-scan-coco-research

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This Skill turns a large codebase into a concise, focused assessment for one area, helping you quickly understand technology choices, architecture, quality signals, and open concerns without running a full repository mapping effort.

Core Features & Use Cases

  • Targeted scanning: Produces a narrow assessment instead of a broad, expensive codebase map.
  • Flexible focus modes: Supports tech, arch, quality, concerns, or tech+arch to match the review goal.
  • Actionable output: Writes targeted documents into .planning/codebase/ for follow-up planning and analysis.
  • Use case: Use it when you need a fast technical readout before a refactor, incident review, or project handoff.

Quick Start

Ask the AI to run the gsd-scan skill on your repository with the focus you want so it generates the assessment documents in .planning/codebase/.

Frequently Asked Questions about gsd-scan

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

FAQPage Schema
How do I generate a focused technical review for a specific repository section?

To generate a focused technical review, run a codebase scan targeting one area. This produces targeted assessment documents covering technology, architecture, quality, and risk analysis without mapping the entire repository.

What is the fastest way to assess codebase architecture and quality before a refactor?

The fastest way to assess codebase architecture and quality is running a narrow scan. It generates a concise readout of technology choices and quality signals in minutes, helping you prepare for refactoring without a full mapping effort.

How do I scan my codebase for risk analysis and open concerns?

You can scan your codebase for risk analysis by executing a targeted scan workflow. It assesses open concerns and risk factors for a single repository section, writing the results into the .planning/codebase/ directory.

Can I choose specific focus modes like tech or arch when scanning a codebase?

Yes, you can choose specific focus modes when scanning a codebase. Supported modes include tech, architecture, quality, concerns, or a combined tech and architecture focus to match your exact technical review goal.

Does a targeted codebase scan produce actionable output for project planning?

Yes, a targeted codebase scan produces actionable output for planning. It writes focused assessment documents directly into the .planning/codebase/ directory, providing a quick technical readout for follow-up analysis and project handoffs.

When should I use a focused codebase scan instead of a full repository mapping effort?

Use a focused codebase scan instead of full repository mapping when you need a fast technical readout for a specific area. It is ideal before a refactor, incident review, or project handoff where a narrow assessment is sufficient.