adonis0123/code-inspector-init
skills/code-inspector-init/SKILL.md
Set up or migrate code-inspector-plugin across modern frontend frameworks. Use when you need click-to-source IDE navigation, hotkey customization, or inspector troubleshooting.
$ install --global
skillsauthnpx skillsauth add adonis0123/adonis-skills code-inspector-initInstall 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: Mar 30, 2026, 6:15 PM63.2s4 files scanned
SKILL.md
- name:
- code-inspector-init
- description:
- Set up or migrate code-inspector-plugin across modern frontend frameworks. Use when you need click-to-source IDE navigation, hotkey customization, or inspector troubleshooting.
- author:
- adonis
Code Inspector Init
Overview
在开发环境为前端项目接入 code-inspector-plugin，实现按组合键后点击 DOM 跳转到源码位置。优先给出最小改动、可复制、可回滚的迁移方案，默认使用插件原生开关策略：needEnvInspector: true + .env.local 中设置 CODE_INSPECTOR=true；但 Next.js >=15.3 主模板默认使用 hotKeys: ["altKey"] + needEnvInspector: false。
Trigger Phrases
- 帮我接入
code-inspector-plugin - 帮我迁移
codeInspectorPlugin到新项目 - Next.js/Vite/Webpack 怎么配 code inspector
- 点击页面元素跳不到 IDE
- Alt+Shift 没反应 / 快捷键怎么改
Decision Tree
- 识别框架与 bundler。
- 从
package.json、配置文件名、构建命令确认是 Next.js、Vite、Webpack、Rspack、Rsbuild、Esbuild、Mako、Umi、Nuxt、Astro 中哪一种。
- 如果是 Next.js，先判断版本区间。
<=14.x：使用 webpack 插件接入。15.0.x ~ 15.2.x：使用experimental.turbo.rules。>=15.3.x（包含 16）：使用turbopack.rules。
- 选择开关策略。
- 默认：
needEnvInspector: true（推荐，迁移一致性最好）。 - Next.js
>=15.3主模板特例：默认needEnvInspector: false，并使用hotKeys: ["altKey"]做最小接入。 - 用户明确要求项目自定义开关时，再补充
ENABLE_CODE_INSPECTOR等外层条件。
- 判断是否需要高级选项。
- 只有用户明确提出需求才调整
hotKeys、hideConsole、openIn、launchType、include/exclude、mappings、pathType、skipSnippets。
Execution Workflow
- 识别项目环境。
- 确认框架、bundler、配置文件路径、是否 dev-only 配置。
- 安装依赖。
- 给出单行命令：
pnpm add -D code-inspector-plugin（如项目使用 npm/yarn，则给对应命令）。
- 注入配置。
- 从
references/bundler-recipes.md选择对应片段。 - 配置中必须包含正确的
bundler值。
- 设置
.env.local。
- 仅当模板显式使用
needEnvInspector: true时，添加CODE_INSPECTOR=true。 - 对 Next.js
>=15.3主模板（hotKeys: ["altKey"]+needEnvInspector: false）不强制配置.env.local。
- 本地验证。
- 启动 dev。
- 在页面按默认组合键（多数模板为 Mac:
Option+Shift/ Windows:Alt+Shift；Next.js>=15.3主模板为Option/Alt单键）后悬浮并点击 DOM。 - 观察浏览器控制台提示和 IDE 跳转结果。
- 故障排查。
- 出现 IDE 无法打开、快捷键无效、路径错误、端口冲突时，按
references/troubleshooting.md分步排查。
Reference Routing
- 需要框架配置代码片段时：读取
references/bundler-recipes.md。 - 需要定制参数与风险评估时：读取
references/options-cheatsheet.md。 - 需要排障步骤时：读取
references/troubleshooting.md。 - 不要一次性加载全部 references，只按当前请求场景读取对应文件。
Output Contract
输出必须严格包含以下四部分，且顺序固定：
- 改动点清单
- 说明要改哪些文件、每个文件做什么。
- 可复制代码块
- 给完整可用的配置片段，不给伪代码。
- 代码块里保留英文 API 名与配置键。
- 验证命令
- 提供可直接执行的单行命令。
- 给出成功判定标准。
- 回滚说明
- 说明如何移除插件配置和环境变量。
Guardrails
- 默认只在开发环境启用，不在生产构建开启 inspector。
- 修改保持最小化，不顺带重构无关代码。
- 不确定框架版本时，先读取
package.json与 lockfile 再下结论。 - 涉及
node_modules源码映射时，优先使用mappings且给出风险说明。
Related Skills
adonis0123/code-plugin-architecture
tools
VerifiedTrustedCommunity
Use when the user's pain is "adding/removing one more X means editing N files" and X is a recurring variant kind: popup, banner, modal, ad slot, payment method, AI model/tool, form field type, connector, sub-site, command, menu item, agent, extension point, or data source. Use when they want to design, refactor, review, name, or explain a pluggable mechanism using registry, interface/trait contract, runtime core, and convention folders; mention pluginize, pluggable, plugin architecture, extension point, registry pattern, or extensibility. Use when explaining the first-principles rationale, DDD/SOLID/OCP mapping, or industry analogies behind that structure. Use for cross-stack mapping to VSCode contributes, Webpack/Vite plugins, Rust/Tauri connectors, Python entry_points, or cargo features. Skip one variant's internals/styles/hooks/copy/bugs, and skip register/registry meaning DI container, user signup, or package registry.
2SKILL.mdUpdated May 30, 2026
adonis0123/workflow-gate
development
VerifiedTrustedCommunity
Use BEFORE heavier workflow skills when route choice matters. Route creative work without a design doc/spec to Brainstorm; destructive or hard-to-reverse work to Discuss; unresolved decisions, Plan/Full fan-out, ship checks, unclear bugs, and fresh-eyes fix-then-re-review need this gate. Skip single-line read-only lookups, pure typo/formatting edits, trivial safe one-line fixes, and clearly safe named-skill requests. Outputs Route, Runtime skill, Fallback alias, and Execution path.
2SKILL.mdUpdated May 17, 2026
adonis0123/agentic-review-handoff
development
VerifiedTrustedCommunity
Cross-agent code review handoff and review-fix-re-review loop with persistent packet artifacts. Requires a git repo because packet addressing uses git rev-parse --show-toplevel. Use when the user asks for an independent, read-only second pair of eyes on a diff/branch/PR another agent or teammate implemented; asks to verify reviewer feedback before fixing; says a fix is done and wants scoped re-review; asks to continue the latest review packet; or asks for first-principles, DDD, high-cohesion/low-coupling review. Persists each loop under $repo_root/.review-handoff/active/ so agents can resume without copy-paste. Do NOT use for ordinary implementation, generic staged-change review, review-comment copy editing, non-git folders/zips/tarballs/temp dirs, or when the user names a different review skill.
2SKILL.mdUpdated May 16, 2026
adonis0123/discuss-before-plan
testing
VerifiedTrustedCommunity
Enforces 'decide then plan' discipline - the pre-planning decision gate. Use when the user asks for a plan or starts a change while key decisions are unresolved: architecture tradeoffs, data flow, public interfaces, unclear requirements, multi-module scope, or roughly 5+ files affected. Also triggers when the user explicitly wants to discuss, compare options, or review architecture before committing. Core job: reduce incorrect-execution cost by confirming decisions before producing executable plans.
2SKILL.mdUpdated Mar 27, 2026