Skill Dependency Graph

To generate a Mermaid dependency graph, this Skill fingerprints frontmatter and memory references to derive shared-state edges, producing navigable overview flowcharts and per-category drill-down diagrams for architecture review. It outputs the visual map directly into docs/skill-graph.md.

Preventing architecture drift requires change-detected skill mapping that fingerprints inputs and persisted state files to compare next-run states. This approach skips noisy documentation updates when nothing has changed and logs outcomes to maintain operational trust without silently regressing.

Automated change detection for dependency mapping works by fingerprinting frontmatter, dependency hints, and derived state references, then comparing them against a persisted state file from the previous run. If changes are detected, it rewrites the documentation or opens a PR; otherwise, it skips the update.

Yes, you can use Mermaid diagrams for repository-level dependency auditing. This Skill lints the Mermaid graph structure and click paths, overlaying enabled versus disabled status from your configuration file to ensure the visual dependency map is accurate and navigable.

Yes, dependency mapping works with scheduled documentation updates by writing a persisted state file for next-run comparisons. The self-healing mechanism fingerprints inputs on each scheduled run, only rewriting the dependency graph documentation when actual changes are detected in the skill set.