wp-project-triage
Use when you need a deterministic inspection of a WordPress repository (plugin/theme/block theme/WP core/Gutenberg/full site) including tooling/test…
它会碰到什么
扫了多少3 个文本文件，25 KB
它会碰到什么读文件联网
命中总数11 处
命中统计严重 0 · 高 0 · 中 10 · 低 1
这一栏是扫描器报的事实，不是结论。命中多不等于有毒（安全工具、规则库、示例脚本本来就会包含危险写法），命中少也不等于干净。它和你手上的凭据、文件、网络有什么关系，需要你自己看。
技能内容
WP Project Triage
When to use
Use this skill to quickly understand what kind of WordPress repo you’re in and what commands/conventions to follow before making changes.
Inputs required
- Repo root (current working directory).
Procedure
- Run the detector (prints JSON to stdout):
node skills/wp-project-triage/scripts/detect_wp_project.mjs
- If you need the exact output contract, read:
skills/wp-project-triage/references/triage.schema.json
- Use the report to select workflow guardrails:
- project kind(s)
- PHP/Node tooling present
- tests present
- version hints and sources
- If the report is missing signals you need, update the detector rather than guessing.
Verification
- The JSON should parse and include:
project.kind,signals, andtooling. - Re-run after changes that affect structure/tooling (adding
theme.json,block.json, build config).
Failure modes / debugging
- If it reports
unknown, check whether the repo root is correct. - If scanning is slow, add/extend ignore directories in the script.
想直接用这个技能？
本站把开放许可（MIT / Apache 等）的技能按仓库打包整理到网盘，点一下转存到你自己的网盘，不用一个个从 GitHub 拉。许可未声明的技能只给原始仓库链接，不打包。