graph-docs

Traverse SeleneDB property graphs to generate structured markdown documentation.

2|Updated Apr 3, 2026
One-click install
npx skills add https://github.com/jscott3201/ai-agent-skills --skill graph-docs-jscott3201
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: graph-docs
Source: https://github.com/jscott3201/ai-agent-skills/tree/main/skills/graph-docs
Command: npx skills add https://github.com/jscott3201/ai-agent-skills --skill graph-docs-jscott3201

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This Skill produces accurate, up-to-date project documentation by traversing a SeleneDB property graph instead of relying on manual notes or scattered file scans, ensuring decisions, milestones, security findings, and deferred work are reflected in documentation.

Core Features & Use Cases

  • Graph-first Documentation: Assemble milestone reports, architecture overviews, security posture summaries, decision logs, deferred-status lists, or a full-project compilation by traversing nodes and relationships.
  • Cross-references & Annotations: Inline rationale and notes, link decisions to commits and conventions, and surface mitigations for security concerns.
  • Controlled Writes: Present drafts for user approval and then persist approved documents back to the graph as Document nodes.
  • Use Case: Create a milestone report that aggregates commits, decisions, rationale notes, and outstanding deferred items for stakeholder status updates.

Quick Start

Use the graph-docs skill to generate a milestone-report for project "my-app" focusing on decisions, commits, and annotations.

Frequently Asked Questions about graph-docs

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

FAQPage Schema
How do I generate milestone reports from a property graph database?

Generate milestone reports by traversing a SeleneDB property graph to aggregate commits, design decisions, and deferred work into structured markdown. The graph is queried for milestone nodes and relationships, then assembled into reports with cross-references and annotations.

Can I document security posture and design decisions directly from graph data?

Document security posture and design decisions by traversing SeleneDB graph nodes and relationships to surface mitigations and rationale. The Skill assembles these findings into structured markdown summaries with inline notes and cross-references to related commits.

What is the best way to keep project documentation updated without manual file scans?

Keep project documentation updated by querying a SeleneDB property graph instead of scanning scattered files. Traversing the graph ensures milestones, security findings, and deferred work are accurately reflected in generated architecture overviews and decision logs.

Does graph-docs write generated documentation back into the SeleneDB graph?

Graph-docs writes approved documentation back into the SeleneDB graph as Document nodes. Drafts are presented for user approval first, then persisted back to the property graph to maintain a unified, queryable project knowledge base.

How do I create a full-project compilation from a property graph?

Create a full-project compilation by traversing all SeleneDB property graph nodes and relationships to assemble a comprehensive markdown document. The Skill aggregates milestones, decisions, security concerns, and deferred statuses into a single structured overview.

What do I need to set up before generating documentation from a SeleneDB property graph?

You need a SeleneDB property graph populated with project nodes representing milestones, decisions, security concerns, and commits. The graph must store these relationships so the Skill can traverse them to produce structured markdown documentation.