What is release-issues?

A release follow-up workflow for GitHub repositories. After a version is tagged, it finds the issues closed by the shipped pull requests and comments on those issues that the fix is available.

Use it after publishing a version, or retry it manually, to identify linked issues and post release information while leaving issue state and labels unchanged.

It keeps people who reported bugs informed when a release contains their fix. It also avoids changing the issues themselves beyond adding the release comment.

How David-Crty/databasement configures Claude Code

About the project

Databasement is a self-hosted web application for scheduling, storing, and restoring backups of several kinds of databases. It is for managing database backups across local storage, S3-compatible storage, SFTP, Samba, and other configured destinations, including databases in private networks. The catalogue instruction and MCP integration connect coding agents to its backup-management workflows.

David-Crty/databasement · 2,606 stars · on GitHub · david-crty.github.io

Reuse

Borrowing it

Nothing to install: this file belongs to David-Crty/databasement. Take a copy, put it at the same path in your own repository, and replace the rules that are about this project with yours.

Copy the file

curl -O https://raw.githubusercontent.com/David-Crty/databasement/main/.ai/skills/release-issues/SKILL.md

Clone the repo

git clone --depth 1 https://github.com/David-Crty/databasement

Made for: Claude Code.

Wrote this? Show the measurements

A badge with what this costs and how it scanned, read live from this page, so it follows the numbers instead of freezing them. Markdown for a README, HTML for a documentation site or a project page.

README.md

[![agentmods](https://agentmods.dev/badge/skills/david-crty/databasement/release-issues/github.svg)](https://agentmods.dev/skills/david-crty/databasement/release-issues)

Your own site

<a href="https://agentmods.dev/skills/david-crty/databasement/release-issues"><img src="https://agentmods.dev/badge/skills/david-crty/databasement/release-issues/github.svg" alt="Measured on agentmods" height="20"></a>

Or the 80×15 button, for a site that already has a row of RSS and ATOM ones. Only the verdict fits; the numbers stay here.

Your own site · 80×15

<a href="https://agentmods.dev/skills/david-crty/databasement/release-issues"><img src="https://agentmods.dev/badge/skills/david-crty/databasement/release-issues.svg" alt="Reviewed on agentmods" width="80" height="20"></a>

Per session 76 Skills are progressive disclosure: only the name and description are preloaded; the body loads when the skill is used.

When invoked 1,168 The whole file, excluding the scripts and references it only reads on demand.

Security scan A 0 findings. A grade says what 26 rules found in the file — not that it is safe.

Origin original No closer match found in the catalogue.

Token cost

What it costs to keep this loaded

Counted locally with the o200k_base tokenizer, which is exact for GPT models; Claude uses its own tokenizer and its counts differ. Treat this as one consistent yardstick across the catalogue rather than a bill. Prices are per million input tokens.

Model	Per session	Once invoked
Fable 5.1	$0.00076	$0.01168
Opus 5.5	$0.00030	$0.00467
Sonnet 5.5	$0.00015	$0.00234
Haiku 4.5	$0.00008	$0.00117

Measured 27d ago against content hash 3040ee89f138, method: parsed. Prices are Anthropic first-party input rates as of 2026-10-07, from the pricing page.

Security

Grade A, and why

release-issues scanned grade A with 0 findings against 26 rules in 11 categories — prompt injection, anti-refusal, data exfiltration, privilege escalation, supply chain, agent snooping, system-prompt leakage, SSRF and excessive agency — measured 27d ago.

A static scan of the body, not an audit. Every finding is printed with the line that produced it so you can judge whether it matters here. A mod is markdown that instructs an agent; that is exactly why what it instructs is worth reading.

Nothing flagged

None of the 26 patterns this scan looks for appear in this file: no shell pipes, no recursive deletes, no credential paths, no hidden text, no instruction-override or anti-refusal phrasing, no agent-config snooping. That is not a guarantee, it is the absence of the things that are checkable.

.ai/skills/release-issues/SKILL.md · 90 lines

How it starts

The opening of the file, as written. The whole thing — 90 lines — stays where its author put it; the contents beside it link to each section on GitHub.

Release issues

A release just went out. Tell the people who reported each issue it resolves, on the issue itself, that the fix is available and what they need to do. Read and comment only: never edit, close, reopen or label an issue, and never touch the repository.

Context

Version released: $ARGUMENTS (required, x.y.z)
Repository: !gh repo view --json nameWithOwner --jq .nameWithOwner
Maintainer (never ping): !gh api user --jq .login

If $ARGUMENTS is empty or is not an x.y.z version, stop and say Usage: /release-issues x.y.z. If git rev-parse -q --verify refs/tags/vx.y.z finds nothing, stop: the release is not tagged yet.

Steps

Range. git fetch --tags --quiet, then the previous release is git describe --tags --abbrev=0 --match 'v*' vx.y.z^. The release's commits are git log <previous>..vx.y.z --no-merges --format='%h %s%n%b%n---'.
Linked issues. Collect, deduplicated:
- for every (#NNN) PR suffix in a subject, the issues that PR closes: gh pr view NNN --json title,body,closingIssuesReferences;
- issues a commit body closes itself (Fixes #N, Closes #N, Resolves #N, any tense or case).
An issue only mentioned (see #N, (#N) in prose) is not linked: skip it. Skip every PR titled fix(security): and the issues it closes: security fixes are disclosed through their advisory, not here. If nothing is linked, report that and stop.
Per issue, read it with gh issue view N --json number,title,state,author,body,comments, then:
- Skip it if a comment already links releases/tag/vx.y.z (this release was already announced there, so a rerun posts nothing twice).
- Who to ping: the author, plus every commenter who says they hit the same problem or asked for the same thing. Never the maintainer, never a bot ([bot] suffix, coderabbitai, github-actions). If nobody is left, skip the issue.
- What shipped: read the closing PR's body (it explains the why and the trade-offs) and the vx.y.z entries in CHANGELOG.md. Compare against what the reporter actually asked for or described, and say plainly if part of it was solved differently or not at all.

Read the full file on GitHub · 90 lines

Changes

What this file has done since we first saw it

Hashed on every crawl. A supply-chain change to an agent config is a question of when, not whether, so the history is kept rather than the latest state alone.

27d ago First seen · 90 lines · 76 tokens per session scan A 3040ee89f138

Subscribe to this mod's changes

release-issues is a skill published in the GitHub repository David-Crty/databasement (2,606 stars, last pushed 2d ago), licensed MIT. It adds 76 tokens to every session and 1,168 once invoked, about $0.0003 per session on Opus 5.5. A static security scan graded it A with 0 findings. No closer match exists in the catalogue, so it is treated as the original; first seen 2026-10-11.

Databases Git and workflow Releases backup mariadb mysql s3 sqlite

release-issues next to 6 skills from other repositories
Mod	Type	Stars	Last push	Licence	Scan	Tokens	Works with
release-issuesDavid-Crty/databasement	Skill	2.6k	2d ago	MIT	A	76	Claude Code
draft-release-notesprisma/orm	Skill	48k	yesterday	Apache-2.0	A	174	Claude Code, Codex
publish-npm-versionprisma/orm	Skill	48k	yesterday	Apache-2.0	A	182	Claude Code, Codex
mysqlericrisco/rsc-harness	Skill	503	2d ago	MIT	A	116	Claude Code, Codex
gh-pull-requestapache/skywalking-banyandb	Skill	355	yesterday	Apache-2.0	A	37	Claude Code
releasematrixorigin/memoria	Skill	623	2d ago	Apache-2.0	A	27	Claude Code, Codex
Drizzle ORM TestingPramodDutta/qaskills	Skill	245	3d ago	MIT	A	36	Claude Code, Codex

databasement: Skill for Claude Code