New: 98,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

Pre Release

by rusq in rusq/slackdump

Prepare this repository for a release. An agent skill from rusq/slackdump.

AGPL-3.0Auto-check passedDevelopment

Install Pre Release

skills CLI
$ npx skills add rusq/slackdump --skill pre-release -a claude-code

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

GitHub CLI
$ gh skill install rusq/slackdump pre-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/rusq/slackdump.git skills-src && mkdir -p .claude/skills && cp -r skills-src/.agents/skills/pre-release .claude/skills/pre-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
pre-release
GitHub stars
2.8k
Token cost
~841 tokens
SKILL.md length
396 words
Files
1
Skills in repo
4
Repo updated
First seen
Licence
AGPL-3.0

At a glance

Prepare this repository for a release. An agent skill from rusq/slackdump.

  • Works in 5 steps: Determine the release range. → Update release notes when requested. → Update contributors when requested or as… → …
  • Asked to do pre-release checks
  • SKILL.md covers Workflow, Search Hints and Final Response
  • Calls git

What it does

Pre Release is an agent skill from rusq/slackdump. Prepare this repository for a release. Use when asked to do pre-release checks, summarize changes since a previous tag, update WHATSNEW.md or changelog entries, update CONTRIBUTORS.md, audit command long help or docs for release-visible features, or verify release documentation consistency.

Its SKILL.md is about 840 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 and Slack. The repository describes itself as: Save or export your private and public Slack messages, threads, files, and users locally without admin privileges. The licence is AGPL-3.0.

When your agent uses it

  • Asked to do pre-release checks
  • Summarize changes since a previous tag
  • Update WHATSNEW.md
  • Changelog entries

Example prompts

  • “/pre-release”

Workflow steps

5 steps, taken from the first numbered list in SKILL.md.

  1. Determine the release range.
  2. Update release notes when requested.
  3. Update contributors when requested or as part of a full release prep.
  4. Audit command help and docs for release-visible changes.
  5. Validate.

What it can do on your machine

Read from SKILL.md and the folder at commit 88e7c22. 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

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

  • Network

    No URLs in SKILL.md. Its commands use git, 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 no API keys, tokens, secrets or passwords.

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

Context cost

Pre Release loads about 841 tokens when it runs. Until then it costs about 76 tokens; SKILL.md has 396 words of instructions outside code blocks.

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

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 passed

The automated check found no risky patterns in SKILL.md.

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 rusq/slackdump at commit 88e7c22, republished under its AGPL-3.0 licence (© rusq). 396 words, ~841 tokens.

Download SKILL.mdSave it as .claude/skills/pre-release/SKILL.md (or your agent's skills folder).
name
pre-release
description
Prepare this repository for a release. Use when asked to do pre-release checks, summarize changes since a previous tag, update WHATSNEW.md or changelog entries, update CONTRIBUTORS.md, audit command long help or docs for release-visible features, or verify release documentation consistency.

Pre-release

Use this skill for repository-local release-prep documentation passes. Ground every update in commit history, diffs, and current command behavior.

Workflow

  1. Determine the release range.

    • Use the base tag or version supplied by the user.
    • If no base is supplied, inspect tags with git tag --list 'v*' --sort=-version:refname and infer the previous release tag.
    • Inspect changes with git log --oneline <base>..HEAD, git diff --stat <base>..HEAD, and git diff --name-only <base>..HEAD.

  2. Update release notes when requested.

    • Check whether the changelog file is a symlink before editing it.
    • Preserve the existing changelog style and section order.
    • Add the new version section above the previous release.
    • Focus on user-visible features, behavior changes, bug fixes, migration notes, and documented workflows.
    • Mention commands, flags, formats, and caveats exactly as implemented.
    • Avoid internal-only refactors unless they materially affect users, maintainers, packaging, or contributors.

  3. Update contributors when requested or as part of a full release prep.

    • Compare git shortlog -sne <base>..HEAD and git log --format='%aN <%aE>' <base>..HEAD against CONTRIBUTORS.md.
    • Inspect individual commits and merge commits for contribution scope.
    • Infer GitHub handles only from reliable local evidence such as PR branch names in merge commits or existing repository metadata.
    • Add concise entries for new contributors and update the displayed total.
    • Do not duplicate existing contributors; extend an existing entry when that is clearer.

  4. Audit command help and docs for release-visible changes.

    • Search embedded help assets, command definitions, and docs for each release-note topic.
    • Update only the help/docs that a user would naturally consult for the changed command, flag, format, or workflow.
    • For Go files with inline long help, avoid Markdown backticks inside raw string literals unless the literal delimiter allows them.
    • Keep documentation concise and practical: what changed, how to use it, and any important tradeoff.

  5. Validate.

    • Run gofmt on edited Go files.
    • Run targeted tests for touched Go packages when Go files changed.
    • For Markdown-only changes, no full test run is required; say that explicitly.
    • Review git diff --stat, relevant git diff, and git status --short.
    • Preserve the user's staged and unstaged state; do not stage files unless asked.
Show full SKILL.md (49 more words)Show less

Search Hints

  • Changelog: WHATSNEW.md, cmd/**/assets/*changelog*.
  • Contributors: CONTRIBUTORS.md, git shortlog, merge commit messages.
  • Embedded command help: cmd/**/assets/*.md and Long: fields in Go files.
  • User docs: doc/, README.md, command-specific usage files.

Final Response

Report:

  • The release range inspected.
  • Files changed.
  • Validation commands run and results.
  • Any notable staged vs unstaged state.

© rusq, AGPL-3.0. 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 .agents/skills/pre-release of rusq/slackdump.

Open the folder on GitHubat commit 88e7c22

Compare with similar skills

Pre 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.

Pre Release compared with similar skills
SkillStarsUsed inTokensAuto-checkLicenceRepo updated
Pre Release this skillrusq/slackdump2.8k—~841Automated safety check: PassAGPL-3.0
Changelog Orchestratorjeremylongshore/tons-of-skills-marketplace2.8k—~694Automated safety check: PassMIT
Code Design Rationale Investigatorcursor/plugins10k9 repos~2.6kAutomated safety check: PassNone
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/Mole70k—~1.9kAutomated safety check: PassGPL-3.0

Similar skills

  • Changelog Orchestrator

    jeremylongshore/tons-of-skills-marketplace

    Draft changelog PRs by collecting GitHub/Slack/Git changes, formatting with templates, running quality gates, and preparing a branch/PR.

    2.8k GitHub stars~694 tokensUpdated today
    DevelopmentAuto-check passed

  • Code Design Rationale Investigator

    cursor/plugins

    Official

    Digs into why code is shaped the way it is by checking git history, pull requests and connected tools in parallel, then reporting a cited read on the tradeoffs.

    10k GitHub starsUsed in 9 repos~2.6k tokens
    DevelopmentAuto-check passed

  • 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 2 days ago
    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 yesterday
    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.

    70k 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 yesterday
    DevelopmentAuto-check passed

More from rusq/slackdump

  • Slackdump

    rusq/slackdump

    Collect the Slack conversation data from Slackdump Archive format.

    2.8k GitHub stars~2k tokensUpdated 5 days ago
    Auto-check passed

  • Slackdump Source

    rusq/slackdump

    Explains the different Slackdump sources structure. An agent skill from rusq/slackdump.

    2.8k GitHub stars~876 tokensUpdated 5 days ago
    Auto-check passed

  • Slackdump Sqlite3

    rusq/slackdump

    Guidance for querying a Slackdump SQLite3 database directly via the sqlite3 CLI.

    2.8k GitHub stars~1.6k tokensUpdated 5 days ago
    Auto-check passed

Works with

Categories

Questions about Pre Release

What does Pre Release do?

Prepare this repository for a release. An agent skill from rusq/slackdump. Pre Release is an agent skill from rusq/slackdump. Prepare this repository for a release.

When should I use Pre Release?

Pre Release fits situations like: asked to do pre-release checks; summarize changes since a previous tag; update WHATSNEW.md; changelog entries.

How do I install Pre Release in Claude Code?

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

How do I install Pre Release in Codex?

Run `npx skills add rusq/slackdump --skill pre-release -a codex`. Or copy the skill folder (.agents/skills/pre-release in rusq/slackdump) into .agents/skills/pre-release in your project. Codex loads it when a task matches its description.

Can I use Pre 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 rusq/slackdump --skill pre-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/pre-release, .gemini/skills/pre-release, .github/skills/pre-release and .opencode/skills/pre-release in your project.

What does Pre Release need to run?

Going by SKILL.md and its folder, Pre Release needs the command-line tools its instructions call (git).

Does Pre Release access the network?

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

Is Pre Release safe to install?

Our automated static check of SKILL.md found no risky patterns, such as piping downloads into a shell, reading credential files or hidden Unicode. It is not a guarantee. Review the folder before installing.

What licence does Pre Release use?

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

How many tokens does Pre Release use?

About 841 tokens (SKILL.md is roughly 3.4k 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 Pre Release?

Skills that share tags, products or a category with Pre Release: Changelog Orchestrator (jeremylongshore/tons-of-skills-marketplace, 2.8k stars), Code Design Rationale Investigator (cursor/plugins, 10k stars), React Router Release Notes Prep (remix-run/react-router, 57k stars) and Draft Release Notes (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 Pre Release?

rusq (a GitHub user) maintains it in rusq/slackdump, which has 2,811 GitHub stars. The repository holds 4 skills in this directory. The repository was last updated on October 3, 2026.

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