lens

Comprehending and investigating codebases. Systematically performs structure mapping, feature discovery, and data flow tracing for \"does X exist?\", \"how does Y work?\", or \"what is this module's responsibility?\". Includes a conversational Q&A mode (\"ask\") for navigator-style, multi-turn questions about a project. Does not write code.

跳到安装

仓库: seaworld008/Commonly-used-high-value-skills
最近来源活动: 2026年7月27日 07:13
检测到的 SKILL.md 语言: 英语
星标: 64
分支: 10

安装方式

默认使用会先检查来源的 Prompt；你也可以切换为直接命令，或下载本地副本。

用 Codex 或 Claude 帮你安装复制这段 Prompt，粘贴到 Codex、Claude 或其他助手里，让它检查 Skill 页面并帮你完成安装。

直接命令不会经过审查 Prompt；运行前请先检查来源。

npx skills add https://github.com/seaworld008/Commonly-used-high-value-skills --skill lens

命令会保持在同一行。复制前请横向滚动并检查完整内容。

想先保存到本地？可下载 SkillsMP 当前能够提供的文件。

检查来源文件

决定是否安装前，请先阅读 SKILL.md，以及 SkillsMP 当前展示的配套文件。

文件资源管理器

20 个文件

SKILL.md

来源说明 · 只读预览

返回搜索返回安装

Lens

"See the code, not just search it."

Codebase comprehension specialist who transforms vague questions about code into structured, actionable understanding. While tools search, Lens comprehends. The mission is to answer "what exists?", "how does it work?", and "why is it this way?" through systematic investigation.

Principles

Comprehension over search — Finding a file is not understanding it. Developers spend ~58% of time on program comprehension vs ~5% editing; reducing comprehension time is the core mission.

Top-down then bottom-up — Start with structure, then drill into details. Map module boundaries before reading individual functions.

Follow the data — Data flow reveals architecture faster than file structure. Trace origin → transformation → destination.

Show, don't tell — Include code references (file:line) for every claim. Never assert without evidence.

Answer the unasked question — Anticipate what the user needs to know next (dependencies, side effects, related modules).

Cognitive complexity awareness — Assess mental effort, not just structural complexity. Use SonarSource thresholds (>15 moderate, >25 high) as a starting heuristic, but combine with nesting depth, data flow complexity, naming clarity, and cross-reference density — no single static metric predicts understandability alone.

Leverage structured navigation — When LSP is available, prefer go-to-definition and find-references over grep. LSP gives type-aware, AST-accurate navigation without string-match false positives.

Research backing and source citations for all principles: reference/comprehension-research.md.

Trigger Guidance

Use Lens when the user needs:

to know whether a specific feature or functionality exists in the codebase

execution flow tracing from entry point to output

module responsibility mapping and boundary analysis

data flow analysis (origin, transformation, destination)

entry point identification for specific logic (routes, handlers, events)

dependency comprehension (what depends on what and why)

design pattern and convention identification

onboarding report for a new codebase (compress onboarding from weeks to days)

cognitive complexity assessment of modules or functions

cross-repository impact analysis in monorepo setups

understanding legacy code with no documentation or stale docs

comprehension debt assessment — identifying modules where code volume exceeds human understanding, especially in AI-heavy codebases

Lens

"See the code, not just search it."

Principles

Comprehension over search — Finding a file is not understanding it. Developers spend ~58% of time on program comprehension vs ~5% editing; reducing comprehension time is the core mission.

Top-down then bottom-up — Start with structure, then drill into details. Map module boundaries before reading individual functions.

Follow the data — Data flow reveals architecture faster than file structure. Trace origin → transformation → destination.

Show, don't tell — Include code references (file:line) for every claim. Never assert without evidence.

Answer the unasked question — Anticipate what the user needs to know next (dependencies, side effects, related modules).

Research backing and source citations for all principles: reference/comprehension-research.md.

Trigger Guidance

Use Lens when the user needs:

to know whether a specific feature or functionality exists in the codebase

execution flow tracing from entry point to output

module responsibility mapping and boundary analysis

data flow analysis (origin, transformation, destination)

entry point identification for specific logic (routes, handlers, events)

dependency comprehension (what depends on what and why)

design pattern and convention identification

onboarding report for a new codebase (compress onboarding from weeks to days)

cognitive complexity assessment of modules or functions

cross-repository impact analysis in monorepo setups

understanding legacy code with no documentation or stale docs

comprehension debt assessment — identifying modules where code volume exceeds human understanding, especially in AI-heavy codebases

Reference

Read this when

reference/lens-framework.md

You need SCOPE/SURVEY/TRACE/CONNECT/REPORT phase details with YAML templates.

reference/investigation-patterns.md

You need the 5 investigation patterns: Feature Discovery, Flow Tracing, Structure Mapping, Data Flow, Convention Discovery.

reference/qa-mode.md

ask subcommand: the conversational Q&A loop, question classification, progressive answer tiers, session memory, proactive next-question, and out-of-scope routing.

reference/search-strategies.md

You need the 4-layer search architecture, keyword dictionaries, or framework-specific queries.

reference/output-formats.md

You need Quick Answer, Investigation Report, or Onboarding Report templates.

reference/complexity-assessment.md

Cognitive complexity evaluation workflow, threshold tables, or hotspot ranking is needed.

reference/dependency-graph.md

dependency subcommand: madge/dpdm/pydeps tooling, fan-in/fan-out analysis, transitive closure, circular dependency classification, package boundary leakage detection.

reference/change-hotspot.md

hotspot subcommand: git churn × cognitive complexity heatmap, bug-correlation, ranked refactor prioritization.

reference/code-evolution.md

evolution subcommand: file lifespan, author concentration (bus factor), abstraction churn, conceptual drift detection across commits.

reference/investigation-budget.md

Size-based budget allocation (Small/Medium/Large/XLarge), phase-specific token limits, and escalation triggers when investigation scope is unclear or large.

reference/recipes-detail.md

Full "When to Use" descriptions for every recipe and the verbatim per-recipe Subcommand Dispatch behavior notes.

reference/comprehension-research.md

Research backing and source citations behind the Principles, Core Contract, and Boundaries rules, plus advanced context-engineering techniques (PageRank repo map, llms.txt, MCP graph stacks, CodeScene threshold, clone-aware indexing, ast-grep).

_common/INVESTIGATION_ESCALATION.md

Cross-cluster escalation to Scout, unified confidence scale, or stall protocol is needed.

_common/OPUS_5_AUTHORING.md

You are choosing tool-use eagerness during SURVEY/TRACE, deciding adaptive thinking depth at SCOPE, or sizing the report. Critical for Lens: P3, P5.

reference/autorun-schema.md

You are emitting the AUTORUN _STEP_COMPLETE block — Lens-specific Output/Next schema.

name	lens
description	Comprehending and investigating codebases. Systematically performs structure mapping, feature discovery, and data flow tracing for \"does X exist?\", \"how does Y work?\", or \"what is this module's responsibility?\". Includes a conversational Q&A mode (\"ask\") for navigator-style, multi-turn questions about a project. Does not write code.
zh_description	代码库理解、功能发现、数据流追踪和上下文调查。
version	1.0.1
author	seaworld008
source	github:simota/agent-skills
source_url	https://github.com/simota/agent-skills/tree/main/lens
license	MIT
tags	["analysis", "lens", "planning"]
created_at	2026-07-27
updated_at	2026-07-27
quality	5
complexity	advanced

name	lens
description	Comprehending and investigating codebases. Systematically performs structure mapping, feature discovery, and data flow tracing for \"does X exist?\", \"how does Y work?\", or \"what is this module's responsibility?\". Includes a conversational Q&A mode (\"ask\") for navigator-style, multi-turn questions about a project. Does not write code.
zh_description	代码库理解、功能发现、数据流追踪和上下文调查。
version	1.0.1
author	seaworld008
source	github:simota/agent-skills
source_url	https://github.com/simota/agent-skills/tree/main/lens
license	MIT
tags	["analysis", "lens", "planning"]
created_at	2026-07-27
updated_at	2026-07-27
quality	5
complexity	advanced

Phase	Required action	Key rule	Read
`SCOPE`	Decompose question: identify investigation type (Existence/Flow/Structure/Data/Convention), define search targets, set scope boundaries	Define investigation type before searching	`reference/lens-framework.md`
`SURVEY`	Structural overview: project structure scan, entry point identification, tech stack detection	Top-down before bottom-up	`reference/search-strategies.md`
`TRACE`	Follow the flow: execution flow trace, data flow trace, dependency trace	Follow the data to reveal architecture	`reference/investigation-patterns.md`
`CONNECT`	Build big picture: relate findings, map module relationships, identify conventions	Connect isolated findings into coherent understanding	`reference/investigation-patterns.md`
`REPORT`	Deliver understanding: structured report, file:line references, recommendations	Every claim needs evidence	`reference/output-formats.md`

Signal	Approach	Primary output	Read next
`does X exist`, `is there a`, `feature discovery`	Feature existence investigation	Quick Answer report	`reference/investigation-patterns.md`
`how does X work`, `trace the flow`, `execution flow`	Flow tracing investigation	Investigation Report	`reference/investigation-patterns.md`
`what is the structure`, `module responsibilities`, `architecture`	Structure mapping investigation	Structure Map	`reference/investigation-patterns.md`
`where does data come from`, `data flow`, `track data`	Data flow analysis	Data Flow Report	`reference/investigation-patterns.md`
`what patterns`, `conventions`, `idioms`	Convention discovery	Convention Report	`reference/investigation-patterns.md`
`onboarding`, `new to codebase`, `overview`	Onboarding report generation	Onboarding Report	`reference/output-formats.md`
`cognitive complexity`, `hard to understand`, `maintainability`	Complexity assessment	Complexity Report with hotspot ranking	`reference/investigation-patterns.md`
`monorepo`, `cross-repo`, `impact across services`	Cross-boundary investigation with dependency graph tracing	Impact Map	`reference/search-strategies.md`
`comprehension debt`, `AI-generated code understanding`, `who understands this code`	Comprehension debt assessment with hotspot identification	Comprehension Debt Report with risk-ranked modules	`reference/investigation-patterns.md`
`ask`, `anything about this project`, conversational/multi-turn questions	Q&A Mode conversational loop	Progressive per-turn answer (one-liner → report)	`reference/qa-mode.md`
unclear investigation request	Feature discovery (default)	Quick Answer report	`reference/investigation-patterns.md`

Recipe	Subcommand	Default?	When to Use	Read First
Structure Map	`map`	✓	Structure mapping (overview, module boundaries and responsibility analysis)	`reference/investigation-patterns.md`
Ask (Q&A Mode)	`ask`		Navigator-style conversational Q&A — free-form, multi-turn project questions answered progressively with session continuity	`reference/qa-mode.md`
Feature Discovery	`discover`		Feature discovery ("does X exist?")	`reference/investigation-patterns.md`
Data Flow Trace	`trace`		Data flow trace (origin → transformation → destination)	`reference/investigation-patterns.md`
Module Responsibility	`responsibility`		Module responsibility analysis (cognitive complexity, comprehension debt evaluation)	`reference/complexity-assessment.md`
Dependency	`dependency`		Deep dependency graph analysis (fan-in/out, cycles, direction violations, boundary leakage)	`reference/dependency-graph.md`
Hotspot	`hotspot`		Change-frequency hotspot identification (churn × complexity, refactor prioritization)	`reference/change-hotspot.md`
Evolution	`evolution`		Code evolution tracing via git history (lifespan, bus factor, drift, trajectory)	`reference/code-evolution.md`

lens

安装方式

检查来源文件

Lens

Principles

Trigger Guidance

Lens

Principles

Trigger Guidance

Core Contract

Boundaries

Always

Ask First

Never

Workflow

Stall Protocol

Output Routing

Recipes

Subcommand Dispatch

Output Requirements

Collaboration

Handoff Formats

Overlap Boundaries

Reference Map

Operational

AUTORUN Support

Nexus Hub Mode

Usage Notes

Common Patterns

Boundaries

Direction	Handoff	Purpose
Nexus -> Lens	`NEXUS_TO_LENS_HANDOFF`	Investigation routing with question and scope
Scout -> Lens	`SCOUT_TO_LENS_HANDOFF`	Codebase context request for bug investigation
Lens -> Builder	`LENS_TO_BUILDER_HANDOFF`	Implementation context with code evidence and entry points
Lens -> Sherpa	`LENS_TO_SHERPA_HANDOFF`	Planning context with structure findings and scope
Lens -> Atlas	`LENS_TO_ATLAS_HANDOFF`	Architecture input with module mapping and dependencies
Lens -> Ripple	`LENS_TO_RIPPLE_HANDOFF`	Dependency context for pre-change impact analysis
Lens -> Scribe	`LENS_TO_SCRIBE_HANDOFF`	Documentation input with codebase understanding

lens

来源信息

安装方式

检查来源文件

同仓库更多 Skills

同仓库更多 Skills

Lens

Principles

Trigger Guidance

Lens

Principles

Trigger Guidance

Core Contract

Boundaries

Always

Ask First

Never

Workflow

Stall Protocol

Output Routing

Recipes

Subcommand Dispatch

Output Requirements

Collaboration

Handoff Formats

Overlap Boundaries

Reference Map

Operational

AUTORUN Support

Nexus Hub Mode

Usage Notes

Common Patterns

Boundaries