nodefony-inspect

Query Nodefony repositories via symbol graphs, inspect commands, and MCP tools.

Updated Dec 19, 2023
One-click install
npx skills add https://github.com/nodefony/nodefony-core --skill nodefony-inspect-nodefony
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: nodefony-inspect
Source: https://github.com/nodefony/nodefony-core/tree/main/.claude/skills/nodefony-inspect
Command: npx skills add https://github.com/nodefony/nodefony-core --skill nodefony-inspect-nodefony

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve? Reading entire source files to answer simple questions about a Nodefony codebase wastes context and time. This Skill answers questions about symbols, method signatures, module wiring, effective configuration, and local changes through indexed queries and targeted commands instead of loading whole files. ## Core Features & Use Cases - Symbol graph queries: Look up definitions, inheritance, interface implementations, decorators, and reverse usage relations in O(1) via jq against .ai/symbols.json and the verbose dist/symbols.json. - Runtime inspection: Run nodefony inspect (routes, services, config with provenance, stores, entities, graph) or call the Nodefony MCP server tools to query the real state of a running application. - Clean diffs: Produce targeted git diff output that excludes build artifacts, lockfiles, and regenerated symbol graphs, plus identify impacted workspace modules. - Use Case: Before refactoring a core class like Container, query relations.usedBy to list every consumer, check method signatures in the verbose graph, then verify the real mounted routes with nodefony inspect routes --json. ## Quick Start Ask the agent which classes extend a given Nodefony service and what routes a specific module exposes.

Frequently Asked Questions about nodefony-inspect

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I find which classes extend or implement a symbol in Nodefony?

Query the committed symbol graph with jq, for example `jq '.relations.extendedBy.Service' .ai/symbols.json` for subclasses or `.relations.implementedBy` for interfaces. The graph is regenerated by `npm run generate-symbols` and indexed for O(1) lookups.

How do I inspect routes, services, and config of a running Nodefony app?

Run `npx nodefony inspect routes --json`, `services --json`, or `config --json` from the application root. It boots a console profile without opening ports and returns the same values as the admin console, including config value provenance.

What is the difference between nodefony check and nodefony inspect?

`nodefony check` is a static diagnostic that works on a broken application, while `nodefony inspect` queries an application that can boot. If inspect fails, run check next to diagnose why the application cannot start.

Why does a method signature query return null in symbols.json?

Method signatures live only in the verbose `dist/symbols.json`, not the committed `.ai/symbols.json`. The verbose file is not versioned, so after a fresh clone you must run `npm run generate-symbols` before querying methods.

When should I use the Nodefony MCP server instead of the CLI?

Prefer the MCP tools when a server is already running, since answers come from the live process without a console boot. The CLI wins when the server is stopped, because it starts its own console boot.

What are the limitations of the Nodefony symbol graph?

The graph strips generics, groups homonymous symbols under shared names, performs syntactic rather than semantic inference, detects no cycles, and holds no runtime values. Stale indexes after uncommitted refactors can also mislead until regenerated.