REA
Reverse engineer anything from your terminal or agent with one CLI and MCP server.
Turn any codebase into a knowledge graph grounded in formal methods. Your AI agents get exact answers for any code-related task, ensure correctness, and optimize time and token usage.
作者の方は、このコードを README に貼れます。バッジはこのページにリンクします。
[](https://mcp.popnx.com/en/skills/axiomcodeai-axiomcodegraph)同じ作業で AI をサービスにつなぐ MCP
Reverse engineer anything from your terminal or agent with one CLI and MCP server.
Codebase intelligence for TypeScript and JavaScript, exposed as structured MCP analysis tools.
MCP server for terminal commands, file operations, and process management
同じ種類の作業。Skill 一覧と同じ並び
| これ axiomcodegraph | rea | graphify | archify | security-audit-skill | |
|---|---|---|---|---|---|
| 作者 | AxiomCodeAI | morluto | Graphify-Labs | tt-a1i | cloudflare |
| Skill 数 | 1 | 1 | 1 | 1 | 1 |
| GitHub スター | 693 | 461,751 | 148,352 | 96,757 | 73,156 |
| 最終コード更新 | 2026年11月10日 | 2026年11月16日 | 2026年11月16日 | 2026年11月15日 | 2026年9月15日 |
| ライセンス | – | MIT | Apache-2.0 | Apache-2.0 | MIT |
AxiomCodeAI による 1 個の Skill(指示セット)。AI が読んでそのとおりに作業します · MCP server ではありません
MCP = 手
AI を外部のサービスやデータにつなぎます(例:Notion を読む、請求書を作る)。プログラムやサーバーが動いている必要があります。
Skill = 手順書
作業のやり方を AI に教えるテキストファイル。どのサービスにもつながりません。
重なる部分もあります。ツールを呼ぶスクリプト付きの Skill や、知識だけを渡す MCP もあります。やりたい作業から選んでください。
Claude CodeCodexCursorGemini CLIGitHub CopilotWindsurf
提供元の README と repo のフォルダから判断
GitHub account AxiomCodeAI (organization) is only 2 months old: take extra care
★ 693 stars · code last changed 2026年11月10日
No, plain text files the AI reads and follows
No scripts, so it does not go online by itself
Installing the maker’s way adds hooks that run without you asking: run on the BeforeAgent event · run on the BeforeTool event · run on the AfterTool event · run on the AfterAgent event · run every time a chat starts
Checked automatically from the repo files at commit 45ee8b1 (read only, nothing was run). Not a safety guarantee: read it and decide for yourself
まず:どの AI を使っていますか
使っているアプリを選ぶと、そのアプリでのインストール方法だけが表示されます
This skill has no license, so we do not hand out a ZIP from our site. Download it from GitHub and arrange the folder yourself, or use "Let the AI install it" above, which is easier
Download from GitHub (whole repo) ↗
Unzip it, then zip only the skills/axiomcode folder again. The ZIP must have a axiomcode folder with SKILL.md at the top level, no loose files
+Create skillUpload a skillpick axiomcode.zip
SettingsCapabilitiesCode execution and file creation
Turn on Code execution and file creation first (newer menus: Create and edit files) · personal plans: Settings → Capabilities · Team/Enterprise: an admin turns it on under Organization settings → Plugins & skills · every plan, including Free
Upload once; it works in claude.ai and Claude Desktop, and in recent Claude Code signed in with a Claude account (not with an API key)
Cowork and cloud sessions use the skills turned on in your claude.ai account, not ~/.claude/skills on your computer (Claude Desktop scheduled tasks run locally and still load it)
Checked against official docs 2026年11月12日 · Source: support.claude.com, support.claude.com, code.claude.com
この文をコピーして Claude Code のチャットに貼り付けます
For one project, paste it into a chat that is open in that project’s folder · The AI always shows you the path before installing
The AI tells you what it will do first and asks your permission at every step
Claude Code を開き直し、/axiomcode と入力するか関連する作業を頼むと Claude が自動で使います
Checked against official docs 2026年11月12日 · Source: code.claude.com
Skill は AI が従う指示です。入れる前にファイルを読み、信頼できる提供元のものだけを入れてください。
Mac:Command+スペースで Terminal と入力 · Windows:下のコマンドは PowerShell では動きません。上の「AI にインストールしてもらう」を使ってください
repo を一時フォルダにダウンロードし、SKILL.md のあるフォルダだけをコピーします
コマンドを確認中 · 確認が通るとコピーボタンが出ます
ChatGPT デスクトップアプリには Codex が組み込まれていて、Codex は ~/.agents/skills フォルダから Skill を読み込みます
ChatGPT デスクトップアプリで Codex を開き、この文をチャットに貼り付けます
The AI always shows you the path before installing
The AI tells you what it will do first and asks your permission at every step
axiomcode フォルダを ~/.agents/skills/axiomcode に置きます
~ はホームフォルダ($HOME)です
Skill は AI が従う指示です。入れる前にファイルを読み、信頼できる提供元のものだけを入れてください。
Mac:Command+スペースで Terminal と入力 · Windows:下のコマンドは PowerShell では動きません。上の「AI にインストールしてもらう」を使ってください
repo を一時フォルダにダウンロードし、SKILL.md のあるフォルダだけをコピーします
コマンドを確認中 · 確認が通るとコピーボタンが出ます
Checked against official docs 2026年11月15日 · Source: learn.chatgpt.com
自分でインストールした Skill は使えません。ディレクトリのプラグインに含まれる Skill だけが使えます
この Skill を ChatGPT で使うには、上の方法で ChatGPT デスクトップアプリを使ってください
Checked against official docs 2026年11月15日 · Source: learn.chatgpt.com
この文をコピーして Codex のチャットに貼り付けます · ChatGPT デスクトップアプリ内の Codex、Codex CLI、IDE 拡張機能で使えます
For one project, paste it into a chat that is open in that project’s folder · The AI always shows you the path before installing
The AI tells you what it will do first and asks your permission at every step
Codex は新しくインストールした Skill を自動で見つけます。表示されない場合は Codex を再起動してください · 使い方:ChatGPT では @ を入力して Skill を選びます · Codex CLI や IDE 拡張機能では /skills を実行するか、$ に続けて Skill 名を入力します
Checked against official docs 2026年11月15日 · Source: learn.chatgpt.com
Skill は AI が従う指示です。入れる前にファイルを読み、信頼できる提供元のものだけを入れてください。
Mac:Command+スペースで Terminal と入力 · Windows:下のコマンドは PowerShell では動きません。上の「AI にインストールしてもらう」を使ってください
repo を一時フォルダにダウンロードし、SKILL.md のあるフォルダだけをコピーします
コマンドを確認中 · 確認が通るとコピーボタンが出ます
この文をコピーして Cursor のチャットに貼り付けます
For one project, paste it into a chat that is open in that project’s folder · The AI always shows you the path before installing
The AI tells you what it will do first and asks your permission at every step
Cursor の Agent チャットで / を入力し axiomcode を選ぶ
Checked against official docs 2026年11月12日 · Source: cursor.com
Skill は AI が従う指示です。入れる前にファイルを読み、信頼できる提供元のものだけを入れてください。
Mac:Command+スペースで Terminal と入力 · Windows:下のコマンドは PowerShell では動きません。上の「AI にインストールしてもらう」を使ってください
repo を一時フォルダにダウンロードし、SKILL.md のあるフォルダだけをコピーします
コマンドを確認中 · 確認が通るとコピーボタンが出ます
Skill を読めるほかのアプリ向けです。この文には Claude Code、Codex、Cursor のパスが入っていて、AI が使っているアプリに合わせて選びます · Copy this sentence into the app’s chat
For one project, paste it into a chat that is open in that project’s folder · The AI always shows you the path before installing
The AI tells you what it will do first and asks your permission at every step
Checked against official docs 2026年11月12日 · Source: code.claude.com, learn.chatgpt.com, cursor.com
Gemini CLI や GitHub Copilot など Agent Skills 対応の他のアプリはフォルダが違います。そのアプリのガイドを見て、SKILL.md のあるフォルダをコピーしてください。
2026年11月11日 に Claude Code、Codex、Cursor の公式ガイドで skill フォルダを確認
以下は提供元の repo の文章で、PopNx MCP の指示ではありません
最初の 8,000 文字を表示 · GitHub で全文を開く
---
name: axiomcode
description: >-
Use for any why, what or where question about code — how a codebase works, where something lives, who calls it, what a change to it breaks, which tests cover an edit. Also use when resolving an issue or bug report, which names a symptom rather than a file. Examples: "How does X work?", "Where do I change Y?", "What calls this?", "What breaks if I change Z?", "Which tests do I run?", "Fix this issue". Search with grep as usual; ask the graph for what grep cannot know — which declaration a call reaches and the callers that never spell the name. Answers come from a resolved call graph, so they include callers that never spell the name — through an interface, an override, a callback, dependency injection or a config key — and every place comes with the code of the function it sits in. Call the MCP tools directly, no need to load this skill first: impact(name) for who calls it and what a change reaches (with no name: your uncommitted edits), path(start, end) for how A reaches B, tests() for the tests your edits reach, context(task, source=True) for how something works as a step-by-step call flow with each step's code. Only when those tools are not in your list, the same from the shell: `axiomcode impact <name>`, `axiomcode path <A> <B>`, `axiomcode tests`, `axiomcode context "<task>" --source`. Java, TypeScript, Python, JavaScript, C#, and HTML + CSS (impact .class, #id, a custom property as var(…), page.html, sheet.css, page.html:LINE; each language its own graph).
---
# axiomcode
Search with grep as usual; the graph answers what grep cannot. Use the MCP tools when they are in your list (in Claude Code
`mcp__plugin_axiomcode_axiomcode__impact`, `__path`, `__tests`, `__context`); otherwise run
`<this dir>/../../plugins/axiomcode/skills/axiomcode/scripts/axiomcode <verb>` from the repository root. Same answer either way.
| the question | MCP tool | shell |
|---|---|---|
| where is the code for this task? | your own search (grep), then bring the name here | — |
| who calls X, what does changing it reach, which tests? | `impact(name)` | `axiomcode impact <name>` |
| what is the value of constant X, and who reads it? | `impact(name)` | `axiomcode impact <name>` |
| what do my uncommitted edits reach? | `impact()` | `axiomcode impact` |
| how does A reach B? | `path(start, end)` | `axiomcode path <A> <B>` |
| which tests do my edits need, and how do I run them? | `tests()` | `axiomcode tests` |
| an answer lists an unresolved call I can see the target of | `link(site, target)` | `axiomcode link <file:line> <target>` |
| how does this work, start to finish? | `context(task, source=True)` | `axiomcode context "<task>" --source` |
Names are written as in the code: `Owner.method`, `function`, `Type`, or `file.py:123` for the declaration at that
line. There is no setup step: the first question builds the graph, and it refreshes itself after every edit.
## What an answer looks like
A numbered list of places, most relevant first, each with the code of the function it sits in. `→` marks the line
that matters; a short function is shown whole.
1. shop/pricing.py:6 [resolved · total]
```python
4 def total(prices):
5 net = sum(prices)
→ 6 return net * (1 + vat_rate())
```
verified: ✓ (4 edge(s) looked up again)
Answer from the code shown; open a file only for a place whose body was cut (`…`). The tag says how sure the place
is: `resolved` is an edge the engine resolved and re-checked (`verified:`), do not re-derive it by grepping;
`one of a set` is one of several real targets; `by name` and `text` are leads, not facts; `test` marks a test;
`hop N` is how far out it is. A call the graph could not resolve is *unknown*, not absent: never report "no callers"
from an empty answer.
## impact
With a name: who calls it, what depends on it further out, and the tests that exercise it. Example:
`impact(name="PriceService.total")`. With no name: the first line is `your edits:` (each declaration you changed and
how), then the same answer for all of them. A constant answers with its value — `change: const MAX_ITEMS = 5` —
so a limit, a default or a threshold is read off the first line rather than from the file.
## path
How one declaration reaches another: every hop of the call chain, with the code at the line each call is written on.
Example: `path(start="main", end="Ledger.put")`.
## tests
The tests your uncommitted edits reach, each with its code, and a last line `run: <command>` that runs exactly those.
Example: `tests()`. It is a lower bound: a test reached only through reflection or a service loader is not listed.
## link
Answers are in three parts. CONFIRMED places are backed by an edge: `resolved` by the engine, or `asserted` by a link —
act on them. LEADS are reached only through a guess (`by name`, `by key`, `one of a set`, `text`) — check each before
relying on it. TO RESOLVE lists the calls the answer stopped at: the site as `file:line:col`, the call as written, why
the engine could not follow it (a value from `getattr`, a handler table, reflection, a callback) and the graph's
candidate targets with their `file:line`.
When the task depends on one of those sites, read the call. Only if the code makes the target CERTAIN, record it:
`link(site="app/dispatch.py:6:12", target="on_save")`, or `axiomcode link app/dispatch.py:6:12 on_save` from the shell.
A candidate is a lead: confirm it by reading the call, never link one because it is ranked first. From then on impact,
path and tests walk that edge, labelled `[asserted]`, never `resolved`; when the target declares a return type, the
calls made on its result (chained, or on a variable assigned from it) resolve too. When a lead at a site is wrong,
reject it: `link(site, "not:<target>")` — it is no longer walked; only a guess can be rejected, never an edge the
engine resolved. The links are kept in `axiomcode-links.tsv` at the repository root, which is worth committing.
`link()` with no arguments lists them and whether the graph took each one; `axiomcode link <file:line:col> -` removes
one. A link is refused when the call written there names a different declaration, or the target is not one; when
the line it was made on is edited, it is dropped and listed as stale, and the site is to resolve again. Never link a
guess: an asserted edge is trusted by every answer after it.
## context
How something works, from a task in your own words: the files and callables the task touches and, for a
how-does-X-work question, the call flow step by step. Example: `context(task="how is an invoice settled",
source=True)` — source carries each step's code, so the flow is read without opening files. Only English task
words land (the graph's vocabulary is the code's identifiers); any language works once the task includes one
identifier as written in the code.
## index
`axiomcode index` builds the graph explicitly; `--lang` and `--src` narrow it. Never re-run it on an
existing graph: the graph rebuilds itself after edits, and an answer given before that finishes says so on a
`graph refresh:` line.
By default the graph is built without the project's dependencies: a call into one is unresolved or named only as an
external boundary. When better coverage is needed, compile the dependencies and enable them with `--library`, given
once on `index` and kept by every rebuild after it:
axiomcode index --library auto # the dependencies the project imports
axiomcode index --library .venv/lib/python3.12/site-packages/requests,/deps/ir/jdk # or name them
`auto` finds what the project depends on, in every language: a Python package its source imports, in its virtual
environment (`.venv`, `venv`, `$VIRTUAL_ENV`); a JavaScript / TypeScript package it imports, under `node_modules`; in a
Deno project, every `jsr:`, `npm:` and URL module it imports, from Deno's cache (`deno install` fetches them); a
Java dependen質問、コツの共有、使えないことの報告ができます。「役に立った」の多い順です。