$ loading_
扫描多项技能并提炼通用规则，自动追加、修订或新建规则文件。
复制安装指令，让 AI 自动完成配置 · 推荐新手
请帮我安装 askskill 上的 "rules-distill" 技能： 1. 下载 https://raw.githubusercontent.com/affaan-m/ECC/main/skills/rules-distill/SKILL.md 2. 保存为 ~/.claude/skills/rules-distill/SKILL.md 3. 装好后重载技能，告诉我可以用了
请扫描这个项目中的所有技能说明，找出重复出现的约束、风格要求和执行原则，整理成一份规则文件；对已有规则去重并保留更通用的表述。
一份去重后的规则文件草案，包含通用原则、修订建议和新增规则。
对比当前规则文件与最新技能定义，找出已过时、冲突或缺失的规则，并给出应追加、修改或删除的具体内容。
一份规则差异清单，以及可直接应用的更新后规则文本。
基于这组技能内容，提炼跨技能的一致性要求，生成适用于后续编写与审核的新规则文件，并按主题分组。
按主题组织的新规则文件，清楚说明每条规则的适用范围与目的。
Scan installed skills, extract cross-cutting principles that appear in multiple skills, and distill them into rules — appending to existing rule files, revising outdated content, or creating new rule files.
Applies the "deterministic collection + LLM judgment" principle: scripts collect facts exhaustively, then an LLM cross-reads the full context and produces verdicts.
The rules distillation process follows three phases:
bash ~/.claude/skills/rules-distill/scripts/scan-skills.sh
bash ~/.claude/skills/rules-distill/scripts/scan-rules.sh
Rules Distillation — Phase 1: Inventory
────────────────────────────────────────
Skills: {N} files scanned
Rules: {M} files ({K} headings indexed)
Proceeding to cross-read analysis...
Extraction and matching are unified in a single pass. Rules files are small enough (~800 lines total) that the full text can be provided to the LLM — no grep pre-filtering needed.
Group skills into thematic clusters based on their descriptions. Analyze each cluster in a subagent with the full rules text.
After all batches complete, merge candidates across batches:
Launch a general-purpose Agent with the following prompt:
You are an analyst who cross-reads skills to extract principles that should be promoted to rules.
## Input
- Skills: {full text of skills in this batch}
- Existing rules: {full text of all rule files}
## Extraction Criteria
Include a candidate ONLY if ALL of these are true:
1. **Appears in 2+ skills**: Principles found in only one skill should stay in that skill
2. **Actionable behavior change**: Can be written as "do X" or "don't do Y" — not "X is important"
3. **Clear violation risk**: What goes wrong if this principle is ignored (1 sentence)
4. **Not already in rules**: Check the full rules text — including concepts expressed in different words
## Matching & Verdict
For each candidate, compare against the full rules text and assign a verdict:
- **Append**: Add to an existing section of an existing rule file
- **Revise**: Existing rule content is inaccurate or insufficient — propose a correction
- **New Section**: Add a new section to an existing rule file
- **New File**: Create a new rule file
- **Already Covered**: Sufficiently covered in existing rules (even if worded differently)
- **Too Specific**: Should remain at the skill level
## Output Format (per candidate)
```json
{
"principle": "1-2 sentences in 'do X' / 'don't do Y' form",
"evidence": ["skill-name: §Section", "skill-name: §Section"],
"violation_risk": "1 sentence",
"verdict": "Append / Revise / New Section / New File / Already Covered / Too Specific",
"target_rule": "filename §Section, or 'new'",
"confidence": "high / medium / low",
"draft": "Draft text for Append/New Section/New File verdicts",
"revision": {
"reason": "Why the existing content is inaccurate or insufficient (Revise only)",
"before": "Current text to be replaced (Revise only)",
"after": "Proposed replacement text (Revise only)"
}
}
```
## Exclude
- Obvious principles already in rules
- Language/framework-specific knowledge (belongs in language-specific rules or skills)
- Code examples and commands (belongs in skills)
…
通过双评审智能体对结果进行对抗式校验，提升输出发布前的可靠性
为 AI 编码助手提供 Rust 编写规则，提升代码质量与一致性。