New: 97,000+ skills indexed from GitHub repos with 100+ stars · every skill safety-checkedBrowse top skillsTop skills
Esc to closeBrowse all skills
Submit a skillBrowse skills
Submit a skillBrowse skills

Agent skill

Hs Release

by vectorize-io in vectorize-io/hindsight

Cut a core Hindsight release (vX.Y.Z) and open the changelog + blog PR.

MITAuto-check: notesDevelopment

Install Hs Release

skills CLI
$ npx skills add vectorize-io/hindsight --skill hs-release -a claude-code

Project install by default; add -g for ~/.claude/skills/.

GitHub CLI
$ gh skill install vectorize-io/hindsight hs-release --agent claude-code

Project scope by default; add --scope user for a personal install. Needs GitHub CLI 2.90.0 or later (public preview).

Manual copy
$ git clone --depth 1 https://github.com/vectorize-io/hindsight.git skills-src && mkdir -p .claude/skills && cp -r skills-src/.claude/skills/hs-release .claude/skills/hs-release && rm -rf skills-src

Use ~/.claude/skills/ instead of .claude/skills for a personal install. The folder must contain SKILL.md.

Claude Code skills documentation · loads skills from .claude/skills/

Facts

Skill name
hs-release
GitHub stars
46k
Token cost
~1.5k tokens
SKILL.md length
730 words
Files
1
Skills in repo
17
Repo updated
First seen
Licence
MIT

At a glance

Cut a core Hindsight release (vX.Y.Z) and open the changelog + blog PR.

  • Works in 3 steps: Pre-flight → Cut the release → Changelog + blog PR (separate)
  • Asked to cut/start a release
  • SKILL.md covers Step 0 — Pre-flight, Step 1 — Cut the release, Step 2 — Changelog + blog PR… and Cleanup
  • Calls git, gh and uv; needs OPENAI_API_KEY

What it does

Hs Release is an agent skill from vectorize-io/hindsight. Cut a core Hindsight release (vX.Y.Z) and open the changelog + blog PR. Use when asked to cut/start a release, bump the version, or publish a new Hindsight version.

Its SKILL.md is about 1.5k tokens, which your agent loads only when the skill is triggered. It is a single SKILL.md file with no bundled scripts.

It sits in Development, covering Changelog and release notes. It works with Git. The repository describes itself as: Hindsight: Agent Memory That Learns. The licence is MIT.

When your agent uses it

  • Asked to cut/start a release
  • Bump the version
  • Publish a new Hindsight version

Example prompts

  • “/hs-release”

Requirements

  • Node.js
  • A credential in OPENAI_API_KEY

Workflow steps

3 steps, taken from the step headings in SKILL.md.

  1. Pre-flight
  2. Cut the release
  3. Changelog + blog PR (separate)

What it can do on your machine

Read from SKILL.md and the folder at commit 9269b88. It shows what the files ask for, not the result of running them.

  • Tool permissions

    Pre-approves nothing: there is no allowed-tools line, so your agent's usual permission prompts apply.

    From allowed-tools in the SKILL.md frontmatter.

  • Runs code

    Shell commands in SKILL.md call:

    • git
    • gh
    • uv
    • npx

    From the folder's file list and the shell code blocks in SKILL.md.

  • Network

    No URLs in SKILL.md. Its commands use git, gh, uv and npx, which can reach the network depending on how they are called.

    From URLs in SKILL.md, links to its own repository left out.

  • Credentials

    Names these keys or tokens, usually read from environment variables:

    • OPENAI_API_KEY

    From names ending in _API_KEY, _TOKEN, _SECRET, _KEY or _PASSWORD in SKILL.md.

Context cost

Hs Release loads about 1.5k tokens when it runs. Until then it costs about 44 tokens; SKILL.md has 730 words of instructions outside code blocks.

Always · name and description, kept in context so the agent knows when to use it
~44
When it runs · the whole SKILL.md, loaded when a task matches
~1.5k

Estimates: characters ÷ 4, the usual rule of thumb; real counts depend on the model's tokenizer. Scripts and assets cost tokens only if the agent reads them.

Safety

Auto-check: notes

The automated check noted patterns worth knowing about, such as sudo or a known installer.

  • NoteMentions a .env fileSKILL.md:78
    `.env`). It excludes `hindsight-integrations/` source, but new integrations whose commits also

Automated static check — not a guarantee. Review scripts before installing. It scans the text of SKILL.md for risky patterns (piping downloads into a shell, reading credential files, hidden Unicode, destructive commands); files beside SKILL.md are not scanned.

SKILL.md

The full file from vectorize-io/hindsight at commit 9269b88, republished under its MIT licence (© vectorize-io). 730 words, ~1,469 tokens.

Download SKILL.mdSave it as .claude/skills/hs-release/SKILL.md (or your agent's skills folder).
name
hs-release
description
Cut a core Hindsight release (vX.Y.Z) and open the changelog + blog PR. Use when asked to cut/start a release, bump the version, or publish a new Hindsight version.
user_invocable
true

Hindsight Release

Cut a core Hindsight release and open the accompanying changelog/blog PR. This is for the core product version (API, clients, CLI, control plane, Helm). Integrations are versioned independently — use scripts/release-integration.sh for those, not this skill.

The release is irreversible and outward-facing: it tags a version and pushes it straight to main, which triggers CI that publishes packages to PyPI / npm / Helm. Confirm the version number and that the intended fixes are already merged to main before you start.

Step 0 — Pre-flight

  1. Decide the base. A release is cut from the latest origin/main, never from a feature branch. git fetch origin --tags first. Confirm the "couple of fixes" the user means are actually merged to main (git log v<prev>..origin/main --oneline).
  2. Find where main is checked out. main is often already checked out in a sibling worktree (git worktree list). You cannot check out main in a second worktree — run the release in the worktree that already holds it. If that worktree is dirty with throwaway cruft (.next-* tsconfig paths, screenshots), git stash push -u, fast-forward to origin/main, run the release, then git stash pop.
  3. Pitfall: never pipe the checkout in an && chain like git checkout main 2>&1 | tail && git reset --hard ... — the pipe's exit status is tail's (always 0), so a failed checkout won't stop the chain and the reset fires on the wrong branch. Check out as its own command and verify git branch --show-current before resetting.

Step 1 — Cut the release

Run from the worktree on a clean main:

bash
./scripts/release.sh <version>     # e.g. 0.8.1  (no leading v)

release.sh bumps the version in every component, regenerates the OpenAPI spec + all client SDKs, updates docs versioning, commits Release v<version>, tags v<version>, and pushes the commit and tag directly to main. The push triggers the Release GitHub Actions workflow that builds and publishes the packages. It is not a PR.

Verify after: gh run list --limit 5 should show the Release v<version> workflow running, and git ls-remote --tags origin v<version> should return the tag.

Step 2 — Changelog + blog PR (separate)

Done after the tag exists, as its own PR (precedent: v0.8.0 = #2053, v0.8.1 = #2080). Work on a branch off the new main:

bash
git checkout -b docs-changelog-<version> origin/main

Only spin up a separate worktree (git worktree add ../hindsight-changelog-<version> -b docs-changelog-<version> origin/main) if you can't get a clean checkout otherwise — e.g. main is held in another worktree and the current one has work you don't want to disturb.

Branch naming: use the docs- (hyphen) convention, e.g. docs-changelog-0.8.1. A remote branch literally named docs exists, so any docs/... branch is rejected on push with directory file conflict.

Show full SKILL.md (306 more words)Show less
Changelog
bash
uv run --directory hindsight-dev generate-changelog <version>

LLM-summarizes the commits between the previous tag and v<version> and prepends an entry to hindsight-docs/src/pages/changelog/index.md.

The entry ends with a Database Migrations section listing every Alembic migration added in the range, each linking to the PR that introduced it. That section is enumerated deterministically from git (--diff-filter=A over hindsight_api/alembic/versions/), not by the LLM — don't hand-edit it, and if a migration is missing, check that its commit actually added the file in the tag range. Requires OPENAI_API_KEY (already in the repo .env). It excludes hindsight-integrations/ source, but new integrations whose commits also touched docs will still appear — that matches precedent, leave them in the changelog.

Blog post

Hand-write hindsight-docs/blog/YYYY-MM-DD-version-X-Y-Z.md (mirror an existing one; patch releases are short — see 2026-06-02-version-0-7-2.md). Guidance:

  • Explain user impact, not internals/mechanism. Lead with what the user can now do and what to set. Config/env-var names are fine (developer-facing), code symbols and internals are not.
  • Do not list integrations in the release blog. The core blog covers core engine / API / ops changes; each integration ships its own changelog. (Integrations may still appear in the generated changelog/index.md — that's fine; just keep them out of the blog.)
  • Call out an upgrade recommendation when there are operational/data-integrity fixes.
  • Validate formatting: npx prettier --check <blog file>.
Sync the docs skill
bash
./scripts/generate-docs-skill.sh

Refreshes skills/hindsight-docs/references/changelog/index.md. It will also bump skills/hindsight-docs/references/openapi.json by one version — release.sh regenerates the skill before bumping OpenAPI, so the skill copy lags a version in the release commit; this step syncs it. Expect a one-line version diff there; keep it.

Commit, push, PR
bash
git add -A
git commit --no-verify -m "docs: changelog and blog post for v<version>"
git push -u origin docs-changelog-<version>
gh pr create --base main --title "docs: changelog and blog post for v<version>" --body "..."

Expected files in the PR: the changelog entry, the new blog post, the regenerated skill changelog mirror, and the skill openapi.json version sync.

Cleanup

If you created a temporary worktree, remove it once the PR is up (git worktree remove ../hindsight-changelog-<version>; the branch stays on origin). Restore any stash you popped in Step 0.

© vectorize-io, MIT. Rendered from Markdown: HTML in the file is shown as text, images as links, and headings moved down two levels. Raw file

Files

Just SKILL.md in .claude/skills/hs-release of vectorize-io/hindsight.

Open the folder on GitHubat commit 9269b88

Compare with similar skills

Hs Release next to the 5 skills that share the most tags, products or categories with it. Stars are the repository's; “used in” counts other GitHub owners with a copy.

Hs Release compared with similar skills
SkillStarsUsed inTokensAuto-checkLicenceRepo updated
Hs Release this skillvectorize-io/hindsight46k—~1.5kAutomated safety check: NotesMIT
React Router Release Notes Prepremix-run/react-router57k—~1.1kAutomated safety check: PassMIT
Draft Release Notesjamiepine/voicebox57k—~941Automated safety check: PassMIT
Mole Release Notes Publishertw93/Mole69k—~1.9kAutomated safety check: PassGPL-3.0
Release Bumpjamiepine/voicebox57k—~1.1kAutomated safety check: PassMIT
Git Workflow and Versioningaddyosmani/agent-skills102k2 repos~3.5kAutomated safety check: NotesMIT

Similar skills

  • React Router Release Notes Prep

    remix-run/react-router

    Polishes pending React Router change files before the versioning scripts run, and decides whether a long-form What's Changed section is warranted.

    57k GitHub stars~1.1k tokensUpdated yesterday
    DevelopmentAuto-check passed

  • Draft Release Notes

    jamiepine/voicebox

    Writes or refreshes the Unreleased section of CHANGELOG.md as a themed narrative built from the commits, PRs and diff since the last version tag.

    57k GitHub stars~941 tokensUpdated today
    DevelopmentAuto-check passed

  • Mole Release Notes Publisher

    tw93/Mole

    Publishes curated, bilingual release notes for an existing Mole version tag with gh release edit, including contributor thanks and reactions, after the release workflow finishes.

    69k GitHub stars~1.9k tokensUpdated today
    DevelopmentAuto-check passed

  • Release Bump

    jamiepine/voicebox

    Ends a release cycle by moving the Unreleased changelog notes under a dated version heading, bumping version files with bumpversion and tagging the commit.

    57k GitHub stars~1.1k tokensUpdated today
    DevelopmentAuto-check passed

  • Git Workflow and Versioning

    addyosmani/agent-skills

    Sets git habits for every change: short-lived branches, atomic commits with descriptive messages, clean pull requests, plus versioning, tagging and changelogs for releases.

    102k GitHub starsUsed in 2 repos~3.5k tokens
    DevelopmentAuto-check: notes

  • Verdaccio Pull Request Workflow

    verdaccio/verdaccio

    Takes a change through a verdaccio pull request: branch, local checks, changeset, title and body, labels, CI and review rounds, and ports to other release lines.

    18k GitHub stars~1.9k tokensUpdated yesterday
    DevelopmentAuto-check passed

More from vectorize-io/hindsight

All 17 skills in this repo

  • Hindsight Docs

    vectorize-io/hindsight

    Complete Hindsight documentation for AI agents. An agent skill from vectorize-io/hindsight.

    46k GitHub stars~928 tokensUpdated today
    Auto-check passed

  • Create Agent

    vectorize-io/hindsight

    Create a new Hindsight-powered subagent with long-term memory.

    46k GitHub stars~1.1k tokensUpdated today
    Auto-check passed

  • Figure

    vectorize-io/hindsight

    Draw an animated figure (boxes, arrows, moving data) as one self-contained SVG for a GitHub README, PR, issue or blog post.

    46k GitHub stars~1.9k tokensUpdated today
    Auto-check passed

  • Hindsight Local

    vectorize-io/hindsight

    Store user preferences, learnings from tasks, and procedure outcomes.

    46k GitHub stars~1.1k tokensUpdated today
    Auto-check passed

  • Hindsight Memory

    vectorize-io/hindsight

    Long-term memory for the agent via Hindsight. An agent skill from vectorize-io/hindsight.

    46k GitHub stars~688 tokensUpdated today
    Auto-check passed

  • Ship It

    vectorize-io/hindsight

    Take a PR from review to merged — run the repo's code-review skill on it in a loop (review, fix, re-review) until nothing is left to fix, applying ALL fixes on the PR branch, wait for CI green, then…

    46k GitHub stars~1.9k tokensUpdated today
    Auto-check passed

Works with

Categories

Questions about Hs Release

What does Hs Release do?

Cut a core Hindsight release (vX.Y.Z) and open the changelog + blog PR. Hs Release is an agent skill from vectorize-io/hindsight.Z) and open the changelog + blog PR.

When should I use Hs Release?

Hs Release fits situations like: asked to cut/start a release; bump the version; publish a new Hindsight version.

How do I install Hs Release in Claude Code?

Run `npx skills add vectorize-io/hindsight --skill hs-release -a claude-code`. Or copy the skill folder (.claude/skills/hs-release in vectorize-io/hindsight) into .claude/skills/hs-release in your project. Claude Code loads it when a task matches its description.

How do I install Hs Release in Codex?

Run `npx skills add vectorize-io/hindsight --skill hs-release -a codex`. Or copy the skill folder (.claude/skills/hs-release in vectorize-io/hindsight) into .agents/skills/hs-release in your project. Codex loads it when a task matches its description.

Can I use Hs Release in Cursor, Gemini CLI or GitHub Copilot?

Cursor, Gemini CLI, GitHub Copilot and OpenCode also load SKILL.md folders. With the skills CLI, run `npx skills add vectorize-io/hindsight --skill hs-release -a cursor` (or -a gemini-cli, github-copilot or opencode for the others). To copy it by hand, put the folder in .cursor/skills/hs-release, .gemini/skills/hs-release, .github/skills/hs-release and .opencode/skills/hs-release in your project.

What does Hs Release need to run?

Going by SKILL.md and its folder, Hs Release needs the command-line tools its instructions call (git, gh, uv and npx) and credentials named OPENAI_API_KEY. Our summary lists: Node.js; A credential in OPENAI_API_KEY.

Does Hs Release access the network?

SKILL.md contains no URLs. Its commands use git, gh, uv and npx, which can reach the network depending on how they are called. This is read from the text; nothing was executed.

Is Hs Release safe to install?

Our automated static check of SKILL.md found notes only (mentions a .env file), nothing it rates as a warning. It is not a guarantee. Review the folder before installing.

What licence does Hs Release use?

Hs Release is published under the MIT licence (the repository's licence). It allows redistribution, so the full SKILL.md is shown on this page.

How many tokens does Hs Release use?

About 1.5k tokens (SKILL.md is roughly 5.9k characters). Agents keep only the skill's name and description in context until a task matches; then they load SKILL.md in full.

What are the alternatives to Hs Release?

Skills that share tags, products or a category with Hs Release: React Router Release Notes Prep (remix-run/react-router, 57k stars), Draft Release Notes (jamiepine/voicebox, 57k stars), Mole Release Notes Publisher (tw93/Mole, 69k stars) and Release Bump (jamiepine/voicebox, 57k stars). The comparison table on this page puts their stars, adoption, token cost, safety result and licence side by side.

Who maintains Hs Release?

vectorize-io (a GitHub organization) maintains it in vectorize-io/hindsight, which has 46,453 GitHub stars. The repository holds 17 skills in this directory. The repository was last updated on October 7, 2026.

Source: vectorize-io/hindsight on GitHub. Facts on this page come from the repository at the commit we read; the author's words are quoted as theirs.