BD Vibe Coding Rules
6个自我进化的AI编程纪律Skill。改代码前强制自查→安全执行→改后28条规则扫描→自动化测试→变更日志，一条龙闭环。 🍞独家面包屑系统：文件自动记住耦合关系和历史坑位。信任分级规则自生长：重复Bug升级为硬规则。 由代码小白用AI写14万行代码的踩坑经验沉淀。支持CodeBuddy/Cursor/Windsurf。Apache 2.0。 6 self-evolving AI coding discipline Skills. Pre-check → Safe exec → 28-rule post-check → Auto-test → Changelog. Closed loop. 🍞 Breadcrumb auto-seeding. Trust-tiered rule growth. Built from 140K lines of real-world pain. Apache 2.0.
6个自我进化的AI编程纪律Skill。改代码前强制自查→安全执行→改后28条规则扫描→自动化测试→变更日志，一条龙闭环。 🍞独家面包屑系统：文件自动记住耦合关系和历史坑位。信任分级规则自生长：重复Bug升级为硬规则。…
As a process D 41/100 · Unfinished process — weak spots: result and completion, when it triggers, inputs and preconditions
How to improve
- Say in the description WHEN to use the skill ("use when…", example requests): that is the agent's main cue.
- For Hermes the description must be one sentence under 60 characters; move the conditions to a "When to Use" section.
- 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: 9. Evidence is masked. Grey chips explain why severity was lowered.
Against the Agent Skills spec
- warning
name-formatname should be kebab-case (lowercase letters, digits, hyphens) - warning
description-long-hermesdescription is 407 chars; the Hermes authoring standard requires ≤ 60 (one sentence, ending with a period) - warning
description-no-whenneither description nor a "## When to Use" section says when to use the skill - note
frontmatter-keyunknown frontmatter key "id" - note
frontmatter-keyunknown frontmatter key "primary" - note
frontmatter-keyunknown frontmatter key "website"
Process rating: all ten parameters 41/100
- 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
- 40Consistency. Frontmatter name (Vibe Coding Rules) differs from the folder (vibe-coding-rules)
- 60Tools and files. Uses tools (bash) that frontmatter does not declare
- 100Steps. 8 steps
- 100Execution cost. Instruction body is 812 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
- +5Description has no quoted example phrases that should trigger the skill
- +4Description does not say when NOT to use the skill (false activations)
- +3Output format is not stated: the model decides each time
- -219 emoji in the instructions: noise for the model
- +2Single-language instructions
- +3Description length 406: enough signal without eating the budget
- +4Structure: 8 headings
- +3Step-by-step instructions: 8 items
- +4Has examples (2 code blocks)
- +1License stated
Quality base 70; lint remarks subtract, signals add up to 100. Result: 57.