hicaosen/feature-explorer
plugins/feature-explorer/skills/feature-explorer/SKILL.md
This skill should be used when the user asks to "explain how X works", "how does X work", "what is the implementation of X", "trace the code for X", "show me the call chain of X", "how is X implemented", "how does the X module work", "what's the design of X", "walk me through X", "explain the X feature", "what does X do", "how is X built", "解释一下 X 是怎么实现的", "帮我分析 X", "梳理一下 X 的设计", "X 的调用链是什么", "X 的代码流程是什么", or mentions understanding, analyzing, or exploring a feature, function, module, mechanism, or design in a codebase. Also triggers when the user asks about the architecture, flow, or internal workings of a component. Provides a structured analysis of how a feature is implemented. Do NOT use for debugging, bug fixing, or modifying code -- only for understanding and explaining.
development
Updated Apr 28, 2026
$ install --global
skillsauthnpx skillsauth add hicaosen/skills feature-explorerInstall this skill globally with one command. Works with Claude Code, Cursor, and Windsurf.
Security Scan Results
3 of 9 scanners reported clean
Some scanners were skipped, did not run, or reported a non-clean status. Review each row below.
3
Scanners Passed
9
Scanners in report
Clean
TrivyContainer and dependency vulnerability scanner
95%
Clean
SemgrepStatic code analysis for vulnerabilities
95%
Clean
mcp-scan (Snyk)Model Context Protocol security validation
95%
Skipped
Snyk (dep)Open source security scanning
50%
Skipped
Socket.devSupply chain security analysis
50%
Skipped
VirusTotalMulti-engine malware detection
50%
Skipped
CrowdStrikeAdvanced threat intelligence
50%
Skipped
OSV-ScannerOpen Source Vulnerability database check
50%
Skipped
OWASP Dep-Check
50%
Last scanned: Apr 28, 2026, 3:48 AM149.5s1 file scanned
SKILL.md
- name:
- feature-explorer
- description:
- >-
Objective
Analyze the implementation of a specified feature in a codebase and produce a structured exploration report.
Target
$ARGUMENTS
Exploration Process
Phase 1: Locate Entry Points
- Use Glob and Grep to search for relevant files, functions, and classes based on the target keyword.
- Identify entry points: API endpoints, CLI commands, event listeners, exported functions, etc.
- If the target is ambiguous (e.g. "the auth system"), list candidate entry points and pick the most relevant one.
- If no relevant code is found, report this clearly rather than forcing an analysis.
Phase 2: Trace the Call Chain
Starting from the entry point, trace function calls layer by layer:
- Record each key function with file_path:line_number
- Summarize what each function does in one sentence
- Identify branching paths (conditional logic that splits execution)
- Stop at the project's own code boundary — when a call enters a third-party library or framework, note the boundary and move on. Do not trace into library internals.
- Keep the call chain to a maximum of 7 levels deep. Fold deeper nesting into "...".
Phase 3: Map Data Flow
- Identify data sources: user input, database, config, external API
- Track data transformations and processing steps
- Identify data destinations: response, storage, side effects
Phase 4: Identify Key Design Decisions
- Identify design patterns in use
- Document important abstractions and interfaces
- Describe the error handling strategy
- Note concurrency/async handling (if applicable)
Output Format
Use this structure for the report:
## Overview
<2-3 sentences summarizing what this feature does and why it exists>
## Call Chain
<Show call relationships with indentation or arrows, annotated with file paths and line numbers>
## Data Flow
<Describe data sources, transformations, and destinations>
## Key Design Decisions
<List important design choices and patterns>
## Files
<Bulleted list of all key file paths (no line numbers — see call chain for those)>
Constraints
- Read-only exploration — do not modify any files.
- Every key reference must include
file_path:line_number. - Focus on the core happy path. If the feature is complex, prioritize the primary flow over edge cases.
- Output language must match the user's query language.
Related Skills
hicaosen/victoriatraces-api
development
VerifiedTrustedCommunity
VictoriaTraces HTTP API reference for querying distributed traces via Jaeger-compatible API. This skill should be used when searching traces, listing services/operations, getting trace details by ID, querying service dependencies, constructing HTTP requests to VictoriaTraces, or working with Jaeger API endpoints for distributed tracing analysis.
SKILL.mdUpdated Apr 28, 2026
hicaosen/victoriametrics-api
development
VerifiedTrustedCommunity
VictoriaMetrics HTTP API reference for querying metrics, exporting/importing data, TSDB stats, and administrative operations. This skill should be used when constructing HTTP requests to VictoriaMetrics, understanding query endpoints (/api/v1/query, /api/v1/query_range, /api/v1/export, /api/v1/import), response formats, checking cardinality, creating snapshots, or integrating with VictoriaMetrics API.
SKILL.mdUpdated Apr 28, 2026
hicaosen/victorialogs-api
development
VerifiedTrustedCommunity
VictoriaLogs HTTP API reference for querying logs, hits stats, field discovery, live tailing, and log statistics. This skill should be used when constructing HTTP requests to VictoriaLogs, understanding query endpoints (/select/logsql/query, /select/logsql/tail, /select/logsql/hits, /select/logsql/field_names), response formats, or integrating with VictoriaLogs API for log search and analysis.
SKILL.mdUpdated Apr 28, 2026
hicaosen/promql
testing
VerifiedTrustedCommunity
PromQL query language fundamentals for Prometheus and Prometheus-compatible systems. Use for understanding PromQL instant/range vectors, label matchers, aggregation operators, offset/@ modifiers, or when targeting non-VictoriaMetrics Prometheus systems. For VictoriaMetrics-specific features like default_rollup, rollup, or outlier detection, use the metricsql skill.
SKILL.mdUpdated Apr 28, 2026