开发与测试
maintenance-rules
Maintenance rules for the skill-forge repo. MUST run Decision Test before accepting changes. MUST update platform-registry when platforms change. MUST keep SKILL.md under 500 lines. MUST verify cross-file consistency after changes. Triggers on "update skill-forge", "maintain skill-forge", "refresh platform registry", "check community tools".
motiful · 已有静态检查记录
安装与使用
运行命令前先阅读来源与依赖说明。复制命令不会自动安装或执行。
npx skills add motiful/skill-forge --skill maintenance-rules技能说明
name: maintenance-rules description: 'Maintenance rules for the skill-forge repo. MUST run Decision Test before accepting changes. MUST update platform-registry when platforms change. MUST keep SKILL.md under 500 lines. MUST verify cross-file consistency after changes. Triggers on "update skill-forge", "maintain skill-forge", "refresh platform registry", "check community tools".' metadata: author: motiful
skill-forge Maintenance Rules
Constraints and procedures for maintaining the skill-forge repository.
Execution Procedure
maintain(trigger) → updated | no_change
if "platform registry" in trigger:
update_platform_registry()
update_downstream() # SKILL.md Fix Phase, README install, Detection logic
if "community tools" in trigger:
update_community_tools()
if change proposed:
run_decision_test() # 7 criteria → accept | reject
verify_constraints() # each MUST's parenthesized method
run_consistency_checks()
update_changelog() # max 5, trim oldest
after significant changes:
run_self_governance() # 4 steps
Constraints
- MUST run Decision Test (7 criteria below) before accepting any change
- MUST NOT push SKILL.md body over 500 lines
- MUST keep SKILL.md ↔ README ↔ references terminology consistent
- MUST add References section entry when adding new reference files
- MUST update "Dependencies" table in README when SKILL.md dependencies or setup.sh changes
- MUST NOT include content that fails the Positional Test (see references/skill-format.md)
- MUST verify reference files follow three-layer format (frontmatter + EP + aligned Content)
- MUST keep examples in standard-defining references generic — no skill-forge-specific labels in universal patterns
- MUST verify SKILL.md pseudocode function names align with sub-module EP entry signatures (run: grep function names from references/ EPs, diff against SKILL.md pseudocode calls)
- MUST verify lossless delegation when moving inline criteria to a sub-module: map every deleted parent line to a sub-module EP line. Unmapped criteria → add to sub-module first, then remove from parent (run: diff parent before/after, match each removed line to a sub-module line)
- MUST verify every defined standard has a corresponding enforcement check in Validation (Structure, Quality, or Publishing). A standard without a check is dead weight — either add the check or remove the standard
Platform Registry Updates
- Open
references/platform-registry.md - For each platform, check Docs link for: user-level paths, project-level paths, shared compat directories, link validity
- Search: "agent skills directory [platform name] 2026" for new platforms
- Distinguish: vendor-native paths vs compat-scanned paths vs custom locations
- Only actual skill roots count as strong signals (not bare parent dirs)
- Treat Gemini CLI as adjacent tooling unless official docs add Agent Skills directory support
- Update paths + "Last verified" date
- Keep platform facts separate from forge behavior
- If path changes affect SKILL.md Fix Phase, README install examples, or Detection logic, update those too
- If README writing guidance changes, update both
references/templates.mdandreferences/readme-quality.md - Add changelog entry (keep max 5, trim oldest)
Community Tools Updates
- Check
npx skills add— still maintained? New features? - Check
skills-ref validate— new validation rules? Keep as optional, not required dependency - Check skills.sh FAQ before making visibility claims. Installability ≠ directory/leaderboard visibility
- Update Community Tools table in
references/platform-registry.mdif needed
Contribution Criteria
Use the Decision Test:
- Does it help users' skills score higher on the 6 quality dimensions?
- Is it simple enough that an AI agent will reliably follow it?
- Can it be expressed as prompts instead of scripts?
- Does it impose an architectural opinion most skills don't need?
- Is it a platform or infrastructure concern, not skill quality?
- Does the ecosystem actually use this pattern?
- Do we practice it ourselves?
Accept when: yes, yes, yes, no, no, yes, yes. Wrong answers need justification.
PR hygiene:
- Changes to SKILL.md must not push body over 500 lines
- New reference files need a SKILL.md References entry
- Terminology changes must be consistent across SKILL.md, README.md, and all affected references
Self-Governance
skill-forge validates other skills. It must also pass its own validation.
Protocol (run after significant changes):
- Run skill-forge Review on this repo
- Every README claim must be backed by a SKILL.md capability
- Every reference listed in SKILL.md must exist and be current
- Version in frontmatter, README badge, and changelog must agree
Consistency Checks
- SKILL.md description matches README positioning
- README "Dependencies" table matches SKILL.md Step 0 + setup.sh
- No residual terminology from previous versions: "five-layer", "Kit", "JIT", "Enhancement Report", "Quick Review", "Full Pipeline", "Multi-Skill Triage", "Scenario 1/2/3/4/5", "Operation Modules", "Step Reference", "Output Checklist", "Content Audience Check", "Interface" (as reference layer name), "Header" (as reference layer name), "Teaching" (as layer name), "Directing" (as layer name), "Review" (as independent EP entry name), "Create" (as independent EP entry name), "Push" (as independent EP entry name), "review_plan()", "update_plan()", "close_plan()", "checkpoint()", "content block" (replaced by "paragraph"), "register_locally()" (replaced by "detect_and_register()" per platform-registry.md EP), "read_repo_meta()" (replaced by Skill("readme-craft", "apply metadata") — github-metadata migrated to readme-craft), "lookup()" (replaced by "detect_and_register()"), "validate(repo_meta)" (replaced by S