archify vs codeflow
Agent skill for architecture, workflow, sequence, data-flow and lifecycle diagrams: the agent emits typed JSON IR, Archify compiles it deterministically to interactive HTML/SVG with PNG/WebM export. — versus — Paste a GitHub URL or drop a local folder → interactive architecture map in the browser: dependency graph, blast radius, health grade, security scan. Single index.html, zero install.
Both produce an interactive architecture map. Codeflow derives it from the code — paste a GitHub URL, get dependencies and blast radius; Archify renders what the agent authored as typed IR, with presets, motion and snapshot diffs. Derived truth vs authored presentation.
| archify | codeflow | |
|---|---|---|
| Stars | 49k | 5.1k |
| Forks | 3.2k | 761 |
| Language | JavaScript | HTML |
| License | MIT | MIT |
| Last activity | today | 3 days ago |
| Topics | skills, code-intel | code-intel |
| Curated connections | 3 | 5 |
archify — the curator's take
The right tool when an agent needs to *present* a system, not just describe it: `npx skills add tt-a1i/archify`, describe the system (or point at a repo) and you get a self-contained HTML map with search, upstream/downstream tracing, guided stories and a Before/Delta/After compare between two validated snapshots. The model never draws — it emits IR that a validator checks, so the topology can't be hallucinated at render time. NOT a code-derived architecture tool: what it shows is what the agent authored, verified against the schema, not against the code. For a map that is provably the codebase, use a code-intelligence tool and hand its output to Archify.
codeflow — the curator's take
The fastest 'what am I looking at?' tool for an unfamiliar repo: zero install, code never leaves the browser, and blast-radius answers 'what breaks if I touch this?' before you refactor. The JSON export and README-card GitHub Action make it more than a toy. NOT compiler-grade: dependency edges come from lightweight in-browser parsing across 30+ languages, so trust it for orientation, not for exhaustive call-graph truth — agents needing tree-sitter-accurate graphs should use code-review-graph or codegraph-mcp. Big repos also eat GitHub API rate limits fast without a token.