BF archunit-architecture-guard
扫描既有 Java/Kotlin 工程，识别其架构模式（分层/MVC、DDD、六边形/端口适配器、整洁架构、按功能分包/模块化单体、或 Android MVVM），报告架构坏味道并给出具体修复指导，再生成 ArchUnit 守护测试把"应有的架构"固化下来，使后续（通常是 AI 生成的）代码无法让它腐烂。当用户想要"守护/约束/保护/测试"某个 Java/Kotlin 工程的架构、提到 ArchUnit、架构适应度函数（architecture fitness function）、依赖规则、越层、包循环、架构腐烂（architecture erosion/rot），或想阻止 AI 生成的代码破坏既有设计时，使用本 Skill。当用户问"这个工程用的什么架构""我的架构干净吗"，或想给一个被 AI 反复修改的代码库加护栏时，也应触发。
扫描既有 Java/Kotlin 工程，识别其架构模式（分层/MVC、DDD、六边形/端口适配器、整洁架构、按功能分包/模块化单体、或 Android MVVM），报告架构坏味道并给出具体修复指导，再生成 ArchUnit 守护测试把"应有的架构"固化下来，使后续（通常是 AI…
As a process F 35/100 · Will not run — References files that are not bundled: references/pattern-detection.md, references/smell-catalog.md, references/archunit-cookbook.md
How to improve
- Say in the description WHEN to use the skill ("use when…", example requests): that is the agent's main cue.
- The text references files that are not there: add them or drop the references.
- Your own cases (evals/evals.json, 4–6 real requests with expected answers): the full check would then run those instead of a model-drafted suite.
- A spec.yaml with trigger phrases and assertions — a behaviour contract for CI; `skilltest init` writes a template.
Guard findings · 0
✓ No critical or high findings
Files scanned: 0. Evidence is masked. Grey chips explain why severity was lowered.
Against the Agent Skills spec
- warning
description-no-whendescription does not say WHEN to use the skill (no "use when") - warning
missing-refreference to a missing file: references/pattern-detection.md - warning
missing-refreference to a missing file: references/smell-catalog.md - warning
missing-refreference to a missing file: references/archunit-cookbook.md
Process rating: all ten parameters 35/100
- 0Tools and files. 3 referenced file(s) missing: references/pattern-detection.md, references/smell-catalog.md, references/archunit-cookbook.md
- 0Result and completion. Does not say what the result is
- 0Inputs and preconditions. Does not say what the process needs to start
- 0Failures and branches. Linear process with no failure handling
- 0Progress reporting. Says nothing while it works
- 20When it triggers. No condition that starts the skill
- 100Steps. 58 steps
- 100Consistency. Name and required fields are in place
- 100Execution cost. Instruction body is 1536 tokens
- 100Running it twice. No mutating operations
Everything here is measured from the skill text rather than judged by a model, so the numbers are checkable. A parameter weighs more when it is a more common reason for the process to stall.
Quality signals
- +4Description does not say when NOT to use the skill (false activations)
- +3Output format is not stated: the model decides each time
- +4No input/output examples
- +1No license
- +2Single-language instructions
- +5Description quotes 3 example trigger phrases
- +3Description length 371: enough signal without eating the budget
- +4Structure: 10 headings
- +3Step-by-step instructions: 58 items
Quality base 70; lint remarks subtract, signals add up to 100. Result: 61.