d-buzz / d-buzz/backend-api-copy
graphify: build knowledge graph + agent-crawlable wiki
- Dominant language
- JavaScript
- Stars
- 0
- Forks
- 1
- PR merge metrics
- No merged PRs in 30d
Description
## Per Father directive 2026-05-11 (msg 92566)
> "Now create an issue on every repo I'm tracking in obsidian and create an issue to graphify and create a wiki for each one then tag Jules to each one or a codex agent"
**Action:** run `/graphify .` and `/graphify . --wiki` on this repo.
**Outputs to commit to `graphify-out/`:**
- `graph.json`, `graph.html`, `GRAPH_REPORT.md`, `wiki/` (index.md + one article per community)
**Acceptance:**
- [ ] graphify completes without errors
- [ ] graph.html opens in browser
- [ ] wiki/index.md exists
- [ ] cost.json logged
- [ ] graphify-out/ committed on a branch + PR opened
**Skill reference:** https://github.com/safishamsi/graphify
@jules — please pick this up. Alternative: assign a codex sibling.
Tracked in House Obsidian board. Auto-created by Alexandrea (Library lane) per Father 92566.
Contributor guide
No contributing guide indexed for this repository
Research direction
Read the graphify skill reference first, then run `/graphify .` and `/graphify . --wiki` in the repository. Check that graphify-out/ contains graph.json, graph.html, GRAPH_REPORT.md, wiki/index.md, the community articles, and cost.json; confirm graph.html opens, commit the outputs on a branch, and open a PR.
Written by the indexing model from the issue text.
Assessment
- Domain
- documentation, tooling
- Issue type
- Feature
- Difficulty
- 3/5
- Estimated time
- 1-2 days
- Activity status
- Quiet
- Clarity
- Clearly specified
- Newbie friendliness
- 58/100