菜单
Review diffs for over-engineering only. One line per finding: location, what to cut, what replaces it. Hard gate before /review in aiops delivery. Use when the user says prune, simplify review, what can we delete, or over-engineered.
用 Codex 或 Claude 帮你安装 复制这段 Prompt，粘贴到 Codex、Claude 或其他助手里，让它检查 Skill 页面并帮你完成安装。
| name | prune |
| description | Review diffs for over-engineering only. One line per finding: location, what to cut, what replaces it. Hard gate before /review in aiops delivery. Use when the user says prune, simplify review, what can we delete, or over-engineered. |
Hunt unnecessary complexity in the diff. One line per finding. Goal: shorter diff.
L<line>: <tag> <what>. <replacement>.
Tags: delete, stdlib, native, yagni, shrink
End with net: -<N> lines possible. or Lean already. Ship.
Complexity only — correctness and security belong in /review. Pre-delivery constraint: /lean. List cuts; do not apply unless asked.
基于 SOC 职业分类
Delivery overlay — orchestrates lean ladder, tdd, prune, review with sub-phase gates; commits only on user approval.
Flow Conductor for the aiops bundle. One entry — infers task type, shows plain-language steps, tracks journey in flow.state.yaml, dispatches skill + agent per phase.
Structured design process for the architect agent. Guides from grill conclusions to complete NOTES.md + tech-spec.md plus needed domain documentation updates through constraint gathering, module identification, interface design, alternative exploration, and risk analysis. Use when the architect needs to produce design decisions and technical specifications.
Build and query a persistent code graph for the target project. Uses graphify (Tree-sitter + Louvain clustering) for deterministic structural extraction, then the model adds semantic annotations. Use when the user says build graph, code graph, dependency graph, impact analysis, or when other skills need structured code understanding before proceeding.
Scan a codebase for deepening opportunities, present them as a visual HTML report, then grill through whichever one you pick. Use when the user says architecture review, codebase health, deepening, refactor suggestions, or complains about architectural friction.
Review in three modes — code (diff vs standards/spec), design (NOTES + tech-spec before planning), drift (implementation vs tech-spec before ship). Pick mode from Flow Conductor phase or user intent; do not mix artifact types.
