Note Graph

To automatically regenerate a navigable graph for markdown memory and docs, this Skill scans memory/**/*.md and docs/**/*.md, computes a fingerprint, and runs an extractor to produce notegraph.json, docs/notegraph.md, and docs/notegraph.html outputs only when content changes are detected.

Fingerprinting detects changes in markdown documentation files by computing a deterministic hash of the memory and docs inputs, comparing it against the previous state, and skipping the extraction workflow entirely if the content remains unchanged, ensuring silent behavior when nothing is modified.

Yes, you can automate a pull request notification when new markdown notes are added, because this Skill seeds a PR and notification workflow specifically when changes occur, including defined verdicts and analysis for new bundled notes and orphaned documentation files.

The best way to handle orphaned notes in a navigable documentation graph is to run an extraction workflow that compares the current markdown state against previous outputs, automatically identifying new orphans and bundled notes with defined verdicts to notify you of meaningful structural changes.

Yes, this documentation graph generator works without external dependencies, using only internal scripts to scan markdown files, compute deterministic fingerprints, generate JSON and HTML outputs, and manage PR workflows based on detected content changes.

Your markdown documentation outputs are not updating because the extraction workflow enforces deterministic outputs and operates silently when fingerprinting detects no changes, ensuring the graph is only regenerated and PRs are only opened for meaningful content modifications.