gsd-scan

Analyze codebase domains and generate planning documents in .planning/codebase/.

1|Updated Apr 4, 2026
One-click install
npx skills add https://github.com/nnexai/git-stacks --skill gsd-scan-nnexai
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: gsd-scan
Source: https://github.com/nnexai/git-stacks/tree/main/.github/skills/gsd-scan
Command: npx skills add https://github.com/nnexai/git-stacks --skill gsd-scan-nnexai

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This Skill addresses the need for a lightweight, targeted analysis of specific codebase areas without the overhead of a full-scale repository mapping process.

Core Features & Use Cases

  • Focused Scanning: Performs deep analysis on specific architectural or technical domains like quality, concerns, or technology stacks.
  • Targeted Documentation: Automatically generates structured planning documents in the .planning/codebase/ directory.
  • Use Case: When you need to quickly audit the technical debt or architectural patterns of a single module, this tool provides a concise report without triggering a massive, multi-agent scan.

Quick Start

Execute the gsd-scan skill to perform a quality assessment on the current codebase area.

Frequently Asked Questions about gsd-scan

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

FAQPage Schema
How do I perform a focused codebase assessment for specific architectural domains?

A focused codebase assessment analyzes specific architectural or technical domains by spawning a mapper agent to evaluate code quality, concerns, or technology stacks within a defined scope. It outputs structured planning documentation directly to the file system.

When do I need targeted codebase scanning instead of a full repository mapping process?

Targeted codebase scanning is needed when you want to audit technical debt or architectural patterns of a single module quickly. It provides concise reporting without the overhead of a massive, multi-agent repository mapping process.

How do I generate targeted planning documentation for code quality concerns?

To generate targeted planning documentation for code quality concerns, execute a focused scan on the current codebase area. The process automatically writes structured reports to the .planning/codebase/ directory.

Does the codebase analysis tool require file system write permissions to output reports?

Yes, the codebase analysis tool requires file system write permissions to output reports. It needs this access to save generated planning documents into the designated .planning/codebase/ directory.

What is the best way to audit technical debt in a single module without triggering a multi-agent scan?

The best way to audit technical debt in a single module is using a rapid, focused scan. This approach evaluates specific technology stacks or concerns and generates concise reports without triggering a full-scale multi-agent scan.

Can I scope codebase analysis to evaluate only specific technology stacks?

Yes, you can scope codebase analysis to evaluate specific technology stacks. The scan operates within a defined scope to analyze code quality, concerns, or the targeted technology stack itself.