architecture-audit
Skill2 starsChanged 10 months agoMITView on GitHub
架構文件稽核。比對 CLAUDE.md 記錄與實際程式碼結構,找出差異並建議更新。大型 refactor 完成後或 OpenSpec 歸檔時手動執行。
Files
Architecture Audit (架構文件稽核)
When to Use
在以下情況使用此 Skill:
- 大型 refactor 完成後
- OpenSpec 歸檔時
- 新增/刪除多個檔案後
- 手動執行
/architecture-audit
稽核流程
Step 1: 讀取 CLAUDE.md
cat CLAUDE.md確認文件存在。若不存在,建議先建立。
Step 2: 掃描實際結構
# 前端
ls -R src/ | head -100
# 後端
ls -R *.py **/*.py | head -100
# 路由數量
grep -c "path:" src/router/index.ts 2>/dev/null || trueStep 3: 比對差異
檢查以下項目:
| 項目 | 方法 |
| 新增的目錄/檔案 | 實際有但 CLAUDE.md 未記錄 |
| 刪除的目錄/檔案 | CLAUDE.md 記錄但實際已不存在 |
| 路由數量 | CLAUDE.md 記錄數 vs 實際數 |
| 依賴版本 | package.json/requirements.txt vs CLAUDE.md |
| 元件數量 | 實際元件數 vs CLAUDE.md 記錄 |
Step 4: 輸出報告
架構稽核報告
===========
專案: {project_name}
日期: {date}
差異:
+ src/views/NewPage.vue (未記錄)
- src/views/OldPage.vue (已刪除)
~ 路由數量: 文件記 22, 實際 25
建議更新:
1. CLAUDE.md 目錄結構段落加入 NewPage
2. 移除已刪除的 OldPage 記錄
3. 更新路由數量為 25Step 5: 使用者確認後更新
- 使用者確認 → 直接更新 CLAUDE.md
- 使用者拒絕 → 跳過
CLI 指令
# 快速檢查
dash architecture check .
# 詳細差異
dash architecture diff .
# 全專案掃描
dash architecture check --all注意事項
- 此 skill 不修改程式碼,只更新文件
- CLAUDE.md 的目錄結構是參考,不需要列出每個檔案
- 重點放在結構性變化(新增/刪除目錄、路由數量、依賴版本)
Other versions14 projects use a version of this.
Word for word · 0
None found.
Edited · 0
None found.
Wrote their own version · 14
- RBraga01/a-team★ 24same name
- helderberto/agent-skills★ 19same name
- Suge8/friedbun★ 9same name
- BrentRector/claude-skills★ 5same name
- creativedeals/free-claude-skill-architecture-audit★ 4same name
- gootf/software-agent-sop★ 2same name
- InsightStudio-2026/agent-assets★ 1same name
- MKAbuMattar/skills★ 1same name
- nelantone/cognivia★ 1same name
- theDRElabs/opencode-config★ 1same name
4 more not listed
How matches are found. Word for word: the exact same text. Edited: shares passages with this file (“99% same” means 99% of its five-word phrases also appear here; 10% or more counts). Their own version: similar meaning, or, weakest, the same name. We can’t tell which project had it first. Projects are counted among the 200 most-starred candidates, and mentions are links to the repository we found, up to 50 per site, so both counts are a floor.
Used alongsideProjects with it also use prototype, review and 1 more.
Other files people use alongside this one.
Files found in the same public projects as a version of this one, more often than they turn up anywhere else. Each project counts once, large collections count for less, and this file's own repository is left out.
GoogleSkillprototype
Build a throwaway prototype to answer a design question. Use when the user wants to sanity-check whether a state model or logic feels right, or explore what a UI should look like.
Also in 3 projects that use this
SentrySkillreview
Fixture review skill.
Also in 3 projects that use this
GoogleSkilltdd
Test-driven development. Use when the user wants to build features or fix bugs test-first, mentions "red-green-refactor", or wants integration tests.
Also in 3 projects that use this
In this repository14 other files it gives its agents.
- pi-agent/AGENTS.mdAGENTS.md
- angular-primengSkill
- build-error-resolverSkill
- cis-design-systemSkill
- doubt-driven-developmentSkill
- fastapi-patternsSkill
- interview-meSkill
- openspecSkill
- quality-gateSkill
- refactor-cleanerSkill
- security-radarSkill
- security-reviewerSkill
- security-scanSkill
- sketchSkill
Does it work?
Reviews from people and from AI agents that ran it: what they used it for, and whether it worked.
Reviews can't be read right now.
Your trail
Files you open will collect here, so you can find them again.
Open two or more, and you can remix the rules you like from each into one list. Kept in this browser only.
Now do this for your own.
Bring your CLAUDE.md, AGENTS.md or skills. agentleFS shows which of your rules are common, which are yours and which only fit one project, and keeps one version your agents read everywhere.

