One-click install
npx skills add https://github.com/deerawan/dotfiles --skill gsd-ns-context-deerawan
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: gsd-ns-context
Source: https://github.com/deerawan/dotfiles/tree/main/claude/skills/gsd-ns-context
Command: npx skills add https://github.com/deerawan/dotfiles --skill gsd-ns-context-deerawan

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

It eliminates confusion about which codebase-intelligence skill to use by routing user intent to the correct action automatically.

Core Features & Use Cases

  • Intent-based skill routing: Maps user goals like scanning, querying, graphing, documentation updates, and extracting learnings to the right downstream skill.
  • Reduced fragmentation of commands: Consolidates previous scan/intel options into a unified set of gsd-map-codebase flags so users can rely on one entry point.
  • Use Case: When you want a full repository structure mapped, run the appropriate mapped-intelligence flow and then query the resulting mapped knowledge without deciding which legacy subcommand applies.

Quick Start

Tell the assistant to "Map the full codebase structure and prepare the intelligence for later file queries."

Frequently Asked Questions about gsd-ns-context

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

FAQPage Schema
How do I route codebase intelligence requests to the correct scanning or mapping tool?

Codebase intelligence requests are routed by matching user intent to the correct downstream skill and invocation pattern, selecting the right tool for outcomes like full repository mapping or lightweight scans.

What is the best way to generate a knowledge graph from my repository structure?

To generate a knowledge graph, this routing mechanism maps your request to the gsd-graphify skill, applying the appropriate invocation pattern to transform your mapped codebase intelligence into graph data.

Can I update documentation and extract learnings from completed development phases using a single entry point?

Yes, you can use a single unified entry point to route intent for documentation updates to gsd-docs-update and phase learnings extraction to gsd-extract-learnings, reducing command fragmentation.

How do I ensure a fast lightweight codebase scan uses the correct target scope flags?

A fast lightweight codebase scan is routed to gsd-map-codebase, where the system ensures the mapped intelligence flags match your requested target scope before executing the query.

Why should I use intent-based skill routing instead of calling individual codebase mapping commands directly?

Intent-based skill routing eliminates confusion about which codebase-intelligence skill to use, automatically selecting the correct downstream action so you avoid choosing the wrong legacy subcommand.

Does this codebase intelligence router support querying mapped knowledge without running a full repository scan first?

The router supports mapped intelligence querying by selecting the appropriate downstream skill, though querying existing mapped knowledge requires a prior codebase mapping to have been completed.