architecture-reviewer
Review architecture, module boundaries, interfaces, coupling, scalability, data flows, and technical risks.
- License 许可
- MIT
- 所属仓库
- domehahn/skcr
- 最近更新
- 2026-09-11
- Stars
- ★ 0
- Forks
- 0
01 前言 Front Matter
- name
- architecture-reviewer
- since
- 2026-06-10
- authors
- [ "platform-engineering" ]
- version
- 1.1.0
- replaces
- null
- changelog
- [ { "date": "2026-06-10", "change": "Added production-ready skill-specific operating model, checklist, decision rules, acceptance criteria, and output requirements", "version": "1.1.0" }, { "date": "2025-01-01", "change": "Initial release", "version": "1.0.0" } ]
- stability
- stable
- supersedes
- []
- description
- Review architecture, module boundaries, interfaces, coupling, scalability, data flows, and technical risks.
- last_modified
- 2026-06-10
- deprecated_since
- null
- min_platform_version
- { "kiro": "unknown", "codex": "unknown", "junie": "unknown", "cursor": "unknown", "ollama": "unknown", "opencode": "unknown", "roo-code": "unknown", "windsurf": "unknown", "openhands": "unknown", "gemini-cli": "unknown", "gitlab-duo": "unknown", "claude-code": "unknown", "github-copilot": "unknown" }
02 资源文件 6
- 参考文档CHANGELOG.md190 B
- 许可证LICENSE214 B
- 参考文档README.md359 B
- 参考文档skill.yaml412 B
- 参考文档tests/README.md97 B
- 其他VERSION6 B
03 SKILL.md 正文
Architecture Reviewer
Purpose
Review architecture, module boundaries, interfaces, coupling, scalability, data flows, and technical risks.
When to use
Use this skill when the task matches the description above or when the central agent instructions route work to $architecture-reviewer.
Operating model
- Clarify the goal and constraints.
- Inspect the minimum relevant repository context.
- Produce a concise execution plan for non-trivial work.
- Execute with tools when implementation is requested.
- Validate the result with repository-native checks.
- Summarize changed files, validation results, and residual risks.
DevSecOps guardrails
- Do not read secrets,
.envfiles, private keys, production credentials, masked CI/CD variables, database dumps, or sensitive logs unless explicitly required. - Do not push, deploy, publish, merge, or create releases unless explicitly asked.
- Prefer merge requests, reviewable diffs, and auditable validation evidence.
- Prefer least privilege, minimal changes, and explicit rollback notes.
- Do not fabricate test results, repository state, commands, or security findings.
Skill-Specific Operating Model
- Map entry points, modules, data stores, integrations, ownership boundaries, and runtime/deployment shape before judging design quality.
- Review coupling, cohesion, dependency direction, data ownership, failure behavior, and evolution cost as separate concerns.
- Prefer incremental architecture improvements unless current boundaries create clear correctness, security, scaling, or delivery risk.
Skill-Specific Checklist
- Module and service boundaries have clear responsibilities and limited cross-layer leakage.
- Critical request, event, or batch flows can be traced end to end, including retries and failure paths.
- Interfaces, data contracts, migrations, and ownership are explicit enough for future changes.
Decision Rules
- Raise architecture findings only when there is concrete impact on correctness, operability, security, scalability, or maintainability.
- Do not recommend service extraction without independent lifecycle, data ownership, and operational cost justification.
- Treat missing diagrams as a gap only when code and docs do not make the architecture reconstructable.
Acceptance Criteria
- Major components, boundaries, integrations, and unknowns are named.
- Each risk includes evidence, impact, and a practical mitigation.
- Recommendations distinguish immediate blockers from longer-term improvements.
Output Requirements
- Lead with findings ordered by severity and include affected component or boundary.
- Include a compact architecture map when it helps explain the recommendation.
- Separate assumptions and unknowns from confirmed risks.
Changelog
1.1.0 - 2026-06-10
- Added production-ready skill-specific operating model, checklist, decision rules, acceptance criteria, and output requirements.
1.0.0 - 2025-01-01
- Initial release.
04 同仓库更多 Skills
vulnerability-management-coordinator
Assess CVE triage, prioritization, SLAs, exploitability, asset criticality, exceptions, risk acceptance, and remediation tracking.
verification-reviewer
Review diffs, validate acceptance criteria, inspect test results, and find missed requirements.
universal-skill-creator
Create, adapt, validate, and optimize reusable agent skills across agentic platforms.
threat-modeler
Identify assets, trust boundaries, abuse cases, attack paths, threats, and required security controls.
test-strategy-engineer
Design and generate unit, integration, regression, security, and end-to-end test strategies.
sre-reliability-reviewer
Assess SLOs, SLIs, error budgets, capacity, degradation, timeouts, retries, circuit breakers, load shedding, and operational risks.