본문으로 건너뛰기
AI NEWS JOURNAL
Hacker News Show HNAI NEWS / JOURNAL

Show HN: An interactive architecture diagram of your codebase and infra

ig (Intent-Graph) is an a CLI tools to visualise your code architecture interactively. As I'm working heavily with AI coding and multiple project. ig helps to reduce cognitive load to have a visual way to view the code and diff. Just `ig init` on anycodebase then `ig analyse` then ìg view` you can have an interactive maps of you software architecture. Try it out `brew install mrzdevcore/tap/ig` and tell me your feedback. Thanks. Comments URL: https://news.ycombinator.com/item?id=50588411 Points: 1 # Comments: 0

번역 서비스가 일시 중지되어 원문을 표시합니다.

The architecture you meant, drawn from the code you have. Install · Quick start · Reference · Design ig (say "eye-gee", short for intent graph) reads a TypeScript/JavaScript, Python, Rust or Go repo and draws it as a system map: a canvas you can walk from the whole system down to a single function. You commit the architecture you intend in ig/, and ig checks the code against it on every run. Ask it a question and the answer is drawn on the map; give it a branch and it shows what the change does to the architecture. One binary, written in Rust. The map is a single offline HTML page. What you get A map you can walk. Packages, folders, modules and functions as nested boxes, with real imports and calls as arrows. Zoom into a box to open it up; a card shows its description, tech and where each value came from. Answers drawn on the map. ig explore "how does checkout work" prints the answer and lights the path through the system, step by step. Architecture review for every diff. ig diff main shows what a branch does to the system: boxes changed, added and removed, new arrows, broken rules. The page walks you through the change. Intent that stays true. ig/ is plain KDL you commit and review. ig plan lists what is still to build and where the code has drifted; ig check fails CI when they disagree. Your agent can use it too. ig mcp lets Claude Code (or any MCP client) read the map and draw its answers on it. Your choice of AI, or none. The map is built from the code alone. An agent (claude, gemini or codex) only runs to name and describe boxes, and only when you ask. Review a change $ ig diff 03d4b9d c251685 03d4b9d..c251685: 2 boxes changed, 1 new arrow Web → Core changed Src (core/root) (1 file) changed Src (web/root) (1 file) arrow + Web → Core (bundle) Both sides are built from a temporary checkout, so ig never touches your branches or working tree. --json gives the same result to scripts and CI. Homebrew (macOS and Linux): brew install mrzdevcore/tap/ig From source (needs Rust, node and pnpm): git clone https://github.com/mrzdevcore/intent-graph && cd intent-graph make install ig needs git on PATH and nothing else. The AI reading needs the claude, gemini or codex CLI, and only when you ask for it. Quick start ig init # ig.yaml, the agent skills, an AGENTS.md snippet ig analyse # read the code and write ig/ for you to review ig view # draw the map and open it ig explore "how does X work" # the answer on stdout, drawn on the map ig diff main # what this branch does to the architecture Review ig/ with git diff ig/ and commit it. From then on it is yours: edit it by hand, or let ig accept and your agent propose changes. Three ways to use it Commands Every flag, layers, connectors and the desktop app are in the reference; what ig init puts in ig.yaml and every key it takes are in the ig.yaml guide. How it works ig parses the repo (oxc for TypeScript/JavaScript, tree-sitter for Python, Rust and Go) into a graph of modules, classes, functions, tests and your own ast-grep patterns. The map is built in three passes: Facts: packages, folders, imports, calls and file counts. No AI; every box and arrow exists after this. Reading (optional): an agent with read-only tools names each box, describes it and spots its pattern (onion, hexagonal, layered). Every value records whether it came from the agent or from ig, and how sure it is. Layers: rule breaks, risks, and anything your own tools write to .ig/layers/*.json. The design is in docs/specs/design.md; building and testing ig itself is under Development.

자료 출처

원문 읽기 ↗

관련 주제

← 전체 소식 이어 읽기