gk-graph

Build and maintain dual-layer dependency and concept graphs for gk-stack projects.

1|Updated Jul 4, 2026
One-click install
npx skills add https://github.com/gkganesh12/gk-stack --skill gk-graph
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: gk-graph
Source: https://github.com/gkganesh12/gk-stack/tree/main/skills-library/gk-graph
Command: npx skills add https://github.com/gkganesh12/gk-stack --skill gk-graph

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes references (resource) components.

What problem does it solve?

This skill solves the problem of excessive token consumption and context window saturation by providing a lightweight, queryable dependency graph that replaces the need to load full codebase documentation.

Core Features & Use Cases

  • Dual-Layer Mapping: Maintains both file-level technical dependencies and concept-level semantic relationships.
  • Rationale Extraction: Automatically surfaces WHY, HACK, and DECISION comments from source code to prevent intent drift during bug fixes or reviews.
  • Blast Radius Analysis: Enables agents to identify exactly which files are impacted by a change, significantly reducing the token budget required for diagnosis and testing.

Quick Start

Run the gk-graph build command to initialize the dependency and concept graphs for your current project.

Frequently Asked Questions about gk-graph

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

FAQPage Schema
How do I reduce token consumption when an AI agent analyzes my entire codebase?▼

To reduce token consumption during codebase analysis, you can build a queryable dependency graph that replaces loading full documentation, directly preventing context window saturation.

What is blast radius analysis for AI coding agents?▼

Blast radius analysis identifies exactly which files are impacted by a code change. It allows AI agents to query a dependency graph, significantly reducing the token budget required for diagnosis and testing.

How do I extract design rationale from source code to prevent intent drift?▼

Extract design rationale by automatically surfacing WHY, HACK, and DECISION comments from source code. This maintains a concept graph that prevents intent drift during bug fixes or code reviews.

Does gk-graph require any external dependencies or package managers to map dependencies?▼

No, gk-graph is a zero-dependency skill. It operates entirely using native git and filesystem commands to ensure high-efficiency context management without requiring external packages.

How do I map both file-level dependencies and semantic concept relationships?▼

Map both layers by maintaining a dual-layer dependency and concept graph. This tracks file-level technical dependencies alongside concept-level semantic relationships across the project.

What is the best way to identify god nodes in a software project architecture?▼

The best way is to analyze a dual-layer dependency graph that maps file and semantic relationships. This approach highlights god nodes and prevents architectural context overload.