Agent skill

Polish Notes

by coreos in coreos/chunkah

Polish raw GitHub release notes into user-impact-focused summaries.

Apache-2.0Auto-check passedDevelopment

Install Polish Notes

skills CLI
$ npx skills add coreos/chunkah --skill polish-notes -a claude-code

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

GitHub CLI
$ gh skill install coreos/chunkah polish-notes --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/coreos/chunkah.git skills-src && mkdir -p .claude/skills && cp -r skills-src/.agents/skills/polish-notes .claude/skills/polish-notes && 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
polish-notes
GitHub stars
148
Token cost
~759 tokens
SKILL.md length
347 words
Files
1
Skills in repo
4
Repo updated
First seen
Licence
Apache-2.0

At a glance

Polish raw GitHub release notes into user-impact-focused summaries.

  • Works in 5 steps: Use gh release list --repo… → For each PR entry, parse the PR number… → From the PR body and commit messages,… → …
  • Preparing release notes for a new chunkah version
  • SKILL.md covers Input, Process, Output format and Example, plus 1 more section
  • Calls gh and just

What it does

Polish Notes is an agent skill from coreos/chunkah. Polish raw GitHub release notes into user-impact-focused summaries. Use when preparing release notes for a new chunkah version.

Its SKILL.md is about 760 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 GitHub. The repository describes itself as: An OCI building tool for content-based layers. The licence is Apache-2.0.

When your agent uses it

  • Preparing release notes for a new chunkah version
  • Tasks that involve Changelog and release notes

Example prompts

  • “/polish-notes”

Workflow steps

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

  1. Use gh release list --repo coreos/chunkah --limit 5 to fetch recent
  2. For each PR entry, parse the PR number from its URL, then use `gh pr view
  3. From the PR body and commit messages, determine the user-facing impact of
  4. Write a brief summary emphasizing impact to users, not implementation
  5. Categorize each item into one of the sections below, using the previous

What it can do on your machine

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

    • gh
    • just

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

  • Network

    No URLs in SKILL.md. Its commands use gh, 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

Polish Notes loads about 759 tokens when it runs. Until then it costs about 35 tokens; SKILL.md has 347 words of instructions outside code blocks.

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

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 coreos/chunkah at commit 780bcd2, republished under its Apache-2.0 licence (© coreos). 347 words, ~759 tokens.

Download SKILL.mdSave it as .claude/skills/polish-notes/SKILL.md (or your agent's skills folder).
name
polish-notes
description
Polish raw GitHub release notes into user-impact-focused summaries. Use when preparing release notes for a new chunkah version.

Polish release notes

Polish raw GitHub-generated release notes for chunkah.

Input

The user provides the version to release (e.g. v0.4.0 or 0.4.0) and optionally a path to a file containing raw release notes. Strip any v prefix to get the bare version (e.g. 0.4.0).

If no file path is provided, run just release generate-notes <bare-version> to fetch raw notes from GitHub. Request to run in the host context if you get a 403.

The raw notes contain entries in this format:

text
* <PR title> by @<author> in <PR URL>

Process

  1. Use gh release list --repo coreos/chunkah --limit 5 to fetch recent release tags, then gh release view <tag> --repo coreos/chunkah to read their release notes. Use these as a reference for how items were categorized in past releases.
  2. For each PR entry, parse the PR number from its URL, then use gh pr view <number> --repo coreos/chunkah --json body,commits to fetch the PR description and commit messages. Fetch all PR details in parallel to minimize latency.
  3. From the PR body and commit messages, determine the user-facing impact of the change (e.g. performance improvement, bug fix, new feature).
  4. Write a brief summary emphasizing impact to users, not implementation details. Keep it to 1-3 sentences.
  5. Categorize each item into one of the sections below, using the previous release notes as a guide for consistency.

Output format

Group items under these section headings (omit sections with no items):

  • Major changes - New features, significant behavior changes, performance improvements, or breaking changes that users should know about.
  • Minor changes - Small enhancements, new options, improved warnings, or documentation updates that are user-visible.
  • Internal changes - Refactoring, CI fixes, test improvements, or code cleanup with no direct user-facing impact.
  • Packaging changes - Dependency bumps, spec file changes, Packit fixes, or build system updates.

Rewrite each entry as:

text
* <user-impact summary> (<PR URL>)

If the raw notes contain a "## New Contributors" section, preserve it verbatim at the bottom of the output, after all other sections.

Example

Input:

text
* tar: stream file reads instead of buffering into `Vec<u8>` by @jlebon in
  https://github.com/coreos/chunkah/pull/72

Output:

markdown
## Major changes

* Dramatically reduced memory usage by streaming file reads instead of
  buffering entire files and tar layers into memory, cutting peak RSS to ~75 MB
  (from ~6.5 GB of allocations for an FCOS image)
  (https://github.com/coreos/chunkah/pull/72)

Final steps

After drafting the output, check for spelling and grammar issues and fix them. Write the final result to .release-notes-<bare-version>.md in the repo root (e.g. .release-notes-0.4.0.md).

© coreos, Apache-2.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/polish-notes of coreos/chunkah.

Open the folder on GitHubat commit 780bcd2

Compare with similar skills

Polish Notes 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.

Polish Notes compared with similar skills
SkillStarsUsed inTokensAuto-checkLicenceRepo updated
Polish Notes this skillcoreos/chunkah148—~759Automated safety check: PassApache-2.0
Cutting A ReleaseTriliumNext/Trilium38k—~3.2kAutomated safety check: PassAGPL-3.0
Mole CLI Release Flowtw93/Mole70k—~2.5kAutomated safety check: PassGPL-3.0
Draft Release Notesjamiepine/voicebox57k—~941Automated safety check: PassMIT
Mole Release Notes Publishertw93/Mole70k—~1.9kAutomated safety check: PassGPL-3.0
Release Bumpjamiepine/voicebox57k—~1.1kAutomated safety check: PassMIT

Similar skills

  • Cutting A Release

    TriliumNext/Trilium

    A skill your agent uses when cutting, preparing, or debugging a Trilium release — bumping the monorepo version, tagging, or diagnosing a failed "Release" workflow run.

    38k GitHub stars~3.2k tokensUpdated today
    DevelopmentAuto-check passed
  • Runbook for assessing and executing a Mole CLI release: distribution channels, pre-flight checks, capital-V tags, build artifacts and the handoff to curated release notes.

    70k GitHub stars~2.5k tokensUpdated today
    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
  • 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
  • Cut Release

    jfernandez/bpftop

    Cut a new versioned release of bpftop — pick the version, open a version-bump PR, sign-tag the merge commit on main, and draft GitHub release notes in the project's established format.

    2.7k GitHub stars~2k tokensUpdated 1 mo ago
    DevelopmentAuto-check passed

More from coreos/chunkah

  • Alloc Tracker

    coreos/chunkah

    A skill your agent uses when you need to measure per-phase memory allocation statistics to investigate memory usage.

    148 GitHub stars~526 tokensUpdated 2 days ago
    Auto-check passed
  • Extract Oci Archive

    coreos/chunkah

    A skill your agent uses when you need to extract an OCI archive to inspect its contents, get the rootfs layer, or read the image config.

    148 GitHub stars~263 tokensUpdated 2 days ago
    Auto-check passed
  • Benchmark Packing

    coreos/chunkah

    Benchmark chunkah packing algorithm changes against a series of OCI images.

    148 GitHub stars~1.1k tokensUpdated 2 days ago
    Auto-check passed

Works with

Categories

Questions about Polish Notes

What does Polish Notes do?

Polish raw GitHub release notes into user-impact-focused summaries. Polish Notes is an agent skill from coreos/chunkah. Polish raw GitHub release notes into user-impact-focused summaries.

When should I use Polish Notes?

Polish Notes fits situations like: preparing release notes for a new chunkah version; tasks that involve Changelog and release notes.

How do I install Polish Notes in Claude Code?

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

How do I install Polish Notes in Codex?

Run `npx skills add coreos/chunkah --skill polish-notes -a codex`. Or copy the skill folder (.agents/skills/polish-notes in coreos/chunkah) into .agents/skills/polish-notes in your project. Codex loads it when a task matches its description.

Can I use Polish Notes 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 coreos/chunkah --skill polish-notes -a cursor` (or -a gemini-cli, github-copilot or opencode for the others). To copy it by hand, put the folder in .cursor/skills/polish-notes, .gemini/skills/polish-notes, .github/skills/polish-notes and .opencode/skills/polish-notes in your project.

What does Polish Notes need to run?

Going by SKILL.md and its folder, Polish Notes needs the command-line tools its instructions call (gh and just).

Does Polish Notes access the network?

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

Is Polish Notes 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 Polish Notes use?

Polish Notes is published under the Apache-2.0 licence (the repository's licence). It allows redistribution, so the full SKILL.md is shown on this page.

How many tokens does Polish Notes use?

About 759 tokens (SKILL.md is roughly 3k 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 Polish Notes?

Skills that share tags, products or a category with Polish Notes: Cutting A Release (TriliumNext/Trilium, 38k stars), Mole CLI Release Flow (tw93/Mole, 70k stars), Draft Release Notes (jamiepine/voicebox, 57k stars) and Mole Release Notes Publisher (tw93/Mole, 70k stars). The comparison table on this page puts their stars, adoption, token cost, safety result and licence side by side.

Who maintains Polish Notes?

coreos (a GitHub organization) maintains it in coreos/chunkah, which has 148 GitHub stars. The repository holds 4 skills in this directory. The repository was last updated on October 5, 2026.

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