agentmods.dev

release-info-writing

release-info-writing is a skill for Claude Code from shopwareLabs/ai-coding-tools. It costs 154 tokens per session (1,484 once invoked), scanned A, original, MIT.

A drafting workflow for release information and upgrade notes in the Shopware core repository. Release information explains changes for developers who use the software.

In plain words
What is it for?
Use it to write entries for release-info and upgrade files when adding features, deprecations, or breaking changes.
Why use it?
It separates the mechanical description of a code change from the explanation of why external developers need to care.

Skill for Claude Code

Written for Claude Code: allowed-tools in frontmatter. Also seen: model in frontmatter; names the AskUserQuestion tool.

Part of the contributor-writing plugin — 5 skills shipped together

not rated 43repo +1 yesterday A scan SkillSpector: warn 154 tokens original MIT

Good fit Use it to write entries for release-info and upgrade files when adding features, deprecations, or breaking changes.

Compare 6 skills from other repositories ↓
Install with agentmods
npx agentmods add skills/shopwarelabs/ai-coding-tools/release-info-writing
View source ↗ shopwareLabs/ai-coding-tools
Install

Getting it into your agent

One page per mod, every tool's command on it. A separate URL per tool would split the same page into five that compete with each other.

Any agent
npx skills add shopwareLabs/ai-coding-tools --skill release-info-writing
Clone the repo
git clone --depth 1 https://github.com/shopwareLabs/ai-coding-tools

Made for: Claude Code.

Or install contributor-writing, the plugin that ships this one along with the rest of its 5 skills.

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.

agentmods badge for release-info-writing

README.md
[![agentmods](https://agentmods.dev/badge/skills/shopwarelabs/ai-coding-tools/release-info-writing.svg)](https://agentmods.dev/skills/shopwarelabs/ai-coding-tools/release-info-writing)
Your own site
<a href="https://agentmods.dev/skills/shopwarelabs/ai-coding-tools/release-info-writing"><img src="https://agentmods.dev/badge/skills/shopwarelabs/ai-coding-tools/release-info-writing.svg" alt="Measured on agentmods" height="20"></a>
Per session 154 Skills are progressive disclosure: only the name and description are preloaded; the body loads when the skill is used.
When invoked 1,484 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. Third-party audits
  • NVIDIA SkillSpector warn 7 Sept 2026
SkillSpector: 1 finding, up to medium

These are SkillSpector’s own severities. On a checked sample its high-severity flags on skills were ~96% false positives — a documented command, a public API, a “never do X” rule — so we show them as a caution to read, not a verdict. Why →

  • medium Excessive Agency · line 4
    Skill selects an external model or provider that may use a different account or billing plan than the operator expects. Undisclosed model switches can cause unexpected cost or quota consumption.
    Fix: Remove the model/provider override or disclose it prominently and require explicit operator approval before invoking an external coding CLI or billed model.
How audits are shown
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.

ModelPer sessionOnce invoked
Fable 5.1 $0.00154 $0.01484
Opus 5 $0.00077 $0.00742
Sonnet 5 $0.00031 $0.00297
Haiku 4.5 $0.00015 $0.00148

Measured 8d ago against content hash b8a22489e98d, method: parsed. Prices are Anthropic first-party input rates as of 2026-09-07, from the pricing page.

Security

Grade A, and why

release-info-writing 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 8d 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.

plugins/contributor-writing/skills/release-info-writing/SKILL.md · 111 lines

How it starts

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

Release Info Drafting

Draft entries for RELEASE_INFO-6.x.md and UPGRADE-6.x.md in the Shopware core repository. The skill auto-generates the mechanical "what changed" from code analysis but requires human input for "why external developers should care."

File write scope: Edit only RELEASE_INFO-6.*.md and UPGRADE-6.*.md. Read everything else.

Phase 1 — Detect Target Files

Parse .danger.php in the repo root to get the canonical file names CI enforces.

  1. Read .danger.php
  2. Look for lines matching matches('RELEASE_INFO- — extract the file name from the string argument (e.g., RELEASE_INFO-6.7.md)
  3. Look for lines matching matches('UPGRADE- or referencing UPGRADE- in failure messages — extract the file name (e.g., UPGRADE-6.8.md)
  4. Fallback: If parsing fails, glob for RELEASE_INFO-6.*.md and UPGRADE-6.*.md in the repo root. Pick the file with the highest version number.
  5. Last resort: Ask the user for the file names.

Verify both files exist before proceeding.

Phase 2 — Analyze Branch Scope

Understand the full story of the branch, not just individual changes.

  1. Get the full diff against trunk:
    • If a PR exists, use the PR diff and PR files tools
    • Otherwise, run git diff trunk...HEAD --stat and git log trunk..HEAD --oneline
  2. Use session context — what the user has been working on and why
  3. Synthesize the narrative: a PR may touch features, fixes, and cleanups. Identify what's most important — what's the story of these changes?
  4. Classify using the decision tree below
  5. If the changes are not externally relevant: tell the user with reasoning, offer to proceed anyway

Classification Decision Tree

Step 1 — Is this externally relevant?

Skip if ALL are true:

  • No public API changes (no new/changed/removed public methods, interfaces, routes)
  • No behavioral changes visible to extensions or integrations
  • No new features, extension points, or config options
  • No deprecation annotations added
  • Only test files, internal refactoring, or non-critical bug fixes

Read the full file on GitHub · 111 lines

Files

What ships with it

4 files beside SKILL.md in the same directory: the scripts, references and assets a skill reads on demand. Not counted in the per-session cost; read them before you install if any of them is executable.

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.

  1. 8d ago First seen · 111 lines · 154 tokens per session scan A b8a22489e98d

Subscribe to this mod's changes

release-info-writing is a skill published in the GitHub repository shopwareLabs/ai-coding-tools (43 stars, last pushed yesterday), licensed MIT. It adds 154 tokens to every session and 1,484 once invoked, about $0.0008 per session on Opus 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-08-30.

Claude CodeGit and workflowReleasesWriting and docsanthropicclaudemarketplacepluginsshopware
Related

Other skills, from other repositories

release

This skill should be used when the user wants to create a new release — bump version, tag, push, create GitHub release, and optionally publish to npm. Use when user says "release", "bump version", "publish", "cut a release", or "release candidate".

NikiforovAll/claude-code-marketplace · 60 tokens

changelog

Ingest Claude Code changelog entries and integrate them into the current repo. Fetch (read-only display), diff (impact analysis, no edits), status (applied versions), and apply (full integrate pipeline, explicit user intent only). Use when: 'new cc version', 'what changed in claude code', 'apply changelog', a new CC…

melodic-software/claude-code-plugins · 84 tokens

quick-pr

Split a minor change from the current work into a separate worktree and open a PR without interrupting your flow. Use when an unrelated small fix (typo, lint rule, config tweak) is sitting in a feature branch and the user wants it shipped on its own — "quick PR", "split this out", "ship this separately". Requires…

2ykwang/agent-skills · 89 tokens

release

A release guide for publishing a software package, including projects with multiple independently versioned packages in one repository, called a monorepo. It determines the release unit, updates versions using Semantic Versioning, and prepares the related GitHub release steps after approval.

tomoking2004/claude-plugins · 141 tokens

batch

Research and plan a large-scale change, then execute it in parallel across 5–30 isolated worktree agents that each open a PR.

asgeirtj/system_prompts_leaks · 30 tokens

github

GitHub via gh CLI: PRs, issues, reviews, repos, auth.

NousResearch/hermes-agent · 19 tokens