Token导航 LogoToken导航

Agent Skill · 研究检索

ln-020-codegraph(ln 020 代码图)

ln-020-codegraph 用于查找、检索和筛选相关信息,适合在 Codex、Claude、Cursor、Gemini CLI 中需要根据关键词、任务场景或来源线索快速定位候选结果时使用。可结合来源仓库、安装命令和原始 README 继续核验具体用法。安装前建议确认权限范围、维护状态,以及是否会触发联网、命令执行或文件读写。

ln-020-codegraph 是研究检索类 Agent Skill,可用宿主为 Codex、Claude、Cursor、Gemini CLI,通过GitHub 仓库获取,权限为调用外部服务;许可证信息还不明确,第三方扫描已通过,按安装量在研究检索类的 73,675 个 Skill 里排第 36,231。

总安装 1,958周安装 80GitHub Stars 437下载 627核验 2026-05-01

安装说明

本站只整理中文说明,不托管安装包,也不代用户安装。
GitHub
许可证
unknown

安装方式

通过对话安装

复制提示词发给支持本地命令或 Skills 的 AI 助手,先确认命令和权限,再让它执行。

请帮我安装这个 Agent Skill:ln-020-codegraph(ln 020 代码图)
来源仓库:https://github.com/levnikolaevich/claude-code-skills
仓库路径:skills/ln-020-codegraph
安装命令:
npx skills add https://github.com/levnikolaevich/claude-code-skills --skill ln-020-codegraph
安装前请先检查当前环境是否支持对应 CLI,并向我确认将要执行的命令、安装目录、联网范围和文件读写权限;确认后再执行。

命令行安装

复制命令到本机终端执行。该命令会通过 npx skills 从第三方来源获取 Skill;本站只展示命令,不托管安装包,也不自动执行。

skills.shnpx skills
npx skills add https://github.com/levnikolaevich/claude-code-skills --skill ln-020-codegraph

这个 Skill 是做什么的

研究检索类 Skill 主要解决「找资料、核对事实、把来源整理清楚」的问题,通常会让助手先检索再总结。

ln-020-codegraph 用于查找、检索和筛选相关信息。适合在 Codex、Claude、Cursor、Gemini CLI 中根据关键词或任务场景快速定位候选结果。通过 npx skills add 命令从指定 GitHub 仓库安装,需结合原始 README 核验具体用法。

安装前建议确认权限范围、维护状态,以及是否会触发联网、命令执行或文件读写操作。适用宿主包括 Codex、Claude、Cursor、Gemini CLI,接入前应确认版本、权限和运行环境要求。

来源仓库内路径:skills/ln-020-codegraph

上手步骤

4 步
  1. 1

    确认自己的宿主工具

    公开资料标注支持 Codex、Claude、Cursor、Gemini CLI;先确认自己用的是其中之一,再按对应工具的 Skills 目录放置。

  2. 2

    拿到安装命令

    可以直接复制的命令是 npx skills add https://github.com/levnikolaevich/claude-code-skills --skill ln-0…;命令里的占位符换成自己的路径或密钥再执行。

  3. 3

    安装后重启宿主

    命令执行完要完全退出宿主工具再打开,让新装的 Skill 被重新扫描到,否则列表里可能看不到。

  4. 4

    按最小权限试用

    它需要调用外部服务,先在测试目录或测试账号里跑,确认没问题再放到正式项目。

常见问题

6 条

ln-020-codegraph 怎么安装?

在终端执行 npx skills add https://github.com/levnikolaevich/claude-code-skills --skill ln-020-codegra…。装完完全退出宿主工具再打开,让它重新扫描本地 Skill。

ln-020-codegraph 支持哪些 AI 工具?

公开资料标注支持 Codex、Claude、Cursor、Gemini CLI。其他工具只要能读取本地 Skill 目录,一般也能手动放进去,但要自己确认触发方式是否一致。

ln-020-codegraph 需要什么权限?

权限级别是调用外部服务。该 Skill 可能调用第三方服务、云服务或外部模型 API,使用前需要确认账号、额度、数据发送范围和服务条款。

ln-020-codegraph 是免费的吗?

公开资料没有标注明确许可证,收费和商用限制都无法确认。正式使用前请到来源仓库核对授权说明。

ln-020-codegraph 用的人多吗?

公开数据是累计安装 1,958 次,近一周安装 80 次,下载 627 次,GitHub 437 星。这些数字来自第三方目录统计,只能当作热度参考,不代表质量或安全性。

ln-020-codegraph 安全吗?

第三方扫描结果为通过,但这只覆盖已知的静态检查项,不能替代自己读一遍源码和安装命令。

值得选的地方和要先想清楚的地方

值得选的地方

  • 同时适配 4 种工具,换客户端不用重新找替代品。
  • 第三方扫描已通过,常见的高风险行为没有命中。

先想清楚的地方

  • 许可证没有明确标注,能不能商用、能不能再分发都不确定。
  • 第三方目录整理,版本更新和行为细节以来源仓库为准。

适不适合你

更适合

  • 已经在用 Codex,想直接扩展它能力的人。
  • 需要处理研究检索类任务、又不想每次都手写提示词的人。

不太适合

  • 需要明确授权才能用到公司项目里的场景。
  • 需要厂商级技术支持和 SLA 的生产系统。

研究检索类 Skill 对比

6 个同类
Skill总安装GitHub 星权限许可证扫描
find-skills

寻找技能 · Codex、Claude

31,199,81316,486操作浏览器MIT有提醒
self-improving-agent

自我改进 Agent · OpenClaw

16,464,0023,396接触敏感数据MIT-0通过
soultrace

灵魂追踪 · Codex、Claude

7,588,94412需要联网未明确有提醒
self-improving

自我完善 · OpenClaw

6,829,2841,046需要联网MIT-0通过
microsoft-foundry

微软代工厂 · Codex、Claude

6,614,144764调用外部服务未明确有提醒
ln-020-codegraph

ln 020 代码图 · 本页

1,958437调用外部服务未明确通过

按安装量取同分类前几名;数字来自第三方目录统计,只作热度参考,不代表质量结论。

SKILL.md 原文

Paths: File paths are relative to skills repo root.

Code Knowledge Graph

Type: Standalone Utility Category: 0XX Dev Environment

Indexes codebase into a layered graph (tree-sitter AST → SQLite) and provides dependency analysis, path tracing, references, implementations, and architecture overview via MCP tools.

Inputs

InputRequiredSourceDescription
project_pathyesargs or CWDProject root to index
commandnoargsSpecific action: index, search, symbol, paths, refs, arch

When to Use

  • Starting work on an unfamiliar codebase → index + architecture
  • Before refactoring a function/class → find_symbols + inspect_symbol + trace_paths
  • Understanding call flow → trace_paths
  • Finding a symbol quickly → search

MCP Availability

MANDATORY READ: Load shared/references/mcp_tool_preferences.md and shared/references/mcp_integration_patterns.md

Use hex-graph first when the task depends on symbol identity, references, implementations, architecture, dataflow, or edit impact. Use hex-line first for targeted local code reads when available. If MCP is unavailable, unsupported, or not indexed, continue with built-in Glob/Grep/Read/Bash, answer with manual evidence, and explicitly note the degraded confidence instead of blocking the skill.

Workflow

Phase 1: Index

Check if graph exists (.hex-skills/codegraph/index.db in project root).

If NOT exists:

Call: index_project({ path: "{project_path}" })

If exists (re-index on demand):

Call: index_project({ path: "{project_path}" })

Idempotent — skips unchanged files automatically.

If hex-graph is unavailable: build a manual project map with Glob and targeted Grep/Read, then continue to the closest matching query workflow without indexing.

Phase 2: Query

Route based on user intent:

User saysToolParameters
"Show dependencies" / "What uses X?"trace_paths{name: "X", file: "...", path_kind: "mixed", direction: "reverse", path: "{project_path}"}
"Who calls X?" / "What does X call?"trace_paths`{name: "X", file: "...", path_kind: "calls", direction: "reverse"\"forward", path: "{project_path}"}`
"Tell me about X" / "Context of X"inspect_symbol{name: "X", file: "...", path: "{project_path}"}
"Project structure" / "Architecture"analyze_architecture{path: "{project_path}", scope?: "src/"}
"Find symbol X"find_symbols{path: "{project_path}", query: "X"}
"Find app.get(...) / router.use(...) / server.registerTool(...) pattern"grep_search`{path: "{project_path}", pattern: "app\.get\(
"Find duplicate code / hotspots / unused exports"audit_workspace{path: "{project_path}", scope?: "src/", verbosity: "minimal", limit: 5, clone_member_limit: 3}
"Circular dependencies / module coupling"analyze_architecture{path: "{project_path}", verbosity: "full"}
"Implementations / overrides"find_implementations{name: "X", file: "...", path: "{project_path}"}
"Dataflow / propagation"trace_dataflow{source: {symbol: {name: "X", file: "..."}, anchor: {kind: "param", name: "input"}}, sink?: {symbol: {name: "X", file: "..."}, anchor: {kind: "return"}}, path: "{project_path}"}
"Review a diff / worktree"analyze_changes{path: "{project_path}", base_ref: "origin/main"}
"Check what editing this range affects"analyze_edit_region{path: "{project_path}", file: "src/file.ts", line_start: 10, line_end: 40}

Canonical selector rule: Semantic tools accept exactly one selector:

  • symbol_id
  • workspace_qualified_name
  • qualified_name
  • name + file

Preferred flow: use find_symbols only after narrowing path as much as practical, then feed the returned workspace_qualified_name into inspect_symbol, trace_paths, find_references, or find_implementations for exact follow-up queries.

Query boundary rule: find_symbols is name-based discovery only. For code fragments like export function or unresolved member-call patterns like app.get(...), use grep_search instead of treating them as symbols.

Ambiguity rule: if find_symbols returns partial... truncated=1 or shows more total results than returned rows, refine with path, then name + file or workspace_qualified_name instead of widening the graph query.

Path rule: path may be the indexed project root or any file/subdirectory inside that indexed project.

Dataflow anchors: trace_dataflow requires source.anchor and optional sink.anchor. Use:

  • param for function parameters
  • local for local variables
  • return for function returns
  • property with access_path for bounded property flow

Precision controls: inspect_symbol, trace_paths, and find_references support min_confidence (low, inferred, exact, precise) when the caller wants to suppress weaker parser-only facts.

Phase 3: Present Results

  1. Show MCP tool output directly when available; otherwise present manual findings and mark them as fallback reasoning
  2. For code snippets referenced in results, use hex-line read_file with line ranges when available; otherwise use built-in Read
  3. Suggest follow-up queries based on results:
  • After find_symbols with a clean top match → suggest inspect_symbol with workspace_qualified_name
  • After find_symbols with partial... truncated=1 → suggest narrowing path or switching to name + file before any deeper graph tool
  • After inspect_symbol → suggest trace_paths if refactoring
  • After trace_paths → suggest find_references or find_implementations depending on symbol kind
  • After empty trace_paths from a broad or module-level selector → suggest inspect_symbol or analyze_architecture instead of assuming there are no dependencies

Supported Languages

LanguageExtensionsCoverage
JavaScript.js,.mjs,.cjs,.jsxStrongest semantic coverage
TypeScript / TSX.ts,.tsxStrongest semantic coverage
Python.pyWorkspace-aware definitions, calls, imports, unused exports; optional precise overlay when provider is installed
C#.csWorkspace-aware definitions, calls, project/namespace ownership, type relations; optional precise overlay when provider is installed
PHP.phpWorkspace-aware definitions, calls, PSR-4 namespace imports, unused exports; optional precise overlay when provider is installed

MCP Server Setup

Add to .mcp.json:

{
  "mcpServers": {
    "hex-graph": {
      "command": "node",
      "args": ["{skills_repo}/mcp/hex-graph-mcp/server.mjs"]
    }
  }
}

Definition of Done

  • Project indexed or manual fallback map built
  • Query results shown to user
  • Follow-up suggestions provided
  • Fallback path stated when MCP was unavailable

Version: 0.1.0 Last Updated: 2026-03-20

平台分布

Codex

37.92%
按下载量换算238

Claude

29.31%
按下载量换算184

Cursor

18.83%
按下载量换算118

Gemini CLI

9.23%
按下载量换算58

安全审计

Gen Agent Trust Hub

通过

Socket

通过

Snyk

通过

权限和风险

调用外部服务

该 Skill 可能调用第三方服务、云服务或外部模型 API,使用前需要确认账号、额度、数据发送范围和服务条款。

安装前确认

本站仅展示第三方公开信息,不托管安装包,不提供自动安装或运行环境。安装前应自行审查源码、依赖和命令行为。目前只有一个公开来源,建议同时核对源仓库。

继续浏览同类 Skills