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

Release Docs

by fastrepl in fastrepl/anarlog

Prepare Anarlog release notes and documentation, publish the website changelog when the app is published, and verify the live content without a separate request.

MITAuto-check passedDevelopment

Install Release Docs

skills CLI
$ npx skills add fastrepl/anarlog --skill release-docs -a claude-code

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

GitHub CLI
$ gh skill install fastrepl/anarlog release-docs --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/fastrepl/anarlog.git skills-src && mkdir -p .claude/skills && cp -r skills-src/.agents/skills/release-docs .claude/skills/release-docs && 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
release-docs
GitHub stars
9.4k
Token cost
~1.6k tokens
SKILL.md length
795 words
Files
1
Skills in repo
32
Repo updated
First seen
Licence
MIT

At a glance

Prepare Anarlog release notes and documentation, publish the website changelog when the app is published, and verify the live content without a separate request.

  • Works in 3 steps: Read docs/AGENTS.md and New Changelog. → Prepare the changelog with its date and… → Merge required content before freezing…
  • Tasks that involve Changelog and release notes
  • SKILL.md covers Before candidate freeze, Publish with the app, Mobile publication and Other documentation and…
  • Calls pnpm and gh; reaches anarlog.so and docs.anarlog.so

What it does

Release Docs is an agent skill from fastrepl/anarlog. Prepare Anarlog release notes and documentation, publish the website changelog when the app is published, and verify the live content without a separate request.

Its SKILL.md is about 1.6k 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 and Technical writing. The repository describes itself as: Open source Granola AI Alternative. The licence is MIT.

When your agent uses it

  • Tasks that involve Changelog and release notes
  • Tasks that involve Technical writing

Example prompts

  • “/release-docs”

Workflow steps

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

  1. Read docs/AGENTS.md and New Changelog.
  2. Prepare the changelog with its date and plain-text summary. Run changed-file
  3. Merge required content before freezing the candidate. Keep unreleased

What it can do on your machine

Read from SKILL.md and the folder at commit 259a04e. 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:

    • pnpm
    • gh

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

  • Network

    Hosts in commands or code, which the agent is likely to contact:

    • anarlog.so
    • docs.anarlog.so

    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

Release Docs loads about 1.6k tokens when it runs. Until then it costs about 44 tokens; SKILL.md has 795 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.6k

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 fastrepl/anarlog at commit 259a04e, republished under its MIT licence (© fastrepl). 795 words, ~1,637 tokens.

Download SKILL.mdSave it as .claude/skills/release-docs/SKILL.md (or your agent's skills folder).
name
release-docs
description
Prepare Anarlog release notes and documentation, publish the website changelog when the app is published, and verify the live content without a separate request.
metadata.internal
true

Release Docs

Review every release. Inherit scope and session authorization from Release a New Version. Own documentation and changelog publication through completion, not just the source file or PR. For mobile-only distribution, prepare Mobile notes and review affected mobile and shared documentation. Use the Mobile publication steps below; desktop release/tag checks are not applicable.

Before candidate freeze

  1. Read docs/AGENTS.md and New Changelog. Compare all user-facing changes since the previous published release in that stream (previous stable for stable notes) with packages/changelog/content/<stream>/<version>.md, docs/, docs/docs.json, and apps/web/public/llms.txt. Cover guides, installation/upgrade instructions, CLI/MCP/API examples, screenshots, troubleshooting, and platform availability. Preserve external-contributor credits and describe shipped behavior only.
  2. Prepare the changelog with its date and plain-text summary. Run changed-file formatting, pnpm -F @anlg/changelog typecheck, and affected web checks from web_ci.yaml/root AGENTS.md. For docs, use the Mintlify version pinned in cli_ci.yaml to run validate and broken-links --check-anchors --check-redirects from docs/; preview affected pages and navigation. Coordinate public skill changes with Agent packages.
  3. Merge required content before freezing the candidate. Keep unreleased notes hidden: desktop entries require published, non-draft, non-prerelease GitHub desktop_v<version> releases; mobile entries require verified adjacent publication records as specified in packages/changelog/content/mobile/AGENTS.md. Verify the production index omits the candidate and its direct URL returns 404 before publication. A local production build can test this; vite dev intentionally previews drafts.

Publish with the app

These steps are part of the authorized stable release, without another user prompt. Read desktop_publish.yaml, web_cd.yaml, and apps/web/changelog-build.ts before selecting the deployment; do not assume merging the notes publishes them.

  1. Wait for the exact GitHub/CrabNebula app version to be published. A website build made before that event deliberately excludes its notes, even when its source contains the Markdown. Do not weaken that gate or move the desktop tag.
  2. Complete the website publication in the same release operation. The desktop workflow currently calls web_cd.yaml through linux-apt-deploy after merging Linux metadata. Follow an existing matching deploy to completion and reuse it if its build began after app publication and its source includes the notes.
  3. If no such deployment exists, including when Linux is excluded, verify the approved main source contains the notes and dispatch web_cd.yaml --ref main with gh workflow run. Verify the returned run's headSha against that source and follow it to completion. Avoid duplicate deployments and preserve newer APT metadata; never deploy the old desktop candidate over newer website/package content. If main contains unrelated unapproved web changes, resolve that source scope before deploying and report the concrete publication blocker.
  4. Fetch https://anarlog.so/changelog/desktop/<version>/ and https://anarlog.so/changelog/ from the live site. Verify the expected version, summary and release-note sections/body, plus the index link. For the latest desktop release, verify it is marked Latest within the Desktop stream. Verify the legacy /changelog/<version>/ URL redirects to its Desktop page. HTTP 200, a generic page, a source file, a search-engine snapshot, or a green build alone is insufficient. If content is stale, inspect the actual deployment revision and cache response and resolve it within this release operation. Do not report completion with missing notes.
  5. Verify GitHub release notes link to the working page and check public download and update routes for the published version. In-app bundled notes, updater payload notes, GitHub release text, and the website are separate surfaces; do not use one as proof of another or promise inline notes where only a link exists.
Show full SKILL.md (239 more words)Show less

Mobile publication

  1. Prepare packages/changelog/content/mobile/<version>.md before candidate freeze, with the requested audience and platform-specific sections.
  2. Follow the coordinator's mobile distribution reference. Verify the exact candidate build is available to the intended testers or public store users; upload/submission success alone is insufficient.
  3. Create the adjacent <version>.json using the contract in packages/changelog/content/mobile/AGENTS.md. Include candidate SHA, channel, exact build numbers, per-platform availability timestamps, and evidence links. Record only available platforms; do not infer simultaneous iOS and Android approval. Run the affected web checks.
  4. Merge the verified record, then reuse or dispatch the website deployment from approved main within the existing mobile release authorization. A build made before the record was merged deliberately excludes the notes.
  5. Verify /changelog/mobile/<version>/, /changelog/?stream=mobile, and the combined index, including full notes, channel, and actual destinations. Add later platform availability to the same record and publish that update. Do not report stable public availability for a beta-only release.

Other documentation and completion

Publish changed Mintlify content through its configured connected deployment and verify the actual changed content at https://docs.anarlog.so, including skill.md, llms.txt, and llms-full.txt when affected. Mintlify and Vercel are separate publication paths; inspect current configuration rather than assuming that a website deployment also updates docs. Reuse unchanged surfaces with evidence.

Return content revisions, validation, website run URL/SHA, live changelog page and index evidence, other published docs, and any blocker or explicit deferral to the coordinator. Do not send announcements or newsletters unless separately requested.

© fastrepl, 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 .agents/skills/release-docs of fastrepl/anarlog.

Open the folder on GitHubat commit 259a04e

Compare with similar skills

Release Docs 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.

Release Docs compared with similar skills
SkillStarsUsed inTokensAuto-checkLicenceRepo updated
Release Docs this skillfastrepl/anarlog9.4k—~1.6kAutomated safety check: PassMIT
RStudio What's New Pagerstudio/rstudio5.1k—~2kAutomated safety check: PassCustom licence
Release Feature Scoringdotnet/core22k—~2.2kAutomated safety check: PassMIT
Azure App Configuration Release NotesAzure/AppConfiguration263—~3.1kAutomated safety check: PassMIT
Updating Docs For Releasestreamlit/docs178—~4kAutomated safety check: PassApache-2.0
Full Releasemrajaeim/image-pipes125—~1.3kAutomated safety check: PassMIT

Similar skills

  • RStudio What's New Page

    rstudio/rstudio

    Turns the current release's NEWS.md entries into the RStudio Desktop What's New page, picking only what Desktop users care about, then commits and opens a PR.

    5.1k GitHub stars~2k tokensUpdated yesterday
    DevelopmentAuto-check passed

  • Release Feature Scoring

    dotnet/core

    Official

    Ranks the changes in a release manifest and writes a scored features file that release notes, docs and blog posts can each cut at their own threshold.

    22k GitHub stars~2.2k tokensUpdated 2 days ago
    DevelopmentAuto-check passed

  • Azure App Configuration Release Notes

    Azure/AppConfiguration

    Official

    Writes customer-facing release notes for Azure App Configuration libraries and providers in a fixed file layout, version heading and category structure.

    263 GitHub stars~3.1k tokensUpdated 2 days ago
    DevelopmentAuto-check passed

  • Updating Docs For Release

    streamlit/docs

    Update the streamlit/docs repo for a new Streamlit release. An agent skill from streamlit/docs.

    178 GitHub stars~4k tokensUpdated yesterday
    DevelopmentAuto-check passed

  • Full Release

    mrajaeim/image-pipes

    Run a full release: update CHANGELOG, commit remaining work with incremental conventional commits, prepare an annotated v tag, and give the user manual push commands.

    125 GitHub stars~1.3k tokensUpdated 5 days ago
    DevelopmentAuto-check passed

  • Change Documentation Writer

    jsmastery-pro/skills

    Writes PR descriptions, changelog entries, release notes and postmortems from the actual commits and diff, and saves each one in the right place.

    1.4k GitHub stars~2.4k tokensUpdated 1 mo ago
    DevelopmentAuto-check: notes

More from fastrepl/anarlog

All 32 skills in this repo

  • But

    fastrepl/anarlog

    Use only in the Anarlog repository when the active checkout branch is exactly gitbutler/workspace.

    9.4k GitHub stars~5.8k tokensUpdated today
    Auto-check passed

  • Create PRs

    fastrepl/anarlog

    Use only in the Anarlog repository when the active checkout branch is exactly gitbutler/workspace.

    9.4k GitHub stars~1.2k tokensUpdated today
    Auto-check passed

  • Fix Ready PRs

    fastrepl/anarlog

    Inspect every open non-draft PR for CI failures and unresolved Cursor Bugbot findings, then fix them on the existing PR branches.

    9.4k GitHub stars~1.4k tokensUpdated today
    Auto-check passed

  • No Use Effect

    fastrepl/anarlog

    Avoid direct React useEffect usage when writing or reviewing React components and hooks.

    9.4k GitHub stars~825 tokensUpdated today
    Auto-check passed

  • QA Critical UX

    fastrepl/anarlog

    QA Anarlog's critical Pro user journey on a signed staging candidate — onboarding, responsive launch, microphone and system-audio capture, automated summaries, and cloud sync.

    9.4k GitHub stars~1.4k tokensUpdated today
    Auto-check passed

  • Reactive Sqlite UI

    fastrepl/anarlog

    Build SQLite-backed reactive UI in apps/desktop using stable patterns for reads, selection, forms, writes, and loading states.

    9.4k GitHub stars~699 tokensUpdated today
    Auto-check passed

Categories

Questions about Release Docs

What does Release Docs do?

Prepare Anarlog release notes and documentation, publish the website changelog when the app is published, and verify the live content without a separate request. Release Docs is an agent skill from fastrepl/anarlog. Prepare Anarlog release notes and documentation, publish the website changelog when the app is published, and verify the live content without a separate request.

When should I use Release Docs?

Release Docs fits situations like: tasks that involve Changelog and release notes; tasks that involve Technical writing.

How do I install Release Docs in Claude Code?

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

How do I install Release Docs in Codex?

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

Can I use Release Docs 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 fastrepl/anarlog --skill release-docs -a cursor` (or -a gemini-cli, github-copilot or opencode for the others). To copy it by hand, put the folder in .cursor/skills/release-docs, .gemini/skills/release-docs, .github/skills/release-docs and .opencode/skills/release-docs in your project.

What does Release Docs need to run?

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

Does Release Docs access the network?

SKILL.md names 2 domains. In commands or code: anarlog.so and docs.anarlog.so; the agent is likely to contact these when it follows the instructions. This is read from the text; nothing was executed.

Is Release Docs 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 Release Docs use?

Release Docs 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 Release Docs use?

About 1.6k tokens (SKILL.md is roughly 6.5k 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 Release Docs?

Skills that share tags, products or a category with Release Docs: RStudio What's New Page (rstudio/rstudio, 5.1k stars), Release Feature Scoring (dotnet/core, 22k stars), Azure App Configuration Release Notes (Azure/AppConfiguration, 263 stars) and Updating Docs For Release (streamlit/docs, 178 stars). The comparison table on this page puts their stars, adoption, token cost, safety result and licence side by side.

Who maintains Release Docs?

fastrepl (a GitHub organization) maintains it in fastrepl/anarlog, which has 9,445 GitHub stars. The repository holds 32 skills in this directory. The repository was last updated on October 7, 2026.

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