Agent Skills › harumiWeb/exstruct › adr-reviewer

adr-reviewer

GitHub

审查ADR草案的决策质量、重叠性、证据强度及风险。仅在linter无未解决高/中问题时执行，识别需人工介入的决策，输出ready/revise/escalate结论及详细发现。

.agents/skills/adr-reviewer/SKILL.md harumiWeb/exstruct

触发场景

需要合并或交接前进行设计审查 adr-linter报告当前草稿无未解决的高/中优先级问题

安装

npx skills add harumiWeb/exstruct --skill adr-reviewer -g -y

更多选项

非标准路径

npx skills add https://github.com/harumiWeb/exstruct/tree/main/.agents/skills/adr-reviewer -g -y

不安装直接使用

npx skills use harumiWeb/exstruct@adr-reviewer

指定 Agent (Claude Code)

npx skills add harumiWeb/exstruct --skill adr-reviewer -a claude-code -g -y

安装 repo 全部 skill

npx skills add harumiWeb/exstruct --all -g -y

预览 repo 内 skill

npx skills add harumiWeb/exstruct --list

SKILL.md

Frontmatter

{
    "name": "adr-reviewer",
    "description": "Review an ExStruct ADR draft for decision quality, overlap with existing ADRs and specs, evidence strength, rollout risk, and human-ownership escalations. Use only after adr-linter reports no unresolved high\/medium findings on the current draft, and when you need design-review findings before merge or handoff."
}

ADR Reviewer

Review the policy decision, not just the document shape.

Read

dev-docs/agents/adr-governance.md
dev-docs/agents/adr-criteria.md
dev-docs/agents/adr-workflow.md
dev-docs/specs/adr-review.md
The target ADR draft
Related ADRs, relevant public docs under docs/ when public API / CLI / MCP contracts are in scope, internal specs, tests, src paths, and issue / PR context
Existing adr-linter findings for the current draft

Workflow

Confirm the current draft has no unresolved adr-linter high / medium findings. Only proceed with design review after that precondition is met.
Read the ADR draft and identify the single policy question it is trying to resolve.
Check whether the draft overlaps with, contradicts, or should supersede an existing ADR or spec.
Verify that the cited Tests, Code, and Related specs actually support the claims being made, and include relevant public docs/ pages in scope when the ADR touches public API / CLI / MCP contracts.
Review whether compatibility, rollout, fallback, migration, or safety consequences are covered when relevant.
Detect human-owned decisions that AI should not settle, including public API break judgment, security or license calls, major directory reorganization, or unresolved product/spec direction.
Return one verdict:
- ready
- revise
- escalate

Output Contract

Return findings first, ordered by severity, and include:

verdict
scope
- draft
- related ADRs
- public docs
- specs
- src
- tests
- issue / PR context
findings

Each finding should include:

type
- decision-gap
- scope-conflict
- evidence-risk
- rollout-gap
- ownership-escalation
severity
summary
why it matters
suggested revision
evidence
- draft
- related sources