跳至正文
OpenAgentSkill
浏览已开放 · 目录记录日期 2026-11-21 · 自动更新和账户服务暂时关闭。
部署与云服务

ln-62-release-publisher

Prepares and publishes an explicitly requested tagged GitHub release; does not deploy applications.

levnikolaevich · 已有静态检查记录

安装与使用

运行命令前先阅读来源与依赖说明。复制命令不会自动安装或执行。

npx skills add levnikolaevich/claude-code-skills --skill ln-62-release-publisher

技能说明


name: ln-62-release-publisher description: "Prepares and publishes an explicitly requested tagged GitHub release; does not deploy applications."

Release Publisher

Goal: Prepare a reproducible release and publish it only after the user approves the exact tag and notes.

Execution contract: The checklist defines completion. Track each item internally as PENDING, PROVEN with evidence, CLEARED with evidence its condition is absent, or UNPROVEN with a gap; reading, delegation, tool failure, a zero exit status, or a self-reported success is not proof; only the observed outcome is. Reconcile after each section. Before returning, resolve all PENDING, count only PROVEN and CLEARED, and apply verdict and approval rules to every gap. Preserve intent, scope, and existing authorization. Continue authorized work; ask only for consequential unresolved choices or required external approval. When no one can answer during the run, state the exact question and apply the skill's verdict for the remaining gap instead of waiting or guessing. Scale depth to material risk without skipping checks. Preserve dependency and safety order; otherwise choose an appropriate verification method. Accept equivalent user or repository evidence; no other skill, named artifact, or complete lifecycle is required. Preserve source requirement and decision IDs. Bind reused evidence to relevant source versions, dirty changes, configuration, and environment; invalidate only affected claims. Choose one primary workflow by the requested outcome, honoring explicit selection. Consume neighboring contracts and valid evidence without duplicating ownership or restarting a full audit. Split genuinely distinct deliverables by scope, not by mandatory skill invocation. Broad independent assessments belong to audit workflows; focused reviews may stay with the domain workflow but remain read-only. On continuation, reconcile task, authorization, current state, and unresolved evidence. For long work, return a compact continuation record or update an already authorized artifact; read-only skills do not persist it. Distinguish artifact readiness, verified behavior, and external-action authority. Prepare authorized work before required approval. If blocked by an instruction, cite its exact source and unresolved boundary; do not invent approval gates from caution. Before a new or changed technical decision, establish applicability and actual technology versions, then verify version-dependent assumptions against official documentation or specifications even when confident. Search and read primary pages for current external recommendations; search snippets are not evidence. Version-matched bundled documentation or still-valid prior evidence can suffice. Record the decision, applicable version, source and limitations. If evidence is unavailable, mark the affected conclusion UNVERIFIED and block only dependent work when essential. Prefer native mechanisms; add tools or abstractions only for an evidenced requirement. Reuse the existing project rule owner instead of creating parallel policy.

Tool Routing

NeedPreferred capabilityFallback
Release boundary and commit evidenceGit history, tags, and diffsHosting API commit comparison
Existing release style and stateAuthenticated GitHub CLI or connectorPublic GitHub API for read-only evidence
Release identity and version scopeRepository policy, prior tags, and canonical version files when presentStop only when the release identity remains ambiguous
Release validationRepository-native gates and clean checkoutManual structural checks with reduced confidence
Tag and GitHub Release creationGit plus an authenticated GitHub release capabilityBLOCKED; do not emulate release state in files
Installation verificationIsolated environment against the documented distribution sourceClean source validation without install proof

When publishing through a shell, use a temporary notes file so Markdown, quotes, and code blocks are not reinterpreted. Keep credentials in the host credential store and never echo them.

Do not browse for generic release advice when repository policy and previous comparable releases answer the question. Use official host documentation only for current API or CLI behavior.

Checklist

Establish scope and evidence

  • Confirm the user explicitly requested a release and identify the repository, release target, and intended audience.
  • Read repository release rules before selecting a version, tag shape, files, or publication sequence.
  • Verify an authenticated GitHub release capability, repository access, and permission to create releases.
  • Require a clean worktree or explicitly exclude unrelated changes before release preparation.
  • Fetch tags and the target branch; confirm local HEAD is synchronized with the remote release branch.
  • Resolve the prior release boundary for this release line; for a first release, use the agreed initial history boundary and label it explicitly.
  • Inspect commits and full commit bodies from the previous release boundary to the proposed release commit.
  • Read the affected manifests, authoritative documentation, installation instructions, configured catalogs, and user-facing migration notes when present.
  • Treat commits and source diffs as evidence; use existing release notes only as secondary context.

Version and Scope

  • Use the repository's declared versioning policy; do not impose CalVer, SemVer, or a shared catalog version when none is specified.
  • If the release target or tag is ambiguous, stop and ask instead of inventing a convention.
  • Check the proposed tag locally and remotely. For a resumed approved release, verify its exact target and existing release state before continuing; otherwise treat a collision as a blocker, never overwrite it.
  • Prepare version changes only in canonic
阅读完整来源 ↗