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

Release Kanban Md

by antopolskiy in antopolskiy/kanban-md

Release kanban-md through its tag-triggered GoReleaser workflow, monitor CI, recover safely from failures, and publish user-facing GitHub release notes.

MITAuto-check passedProductivity & Automation

Install Release Kanban Md

skills CLI
$ npx skills add antopolskiy/kanban-md --skill release-kanban-md -a claude-code

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

GitHub CLI
$ gh skill install antopolskiy/kanban-md release-kanban-md --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/antopolskiy/kanban-md.git skills-src && mkdir -p .claude/skills && cp -r skills-src/.agents/skills/release-kanban-md .claude/skills/release-kanban-md && 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-kanban-md
GitHub stars
223
Token cost
~1.2k tokens
SKILL.md length
534 words
Files
2 (incl. references)
Skills in repo
7
Repo updated
First seen
Licence
MIT

At a glance

Release kanban-md through its tag-triggered GoReleaser workflow, monitor CI, recover safely from failures, and publish user-facing GitHub release notes.

  • Works in 6 steps: Preflight → Inspect changes and choose the version → Tag and push → …
  • The user asks to release
  • SKILL.md covers Release invariants, 1. Preflight, 2. Inspect changes and choose… and 3. Tag and push, plus 3 more sections
  • Calls git, gh and make

What it does

Release Kanban Md is an agent skill from antopolskiy/kanban-md. Release kanban-md through its tag-triggered GoReleaser workflow, monitor CI, recover safely from failures, and publish user-facing GitHub release notes. Use when the user asks to release, tag, publish, or prepare release notes for kanban-md. Do not use for ordinary commits or unreleased changelog edits.

Its SKILL.md is about 1.2k tokens, which your agent loads only when the skill is triggered. The skill folder holds 2 other files, including reference files (for example `references/release-notes.md`).

It sits in Productivity & Automation, covering Task management and Changelog and release notes. It works with GitHub. The repository describes itself as: File-based kanban board for autonomous agentic loop. CLI and TUI for multi-agent workflows. Skills included. The licence is MIT.

When your agent uses it

  • The user asks to release
  • Prepare release notes for kanban-md
  • Ordinary commits
  • Unreleased changelog edits

Example prompts

  • “/release-kanban-md”

Requirements

  • Pre-approved tools (allowed-tools): Bash(git *), Bash(gh *), Bash(make *), Bash(go *), Bash(golangci-lint *)

Workflow steps

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

  1. Preflight
  2. Inspect changes and choose the version
  3. Tag and push
  4. Watch the release workflow
  5. Write and publish release notes
  6. Verify the finished release

What it can do on your machine

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

  • Tool permissions

    Pre-approves these tools, so the agent can use them without asking each time:

    • Bash(git *)
    • Bash(gh *)
    • Bash(make *)
    • Bash(go *)
    • Bash(golangci-lint *)

    From allowed-tools in the SKILL.md frontmatter.

  • Runs code

    Shell commands in SKILL.md call:

    • git
    • gh
    • make

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

  • Network

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

Release Kanban Md loads about 1.2k tokens when it runs, and up to ~1.7k if it reads all its reference files. Until then it costs about 81 tokens; SKILL.md has 534 words of instructions outside code blocks.

Always · name and description, kept in context so the agent knows when to use it
~81
When it runs · the whole SKILL.md, loaded when a task matches
~1.2k
With references · SKILL.md plus every file in references/, read only if the agent opens them
~1.7k

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 antopolskiy/kanban-md at commit e3816f2, republished under its MIT licence (© antopolskiy). 534 words, ~1,152 tokens.

Download SKILL.mdSave it as .claude/skills/release-kanban-md/SKILL.md (or your agent's skills folder). This skill also uses 1 other file; get the full folder from GitHub.
name
release-kanban-md
description
Release kanban-md through its tag-triggered GoReleaser workflow, monitor CI, recover safely from failures, and publish user-facing GitHub release notes. Use when the user asks to release, tag, publish, or prepare release notes for kanban-md. Do not use for ordinary commits or unreleased changelog edits.
allowed-tools
Bash(git *), Bash(gh *), Bash(make *), Bash(go *), Bash(golangci-lint *)

Release kanban-md

Carry an explicitly requested release from preflight through a verified GitHub release. A request to inspect, plan, or draft a release does not authorize pushing a tag or editing a live release; perform remote mutations only when the user has asked to release or publish.

Release invariants

  • A version tag triggers the GitHub Actions release workflow, which uses GoReleaser to create the GitHub release and its artifacts.
  • Never run gh workflow run release; tag push already triggers the workflow and a manual dispatch can create a duplicate build.
  • Never run gh release create. Let GoReleaser create the release, then update its title and notes with gh release edit after CI succeeds.
  • Never move, delete, or reuse a tag that has been pushed. After a non-transient failure, fix the cause and choose a new, higher version.
  • Decide the version autonomously using semver: patch for fixes, minor for backward-compatible features, and major for breaking changes. Do not ask the user to confirm the version.
  • A release is complete only when the workflow is green, the generated release exists, its human-written notes are published, and the final release is verified.

1. Preflight

Work from a clean, up-to-date main containing exactly the changes intended for release. Do not discard, overwrite, or silently stash unrelated user changes.

bash
git branch --show-current
git status --short
git fetch origin --tags
git status --short --branch
git tag --sort=-version:refname | head -20
gh release list --limit 100

If main is dirty, diverged, or missing intended work, resolve that through the normal project development workflow before releasing. Run the release-appropriate verification, normally:

bash
make precommit

Do not tag a revision that fails required tests or lint.

2. Inspect changes and choose the version

Identify the previous release tag and review the user-visible changes, including outside contributions that may need attribution:

bash
git log vPREVIOUS..HEAD --oneline
git diff vPREVIOUS..HEAD --stat
git diff vPREVIOUS..HEAD

Choose vX.Y.Z according to semver and confirm that it does not already exist locally or remotely. The tag must identify the verified main commit.

3. Tag and push

Push main and the exact new tag. Do not use --tags, which can publish other local tags unintentionally.

bash
git push origin main
git tag vX.Y.Z
git push origin vX.Y.Z
Show full SKILL.md (215 more words)Show less

4. Watch the release workflow

Find the run associated with the new tag and watch it to completion:

bash
gh run list --workflow release --limit 10
gh run watch <RUN_ID>

Confirm the selected run is for vX.Y.Z. Do not publish release notes before the workflow is green.

If the workflow fails:

  1. Inspect the failed logs with gh run view <RUN_ID> --log-failed.
  2. If the failure is clearly transient, rerun only the failed jobs with gh run rerun <RUN_ID> --failed, then watch the run again.
  3. If code, tests, lint, configuration, or packaging must change, stop the release attempt. Fix and merge the problem through the normal development workflow, verify main, choose a new higher semver, and push a new tag.

Do not delete the failed tag or partially generated release unless the user explicitly requests that separate cleanup.

5. Write and publish release notes

Once CI is green, read references/release-notes.md and draft the notes from the full diff, commits, and relevant pull-request authors. Release notes must explain what users can now do, not merely restate commit messages.

Publish from a notes file so shell quoting cannot corrupt Markdown:

bash
gh release edit vX.Y.Z \
  --title 'vX.Y.Z "Codename" — Short Theme' \
  --notes-file <RELEASE_NOTES_FILE>

6. Verify the finished release

bash
gh release view vX.Y.Z
gh run view <RUN_ID>

Confirm the workflow conclusion is successful, the release title and notes are correct, and GoReleaser attached the expected artifacts. Report the version, release URL, workflow result, and any recovery actions to the user.

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

Files

SKILL.md and 1 other file (references) in .agents/skills/release-kanban-md of antopolskiy/kanban-md.

  • SKILL.md
  • references/release-notes.md

Open the folder on GitHubat commit e3816f2

Compare with similar skills

Release Kanban Md 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 Kanban Md compared with similar skills
SkillStarsUsed inTokensAuto-checkLicenceRepo updated
Release Kanban Md this skillantopolskiy/kanban-md223—~1.2kAutomated safety check: PassMIT
Kanvibe Release Deployrookedsysc/kanvibe144—~12kAutomated safety check: NotesAGPL-3.0
OpenObserve PR Briefopenobserve/openobserve22k—~1.8kAutomated safety check: PassAGPL-3.0
Agent Kanban Task Workersaltbo/agent-kanban488—~855Automated safety check: PassCustom licence
Worklogtokenbender/agent-guides367—~1.6kAutomated safety check: PassApache-2.0
Pmcoreyhaines31/makerskills851—~2.2kAutomated safety check: PassMIT

Similar skills

  • Kanvibe Release Deploy

    rookedsysc/kanvibe

    A skill your agent uses whenever releasing or deploying KanVibe desktop from a clean, up-to-date dev checkout: ask only for the target version and release-note approval, then let the AI update…

    144 GitHub stars~12k tokensUpdated today
    DevelopmentAuto-check: notes

  • OpenObserve PR Brief

    openobserve/openobserve

    Produces a read-only morning brief of your open pull requests across the openobserve GitHub org, with a next step for each and a reminder for idle ones.

    22k GitHub stars~1.8k tokensUpdated yesterday
    Productivity & AutomationAuto-check passed

  • Agent Kanban Task Worker

    saltbo/agent-kanban

    Lets an agent read, claim, update and submit an assigned Agent Kanban task through the Realmroot Toolbox CLI, with progress notes and a review handoff.

    488 GitHub stars~855 tokensUpdated 9 days ago
    Productivity & AutomationAuto-check passed

  • Worklog

    tokenbender/agent-guides

    Issue-led atomic work logging. An agent skill from tokenbender/agent-guides.

    367 GitHub stars~1.6k tokensUpdated 2 mo ago
    Productivity & AutomationAuto-check passed

  • Pm

    coreyhaines31/makerskills

    When you want to manage projects across your businesses using a kanban + Eisenhower methodology.

    851 GitHub stars~2.2k tokensUpdated 2 days ago
    Productivity & AutomationAuto-check passed

  • Gh CLI

    farm-fe/farm

    A skill your agent uses when working with GitHub via the gh CLI - managing PRs, issues, releases, repos, workflows, searching code, or calling the GitHub API.

    5.6k GitHub stars~1.5k tokensUpdated 19 days ago
    DevelopmentAuto-check passed

More from antopolskiy/kanban-md

  • Kanban Md

    antopolskiy/kanban-md

    Manage project tasks using kanban-md, a file-based kanban board CLI.

    223 GitHub stars~4k tokensUpdated 5 days ago
    Auto-check passed

  • Test Kanban Md

    antopolskiy/kanban-md

    Plan and run verification for kanban-md changes, including test-driven bug fixes, Go package tests, CLI end-to-end tests, TUI behavior and snapshots, lint, and precommit checks.

    223 GitHub stars~737 tokensUpdated 5 days ago
    Auto-check passed

  • Evolve Kanban Md Formats

    antopolskiy/kanban-md

    Evolve kanban-md config.yml schemas and task Markdown frontmatter without breaking existing boards.

    223 GitHub stars~795 tokensUpdated 5 days ago
    Auto-check passed

  • Kanban Based Development

    antopolskiy/kanban-md

    Autonomous, parallel-safe development workflow using kanban-md.

    223 GitHub stars~2.3k tokensUpdated 5 days ago
    Auto-check passed

  • Design Kanban Md Output

    antopolskiy/kanban-md

    Preserve and evolve kanban-md table, compact, and JSON output contracts.

    223 GitHub stars~767 tokensUpdated 5 days ago
    Auto-check passed

  • Kanban Md Principal Owner

    antopolskiy/kanban-md

    Review kanban-md feature requests, issues, PRs, and design proposals for product fit, domain-model growth, configurability, and compatibility.

    223 GitHub stars~1.7k tokensUpdated 5 days ago
    Auto-check passed

Works with

Categories

Questions about Release Kanban Md

What does Release Kanban Md do?

Release kanban-md through its tag-triggered GoReleaser workflow, monitor CI, recover safely from failures, and publish user-facing GitHub release notes. Release Kanban Md is an agent skill from antopolskiy/kanban-md. Release kanban-md through its tag-triggered GoReleaser workflow, monitor CI, recover safely from failures, and publish user-facing GitHub release notes.

When should I use Release Kanban Md?

Release Kanban Md fits situations like: the user asks to release; prepare release notes for kanban-md; ordinary commits; unreleased changelog edits.

How do I install Release Kanban Md in Claude Code?

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

How do I install Release Kanban Md in Codex?

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

Can I use Release Kanban Md 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 antopolskiy/kanban-md --skill release-kanban-md -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-kanban-md, .gemini/skills/release-kanban-md, .github/skills/release-kanban-md and .opencode/skills/release-kanban-md in your project.

What does Release Kanban Md need to run?

Going by SKILL.md and its folder, Release Kanban Md needs the command-line tools its instructions call (git, gh and make). Its frontmatter pre-approves these tools: Bash(git *), Bash(gh *), Bash(make *), Bash(go *), Bash(golangci-lint *).

Does Release Kanban Md access the network?

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

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

Release Kanban Md 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 Kanban Md use?

About 1.2k tokens (SKILL.md is roughly 4.6k characters). Agents keep only the skill's name and description in context until a task matches; then they load SKILL.md in full. Its references folder adds about 577 tokens, read only when the agent opens those files.

What are the alternatives to Release Kanban Md?

Skills that share tags, products or a category with Release Kanban Md: Kanvibe Release Deploy (rookedsysc/kanvibe, 144 stars), OpenObserve PR Brief (openobserve/openobserve, 22k stars), Agent Kanban Task Worker (saltbo/agent-kanban, 488 stars) and Worklog (tokenbender/agent-guides, 367 stars). The comparison table on this page puts their stars, adoption, token cost, safety result and licence side by side.

Who maintains Release Kanban Md?

antopolskiy (a GitHub user) maintains it in antopolskiy/kanban-md, which has 223 GitHub stars. The repository holds 7 skills in this directory. The repository was last updated on October 5, 2026.

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