nw-code-analysis-port
KNOWLEDGE — resolve code facts (who-calls-X / where-defined-or-read / call-graph / change-scope / file-atoms) through the vendor-neutral CLI `code-fact`, degrading LOUD through bundled adapters (AST, TextSearch).
Install / Use
npx skills add nWave-ai/nWave --skill nw-code-analysis-portInstalls into whichever agent you are using.
SKILL.md
Installable skill definition
Quality Score
Category
Development & EngineeringSupported Platforms
Our assessment of nw-code-analysis-port
nw-code-analysis-port scores 87/100 on our quality scale, 2219th of 4,698 Development & Engineering skills we index (top 48%).
Its SKILL.md is 8.8 KB long, well organised into 11 sections with 1 code example: a thorough specification that gives an agent plenty to work with.
It has 617 GitHub stars, a meaningful sign that others use it.
Maintenance, license and trust
- The repository was last updated about 2 months ago, so nw-code-analysis-port is actively maintained.
- It is released under the MIT license, a permissive license that allows use, modification and commercial use with attribution.
- Its trust signals score 100/100, with no cautions. These come from repository metadata, not a code audit — read the skill file before letting an agent act on it.
Safety scan
No issues foundOur scan of the whole file found no instruction hijacking, hidden characters, credential access, data exfiltration or destructive commands. An AI review of the same text found nothing harmful.
AI review by kimi-k2.7-code on 2026-11-10. Automated pattern scan on 2026-11-10. It catches known dangerous patterns, not every risk — read a skill before letting an agent act on it.
nw-code-analysis-port compared with similar skills
All 4 of these similar skills score higher than nw-code-analysis-port; compare them before choosing.
| Skill | Score | Stars | Updated | Format |
|---|---|---|---|---|
| nw-code-analysis-port (this skill)by nWave-ai | 87 | 617 | 2mo ago | SKILL.md |
| taste-skillby Leonxlnx | 100 | 116.8k | 8d ago | CLAUDE.md |
| ai-job-searchby ai-job-search-dev | 100 | 72.1k | today | CLAUDE.md |
| claude-howtoby luongnv89 | 100 | 47.3k | 2d ago | CLAUDE.md |
| Claude-Code-Game-Studiosby Donchitos | 100 | 39.7k | 7d ago | CLAUDE.md |
Frequently asked questions
- How do I install nw-code-analysis-port?
- Run
npx skills add nWave-ai/nWave --skill nw-code-analysis-port. The install tabs above show the steps for each supported agent. - Which AI agents does nw-code-analysis-port work with?
- It is written for Universal, as a SKILL.md file. Other agents that read the same format can often use it too.
- Is nw-code-analysis-port safe to use?
- Our scan of the whole file found no instruction hijacking, hidden characters, credential access, data exfiltration or destructive commands. An AI review of the same text found nothing harmful. It is MIT-licensed and scores 100/100 on trust signals. Skills are instructions an agent will follow, so read the file before installing it and do not approve commands you do not understand.
- Is nw-code-analysis-port still maintained?
- The repository was last updated about 2 months ago, so nw-code-analysis-port is actively maintained.
Skill content
View source on GitHubname: nw-code-analysis-port
description: "KNOWLEDGE — resolve code facts (who-calls-X / where-defined-or-read / call-graph / change-scope / file-atoms) through the vendor-neutral CLI code-fact, degrading LOUD through bundled adapters (AST, TextSearch). Trigger: any time an agent designs, writes, analyzes, or reviews code or tests and needs a structural code fact."
user-invocable: false
nw-code-analysis-port (KNOWLEDGE)
Kind: KNOWLEDGE (reference / discipline). Consulted whenever you need a fact about code. No forced sequence — load it, obey the resolution rule.
TRIGGER
Any time you design, write, analyze, or review code or tests and need a code fact — who calls X, where Y is defined or read, the call graph, the blast-radius of a change, or what a file contains — resolve it through the vendor-neutral code-fact CLI, not ad-hoc grep.
Public CLI — available now
The five-capability public stable core is wrapped in the production CLI:
code-fact query.callers-of SYMBOL --root ROOT
code-fact query.reads-of SYMBOL --root ROOT
code-fact query.never-wired SYMBOL --root ROOT
code-fact query.atoms-in-file --root FILE_OR_ROOT
code-fact query.adr-section ANCHOR --root ROOT
The CLI returns JSON: { provider, confidence, payload, index, coverage, trace }. Agents consume that envelope and degrade LOUD; they never probe/install/select an analyzer themselves. code-fact refresh --root ROOT is the one explicit way to regenerate the index (see "Index snapshot, coverage and refresh").
The resolution rule (one order, every time)
The CLI delegates to the best available bundled adapter. You report the answer tagged with which adapter answered.
The chain is walked top-down, highest declared precision first; the first provider covering the capability answers. The query's trace names the answering provider and scope. Do not duplicate a provider ranking in prose or infer precision from a familiar module name. What is stable, and all a consumer needs:
- AST gives
approxconfidence (structural, per-language) on any parseable target. - grep / lexical search is the last resort, never the default. Reach for it only when AST cannot answer.
DEGRADE-LOUD (never silent)
- Always state which adapter answered and at what confidence:
approx|binding-resolved|noisy. - If the answer came from TextSearch (grep), announce the degradation AND its limits. Example: "AST unavailable → grep fallback (
noisy): may include false positives, miss dynamic/indirect references, and conflate same-named symbols." - Never silently let grep stand in for the port. A
noisyanswer presented as fact is the failure mode this skill exists to prevent. - The CLI's
tracearray names which provider answered and its scan-scope honesty (complete|filtered|unfiltered) — that per-query record is the loud announcement a gate reads.
Operations quick-reference (question → CLI command)
| Code fact you need | CLI command | Stable |
|--------------------|-------------|--------|
| Who calls X? | code-fact query.callers-of SYMBOL --root ROOT | yes |
| Where is Y read / referenced? | code-fact query.reads-of SYMBOL --root ROOT | yes |
| Is this symbol defined-but-never-wired/used? | code-fact query.never-wired SYMBOL --root ROOT | yes |
| What atoms (defs/symbols) does this file contain? | code-fact query.atoms-in-file --root FILE_OR_ROOT | yes |
| What does an ADR / design-prose section say? | code-fact query.adr-section ANCHOR --root ROOT | yes |
| Call graph / change-scope / scope-delta | unsupported by stable CLI — use bounded stable queries + manual inspection with explicit limitation note | no |
The five stable-core capabilities answer on any UTF-8 repository, including repositories without Python: textsearch supplies the lexical floor at noisy confidence. A capability with no covering adapter returns no answer (none faked), records the honest failure in trace, and the work proceeds — do NOT substitute grep and call it the same fact.
Index snapshot, coverage and refresh
A query never writes a file and never regenerates anything. Every answer states where it was read from and what that source covers:
indexis{ "kind": "present", graph_sha256, manifest_sha256, indexed_files }when a paired code index answered, or{ "kind": "live-source" }when the answer was read from live sources (no index, or an index no refresh has paired).coverageis{ missing, stale, empty_unindexed }: non-empty files in scope the index never recorded, files whose recorded modification time differs from the live one, and 0-byte files absent from the index. The lists are complete and sorted, matched by exact path (never by a shared file name). An empty unindexed file is reported but never makes an answer indeterminate.- When the index claims a capability and
missingorstaleis non-empty, the CLI prints{ "resolution": "indeterminate", uncovered, index, coverage, trace }and exits 1.uncoveredis exactlymissingplusstale. No lower tier answers in its place. Do NOT treat it as an answer, and do NOT treat an empty result as "none": say which files are uncovered. - To regenerate the index, run
code-fact refresh --root ROOT. It prints{ "refresh": "refreshed", index, coverage }and exits 0;refused(index unchanged) orindeterminate(naming the changed index files) exit 1 with a reason. It is the only command that regenerates, it needs the indexing tool on PATH, and refuses without it.
Invocation — how to use the CLI
For ANY structural code fact, call the CLI directly:
- Stable-core queries — use
code-fact query.<capability>with the exact form above.- The CLI parses JSON and emits it; consume the
provider,confidence, andpayloadfields. - Inspect
tracefor the answering provider + scan-scope honesty (AST unavailable → TextSearch fallback).
- The CLI parses JSON and emits it; consume the
- Beyond the five capabilities — feature-level change-scope / call-graph analysis has no stable CLI today.
Say so and take the fallback: bounded stable queries (e.g.
query.callers-ofper known seams) + manual inspection + explicit limitation note. - Bundled additive tools —
code-fact find-similar-responsibility --scope ROOT --name NAMElocates similar responsibilities;code-fact impacted-tests PATH... --root ROOTreports test reach. Neither requires selecting an external provider.
Tag every answer with provider + confidence (approx | binding-resolved | noisy). Defaulting to grep/Read for a structural fact (callers/reads/never-wired/atoms) is the anti-pattern this skill exists to prevent — CLI first, grep last.
WHY through the CLI, not grep
- Structural vs lexical. AST is structural and reports
approxconfidence; TextSearch (grep) is lexical and reportsnoisyconfidence. grep over-reports (same-named symbols, comments, strings) and under-reports (dynamic/indirect refs). - Confidence is carried, not assumed. Every answer comes back in a
{provider, confidence, payload, index, coverage, trace}envelope. The confidence label is the honesty signal — a consumer can see whether a fact isapprox,binding-resolvedornoisy— andindexandcoveragesay which snapshot it was read from and which files that snapshot covers. reason_codedisambiguateslive-non-callablefromabsentinside a capability's ownpayload(e.g.query.never-wired) — a distinction grep cannot make. Degrade signals — which adapter answered, and its scan-scope honesty — live in the envelope'strace: per-query entries carryingprovider_id,event,fault_countandscope.- One seam, no per-task
import ast. Re-deriving a fact through one honest provider beats each agent hand-rolling its own search.
Implementation ownership
src/codefact/model.py owns the envelope and the provider port: each provider record declares its id, a cover function returning an answer capability, stale coverage or a pass, and an answer function returning a reply or fault. src/codefact/fold.py owns resolution over the single provider tuple composed in src/codefact/shell/cli.py. Each provider reads immutable snapshots. The index-backed provider admits an index only when its pairing record contains exactly graph_sha256 and manifest_sha256, matching the bytes read. Filesystem and refresh effects belong only to src/codefact/shell/. The public wheel binds only the AST and text-search providers: answers name their provider and carry approx or noisy confidence. It binds no code index, so refresh refuses with a reason explaining that there is nothing to regenerate and queries answer from live sources.
Scope note
This complements — it does NOT replace — reading the code and tests. Use the port to LOCATE facts (callers, definitions, references, atoms) precisely; then read the located code to understand it. The port answers "where / who / what", not "is this correct".
Related Skills
taste-skill
116.8kAgent skills that give coding agents taste: art direction, reference images and a browser check instead of generic AI pages
ai-job-search
72.1kThe job search that runs on your machine. AI job application framework built on Claude Code: evaluate postings, tailor CVs, write cover letters, prep interviews. Fork it and own it.
claude-howto
47.3kA visual, example-driven guide to Claude Code — from basic concepts to advanced agents, with copy-paste templates that bring immediate value.
Claude-Code-Game-Studios
39.7kTurn Claude Code into a full game dev studio — 49 AI agents, 72 workflow skills, and a complete coordination system mirroring real studio hierarchy.
Languages
Trust signals
From repository metadata: license, adoption, age and documentation. Not a code audit — see the Safety scan above for what the skill file itself contains.
