skills.rest
yusaduymaz
yusaduymazCOMMUNITY
Explore all skills by this author →
WebsiteGitHub

gsd-graphify

Build and inspect repository knowledge graphs with queryable node summaries.

Updated May 22, 2026
Search Tags:#knowledge graph#dependency mapping#repository analysis#graphify#diff inspection#status checks
One-click install
npx skills add https://github.com/yusaduymaz/loexai --skill gsd-graphify-yusaduymaz
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: gsd-graphify
Source: https://github.com/yusaduymaz/loexai/tree/main/.codex/skills/gsd-graphify
Command: npx skills add https://github.com/yusaduymaz/loexai --skill gsd-graphify-yusaduymaz

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This Skill helps you build, query, and inspect a repository knowledge graph so you can understand project structure, relationships, and freshness without manually tracing files and dependencies.

Core Features & Use Cases

  • Graph Build: Create or rebuild the project knowledge graph from the current repository.
  • Graph Query: Search for nodes, relationships, and confidence tiers to find specific concepts or files.
  • Status and Diff Checks: Review graph freshness, counts, and changes since the last build to keep the graph trustworthy.
  • Use Case: Use it when you need a fast overview of architecture, want to inspect how repository concepts connect, or need to verify whether the graph is up to date before acting on it.

Quick Start

Ask the skill to build the knowledge graph for the current repository.

Frequently Asked Questions about gsd-graphify

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

FAQPage Schema
How do I build a knowledge graph for my repository to map dependencies?▼

Building a knowledge graph for repository dependency mapping requires deterministic build orchestration that parses your codebase and generates queryable node and edge summaries. This Skill creates a structured .planning graph output representing project relationships and artifacts.

What is a repository knowledge graph used for in codebase analysis?▼

A repository knowledge graph represents project structure and relationships, allowing you to trace dependencies and inspect artifact connections without manually reading files. It provides queryable node and edge summaries of how repository concepts connect.

How do I check if my project knowledge graph is fresh and up to date?▼

To check if your project knowledge graph is fresh, run a status check to review graph counts and freshness since the last build. This verifies whether the graph is up to date before you act on its dependency mappings.

Can I inspect changes and diffs in my repository dependency graph?▼

Yes, you can inspect changes and diffs in your repository dependency graph by running a diff workflow. This compares the current codebase state against the last build to highlight changes in nodes, edges, and confidence tiers.

What happens if the graph configuration is missing or disabled?▼

If the graph configuration is missing or disabled, the Skill handles it safely by avoiding build failures and returning status notifications. It ensures deterministic build orchestration skips gracefully without corrupting existing graph outputs.

Related Skills

Explore More Software Engineering Skills→
paradox123paradox123

context-bootstrap

Collect repository structure, runnable commands, and architecture anchors at startup.

Community
Intermediate
IoncradeIoncrade

contextmap

Builds and queries knowledge graphs from source code using Python libraries.

Community
Advanced
lalulalilalulali
8

code-graph

Build and maintain structural dependency graphs from codebase imports and exports.

Community
Intermediate
automatedigitalautomatedigital
1

graphify

Convert unstructured code, docs, and media into queryable knowledge graphs.

Official
Advanced