From hrp
Records Helium Release Proposal (HRP) vote results: updates status to Approved/Proposed, adds vote URL to frontmatter, inserts outcome in README vote history, posts Reddit comment. Handles pass/fail/cancel.
How this skill is triggered — by the user, by Claude, or both
Slash command
/hrp:vote-closeThe summary Claude sees in its skill listing — used to decide when to auto-load this skill
You record the outcome of a Helium Release Proposal community vote and update all the
You record the outcome of a Helium Release Proposal community vote and update all the tracking surfaces — the release file, the README, and the Reddit thread.
This skill also handles the "vote cancelled" case where the vote never actually started (e.g. the helium-vote PR was rejected or the multisig didn't sign).
status: Frozen — this is the one with an active or recently completed voteStatus guard: This skill only operates on Frozen HRPs. If the HRP has a different status:
Proposed → "This HRP hasn't been frozen for voting yet. Run /hrp:vote-open first."Approved → "This HRP's vote result has already been recorded."Released → "This HRP has already been released."Ask the user which scenario applies:
Gather from the user (or extract from context):
https://www.heliumvote.com/hnt/proposals/3hSC...)Update frontmatter:
status: Approvedvote-url: {heliumvote.com URL}Update README — insert a new line into the vote history list. The list lives between the intro paragraph and the "How to Contribute" section. Insert at the top of the list (newest first), matching the existing format exactly:
- HRP {YYYY-MM} passed with [{X}% of the vote]({vote-url}) on {Month Dth Year}
Post Reddit comment (if reddit-post-id exists):
**HRP {Month Year} passed!**
The community approved this release with {X}% of the vote. Deployment is expected within the next few days.
Thanks to everyone who participated in the vote!
[Vote results]({vote-url})
Gather the same details as 3a (URL, percentage, date).
Update frontmatter:
status: Proposed (reverts to allow further changes)vote-url: {heliumvote.com URL} (kept for historical record)vote-summary-url and vote-pr fieldsUpdate README — same insertion point as 3a:
- HRP {YYYY-MM} failed with [{X}% of the vote]({vote-url}) on {Month Dth Year}
Post Reddit comment (if reddit-post-id exists):
**HRP {Month Year} did not pass**
The community vote concluded with {X}% approval. The proposal has been reverted to Proposed status for further discussion and revision.
[Vote results]({vote-url})
No vote URL, percentage, or date needed.
Update frontmatter:
status: Proposed (reverts to allow further changes)vote-summary-url and vote-pr fieldsDo not update the README — nothing to record if no vote happened.
No Reddit comment — unless the user specifically asks for one.
Commit directly to main (the release file should already be on main by this point). Include both the release file and README (if changed) in a single commit:
Record HRP {Month Year} vote result: approved with {X}%Record HRP {Month Year} vote result: failed with {X}%Revert HRP {Month Year} to Proposed (vote cancelled)Tell the user:
/hrp:release to record the deployment date."/hrp:vote-open again when ready."npx claudepluginhub helium/helium-release-proposals --plugin hrpAutomates releases for projects using Keep a Changelog and GitHub: bump detection, CHANGELOG promotion, merge to main, tag, and GitHub Release with a single confirmation gate.
Automates releases for Keep a Changelog + GitHub projects: bump detection, CHANGELOG promotion, PR/main merge, tag, and GitHub Release with a single confirmation gate.
Generates SemVer-compliant version bumps and changelog entries from git diffs. Use when cutting releases, tagging, or publishing with precise change summaries.