graphify

Generate graph-based views of Lua corpora and subsystem routing in STALKER workspaces.

6|2|Updated Apr 4, 2026
One-click install
npx skills add https://github.com/qkff99/anomaly-codex --skill graphify-qkff99
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: graphify
Source: https://github.com/qkff99/anomaly-codex/tree/main/plugins/stalker-modding-workbench/skills/graphify
Command: npx skills add https://github.com/qkff99/anomaly-codex --skill graphify-qkff99

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Visualizes and navigates the STALKER workspace by providing a graph-based view of Lua corpora, subsystem routing, and cross-reference lookups.

Core Features & Use Cases

  • Repo-local graph patches for Lua scripts and a matrix of maps and reports to support focused exploration.
  • Subsystem routing, path finding, and cross-references across vanilla, GAMMA, and MCM packs to plan changes.
  • Use case: quickly identify dependencies and communication flows between ui_main, ai_workspace, and related subsystems to scope edits.

Quick Start

Describe the current workspace graph and identify a focused path between the ui_main and ai_workspace subsystems.

Frequently Asked Questions about graphify

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

FAQPage Schema
How do I visualize Lua script dependencies in a STALKER workspace?

It maps Lua script dependencies and cross-references using graph-based views of Lua corpora and subsystem routing. Focused subgraphs are generated for specific reference packs or ai_workspace subfolders to reveal module relationships.

Can I trace subsystem routing across vanilla, GAMMA, and MCM packs?

Yes, you can trace routing across vanilla, GAMMA, and MCM packs. The graph view identifies communication flows and cross-references between modules like ui_main and ai_workspace to plan changes.

What do I need to set up before generating a Lua workspace graph?

Generating a Lua workspace graph requires a valid SKILL.md with a name and description, optional assets/scripts/references directories, and repo-local bootstrap artifacts. These components must be present to operate correctly.

How do I find the dependency path between ui_main and ai_workspace subsystems?

To find the path, describe the current workspace graph and identify a focused route between ui_main and ai_workspace. This reveals dependencies and communication flows to scope edits.

Are there limitations when navigating large STALKER Lua corpora with graph views?

Graph navigation relies on repo-local patches and valid bootstrap artifacts. Large Lua corpora are handled by generating focused subgraphs for specific reference packs or ai_workspace subfolders rather than the entire workspace.