{"slug": "archify-honest-review", "title": "Archify : Honest Review", "summary": "Archify, an agent skill for Claude Code, Cursor, Codex, and OpenCode, generates architecture diagrams from code repositories via a coding agent that creates a typed JSON description, which Archify validates and renders as interactive HTML/SVG diagrams. A developer's review found the tool useful for regenerating diagrams when code changes and for inspecting source evidence, but noted that validation does not prevent hallucinations and that users must verify important nodes and relationships.", "body_md": "Architecture diagrams become unreliable when the code changes but the diagram does not.\n\nArchify approaches this problem by generating diagrams through your coding agent. The agent analyzes a repository, creates a typed JSON description of the system, and Archify validates and renders it as an interactive HTML/SVG diagram.\n\nI tested it on an unfamiliar repository to answer four practical questions:\n\nHow accurately does it represent real code?\n\nCan the diagram be regenerated when the code changes?\n\nIs its architecture comparison useful during reviews?\n\nWhat should you verify before trusting the output?\n\nThis post explains how to install Archify, generate a focused architecture diagram, check its claims against the repository, and avoid wasting model usage on an overly broad scan.\n\nArchify is an agent skill for Claude Code, Cursor, Codex, and OpenCode.\n\nThe coding agent examines your repository or system description and writes a typed JSON representation of the architecture. Archify validates that representation and compiles it into a self-contained interactive HTML/SVG diagram.\n\nIt currently supports five types of diagrams:\n\nThis distinction matters: the coding agent interprets the repository, while Archify validates and renders the resulting structure.\n\nArchify can catch malformed data, invalid references, layout problems, and several kinds of misleading visual routing. It cannot guarantee that the agent understood every architectural detail correctly.\n\nYou still need to review the result.\n\nArchify requires Node.js 18 or newer.\n\nInstall the skill globally:\n\n```\nnpx skills add tt-a1i/archify -g\n```\n\nThen open your project in a supported coding agent and use a scoped prompt such as:\n\n```\nAnalyze this repository, then use Archify to create a high-level\nruntime architecture diagram.\n\nShow 8–12 core components, the primary request path, external\ndependencies, storage, and trust boundaries.\n\nInclude source evidence where it is supported. Put secondary\ndetails in cards instead of adding more edges.\n```\n\nThe `8–12 core components`\n\nconstraint is useful. Without it, a large repository can produce a technically detailed diagram that is difficult to read.\n\nFor a system that does not exist as code yet, you can also start with plain English:\n\n``` php\nUse Archify to draw this system:\n\nBrowser -> API gateway -> authentication service -> application API\n-> Redis cache -> PostgreSQL fallback.\n\nShow the trust boundary around the private services and database.\n```\n\nEvery architecture diagram I have created manually was accurate for a limited time.\n\nThen somebody renamed a service, moved a responsibility, or introduced another queue. The code changed, but the diagram did not.\n\nAn Archify diagram is not automatically synchronized with your repository. You must rerun the agent when the architecture changes.\n\nThe difference is that regeneration is much cheaper than manually redrawing the system.\n\nInstead of deciding whether an old diagram is still trustworthy, I can regenerate it from the current repository and review the differences.\n\nThat makes architecture documentation feel more like a build artifact and less like a drawing somebody has to remember to maintain.\n\nIn evidence-backed architecture mode, components can reference repository files and line ranges pinned to a specific commit.\n\nThis is the part I found most valuable.\n\nWhen I select a component, I can inspect the source evidence behind it instead of accepting a convincing-looking box. If a component is missing, I can search the repository and determine whether the agent overlooked it or whether the code genuinely is not there.\n\nThere is an important limitation, though.\n\nValidation does not make hallucination impossible. The agent still authors the JSON structure, and repository evidence is optional and subject to supported repository conditions.\n\nMy rule is simple: I do not trust the diagram because it looks polished. I trust it only after I have checked the important nodes and relationships against the code.\n\nA useful verification pass is:\n\nThe diagram accelerates understanding. It does not replace engineering judgment.\n\nArchify diagrams can contain guided views that focus the reader on existing nodes and relationships.\n\nA view might highlight:\n\nThese views are presentation layers over the authored topology. They do not silently create additional components or connections.\n\nThis makes the output useful for more than private exploration. I could see it working well for onboarding, design discussions, and explaining an unfamiliar service during a review.\n\nArchify can compare two validated architecture snapshots and produce a Before, Delta, and After view.\n\nFrom a checkout containing the Archify CLI, the command looks like this:\n\n```\nnode archify/bin/archify.mjs compare architecture \\\n  base.json \\\n  head.json \\\n  architecture-delta.html \\\n  --json\n```\n\nAdjust the CLI path to match your installation.\n\nThe comparison can identify authored additions, removals, changes, movement, and rerouted relationships. It also produces a machine-readable receipt.\n\nWhat it does **not** do is equally important.\n\nThe delta view does not determine:\n\nIt compares two authored architecture descriptions. It does not replace tests, observability, or human review.\n\nEven with that limitation, seeing architectural additions and removals beside a pull request is something a static diagram rarely provides.\n\nArchify itself is open source and free to run locally. The potentially expensive part is the coding agent analyzing your repository.\n\nOn a small application, that may be negligible. On a large monorepo, an unbounded request can consume significant model context and usage.\n\nI now scope repository runs by:\n\nI would not begin with “diagram the entire monorepo.”\n\nI would start with something narrower:\n\n```\nMap the runtime architecture of packages/payments only.\n\nInclude its public entry points, database access, queues, external\nproviders, and calls to other workspace packages.\n\nLimit the result to 12 primary components.\n```\n\nSmaller diagrams are cheaper to generate and easier to verify.\n\nI would use it for:\n\nI would not rely on it alone for:\n\nThose require evidence beyond a diagram.\n\nI tested Archify on both a plain-English system and a real repository. I also show two failure cases and how I checked the output.\n\nArchify did not eliminate the work of understanding an unfamiliar codebase.\n\nIt changed the order of that work.\n\nInstead of reading everything before I could form a useful mental model, I started with a structured map. I then used the code to confirm, correct, and deepen that map.\n\nThat was much faster than starting from a blank whiteboard.\n\nThe most useful feature was not that the diagrams looked good. It was that the underlying structure could be validated, regenerated, inspected, and compared.\n\nHave your architecture diagrams ever survived longer than a month, or have you accepted that they eventually lie?", "url": "https://wpnews.pro/news/archify-honest-review", "canonical_source": "https://dev.to/aditi_gupta_8d81622a592aa/archify-honest-review-30p8", "published_at": "2026-09-03 07:20:29+00:00", "updated_at": "2026-09-03 07:53:03.413013+00:00", "lang": "en", "topics": ["developer-tools", "ai-tools", "ai-agents"], "entities": ["Archify", "Claude Code", "Cursor", "Codex", "OpenCode", "Node.js"], "alternates": {"html": "https://wpnews.pro/news/archify-honest-review", "markdown": "https://wpnews.pro/news/archify-honest-review.md", "text": "https://wpnews.pro/news/archify-honest-review.txt", "jsonld": "https://wpnews.pro/news/archify-honest-review.jsonld"}}