ln-63-release-publisher
Prepares and publishes a tagged GitHub release from repository evidence. Use for an explicit release request; not for ordinary commits, packages, or community news.
Profile →npx skills add levnikolaevich/claude-code-skills --skill ln-63-release-publisher --agent claude-code
Same command for any agent — swap --agent for codex, cursor, copilot.
Weekly change comes from our own snapshots, not the repository page — it measures attention, not adoption.
# Release Publisher **Goal:** Prepare a reproducible release and publish it only after the user approves the exact tag and notes. **Execution contract:** Treat the ordered checkbox workflow below as this skill's Definition of Done. Work through every item in order, and mark it complete only when its action and required evidence are complete. `N/A`, skipped, unavailable, or delegated items remain incomplete. Before returning, apply this skill's verdict, decision, and approval rules to every incomplete item and prepend **Checklist: X/Y complete**<br>**Incomplete: None | section/item — reason; outcome impact; exact next action**; list every incomplete item. ## Tool Routing | Need | Preferred capability | Fallback | |---|---|---| | Release boundary and commit evidence | Git history, tags, and diffs | Hosting API commit comparison | | Existing release style and state | Authenticated GitHub CLI or connector | Public GitHub API for read-only evidence | | Release identity and version scope | Repository policy, prior tags, and canonical version files when present | Stop only when the release identity remains ambiguous | | Release validation | Repository-native gates and clean checkout | Man
- Tool Routing
- Checklist
- Version and Scope
- Release Notes
- Validation and Approval
- Publication
- Failure Handling
- Verdict
- Output Contract
What does the ln-63-release-publisher skill do?
Prepares and publishes a tagged GitHub release from repository evidence. Use for an explicit release request; not for ordinary commits, packages, or community news.
How do I install it?
Run `npx skills add levnikolaevich/claude-code-skills --skill ln-63-release-publisher --agent claude-code` — it drops the skill into your project so the agent can pick it up. Swap the --agent value for codex, cursor or copilot if you use one of those.
Where does this skill come from?
From levnikolaevich/claude-code-skills, a repository with 528 stars. We read it straight from the repository tree rather than a submitted listing, so what you see here is what is actually published.
Is a popular skill a good skill?
Not necessarily. Stars measure attention, not adoption — a repository can trend for a week and be abandoned. That is why we show the weekly change from our own snapshots next to the total, instead of a single flattering number.