菜单
Keep SPEC.md authoritative for RPM contract-affecting changes. Use when code, reviews, or tickets may affect CLI behavior, lockfiles, manifests, semver, registry/cache/install/linking behavior, scripts, or diagnostics.
用 Codex 或 Claude 帮你安装 复制这段 Prompt，粘贴到 Codex、Claude 或其他助手里，让它检查 Skill 页面并帮你完成安装。
基于 SOC 职业分类
Create and review deterministic RPM fixtures for safe, non-mutating tests. Use when tests need package manifests, lockfiles, registry metadata, install projects, expected outputs, or regression fixtures.
Resolve RPM PR review feedback. Use after Codex or human PR comments arrive to collect review context, classify feedback, apply only accepted in-scope fixes, validate, and draft/create deferred follow-up issues when explicitly allowed.
Context handoff for RPM GitHub issue-to-PR work. Use when the user says to take a ticket, implement a GitHub issue, run the ticket loop, or coordinate RPM issue work; this skill prepares the shared context packet and delegates execution to ticket-pr-lifecycle, spec-governance, fixture-governance, and pr-review-resolution.
Execute RPM GitHub issue-to-PR lifecycle work after take-ticket prepares context. Use for intake, issue reading, exploration handoff, draft PR setup, focused implementation, validation, PR checklist updates, and final audit; not for review feedback resolution.
| name | spec-governance |
| description | Keep SPEC.md authoritative for RPM contract-affecting changes. Use when code, reviews, or tickets may affect CLI behavior, lockfiles, manifests, semver, registry/cache/install/linking behavior, scripts, or diagnostics. |
Treat SPEC.md as the source of truth for observable package-manager contracts.
If code and SPEC disagree, classify the mismatch before editing further:
Use this skill for changes affecting:
node_modules linker layoutRead references/spec-locations-and-actions.md when you need SPEC path conventions, classification actions, minimal SPEC template, or reporting format.
Before finishing contract-affecting work, verify: