AGENT SKILL
archi-full
Run or read full-project architecture analysis and summarize structural weaknesses, hotspots, and maintainability risks.
- License 许可
- Apache-2.0
- 最近更新
- 2026-08-14
- Stars
- ★ 19
- Forks
- 2
01 前言 Front Matter
- name
- archi-full
- description
- Run or read full-project architecture analysis and summarize structural weaknesses, hotspots, and maintainability risks.
03 SKILL.md 正文
Archi Full
Use this skill for full-project baseline architecture review.
Workflow
- Inspect the available architecture-analysis command shape before assuming flags.
- Use
archi-evidence-mapwhen deciding whether to use Architec/Hippo, dependency graphs, architecture tests, Semgrep, CodeQL, or direct review. - Run or read full-project architecture review evidence only when available or requested.
- Refresh structural inputs only when the user asks for fresh evidence, the snapshot is stale, or stale evidence is central to the question.
- Read project docs, module maps, dependency rules, and representative source paths directly.
- Route focused findings to
archi-dependency-topology,archi-module-boundaries,archi-fitness-functions,archi-decision-drift,archi-change-impact, orarchi-distributed-systemswhen the baseline needs that method. - Use vendored
improve-codebase-architecturewhen the review is looking for deep-module, seam, adapter, leverage, locality, or interface-depth opportunities. - Use vendored
code-review-and-qualitywhen the baseline needs adjacent correctness, security, performance, or review-quality coverage. - Read
.architec/architec-summary.mdfirst when present. - Use
.architec/architec-analysis.jsonfor exact scores, concerns, signals, hotspots, and artifact paths.
Output
Score
- overall:
- key reading:
Problems
- ...
Improvements
- ...
Verification
- ...
Do not turn full review into task-goal planning. Use archi-advice when the
user wants a refactor roadmap.
If the tool baseline is missing, produce a source-backed baseline with an explicit "tool evidence unavailable" note.
04 同仓库更多 Skills
example-skill
暂无简介
★ 19
su-status
从 docs 人读真相源与 .ccb 协调件读取当前项目、Requirement 或子任务状态。
★ 19
su-revise-breakdown
根据用户反馈重写 Requirement breakdown draft。
★ 19
su-review
审查执行回执、diff 和验证证据,决定通过、返工、replan 或升级用户。
★ 19
su-resume
从 docs 人读真相源与 .ccb 协调件恢复 paused/deferred/in-progress 主体的上下文。
★ 19
su-reconcile
AI-native 自检 docs 人读真相源、.ccb 协调件与 Console 投影漂移,并按审批结果执行修复。
★ 19