uselink-changelog

uselink-changelog is a skill for Claude Code from compilet-dev/agent-skill-uselink. It costs 50 tokens per session (1,320 once invoked), scanned A, original, MIT.

A skill that creates release notes from Git history and publishes them as a shareable Uselink page. Release notes summarize changes included in a version, time period, or deployment.

In plain words
What is it for?
Use it for version changelogs, weekly shipping summaries, sprint updates, and release notes between Git tags.
Why use it?
It removes the manual work of collecting commits and, when available, merged pull requests. It gives stakeholders one page to read and share.

Skill for Claude Code

Written for Claude Code: allowed-tools in frontmatter.

Good fit Use it for version changelogs, weekly shipping summaries, sprint updates, and release notes between Git tags.

Compare 6 skills from other repositories ↓
Install with agentmods
npx agentmods add skills/compilet-dev/agent-skill-uselink/uselink-changelog
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 compilet-dev/agent-skill-uselink --skill uselink-changelog
Clone the repo
git clone --depth 1 https://github.com/compilet-dev/agent-skill-uselink

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.

agentmods badge for uselink-changelog

README.md
[![agentmods](https://agentmods.dev/badge/skills/compilet-dev/agent-skill-uselink/uselink-changelog/github.svg)](https://agentmods.dev/skills/compilet-dev/agent-skill-uselink/uselink-changelog)
Your own site
<a href="https://agentmods.dev/skills/compilet-dev/agent-skill-uselink/uselink-changelog"><img src="https://agentmods.dev/badge/skills/compilet-dev/agent-skill-uselink/uselink-changelog/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.

agentmods 80×15 button for uselink-changelog

Your own site · 80×15
<a href="https://agentmods.dev/skills/compilet-dev/agent-skill-uselink/uselink-changelog"><img src="https://agentmods.dev/badge/skills/compilet-dev/agent-skill-uselink/uselink-changelog.svg" alt="Reviewed on agentmods" width="80" height="20"></a>
Per session 50 Skills are progressive disclosure: only the name and description are preloaded; the body loads when the skill is used.
When invoked 1,320 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.

ModelPer sessionOnce invoked
Fable 5.1 $0.00050 $0.01320
Opus 5 $0.00025 $0.00660
Sonnet 5 $0.00010 $0.00264
Haiku 4.5 $0.00005 $0.00132

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

Security

Grade A, and why

uselink-changelog 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 10d 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.

skills/uselink-changelog/SKILL.md · 148 lines

How it starts

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

Generate formatted release notes from git history and publish as a shareable uselink page.

When to Use

  • "Generate release notes for this version"
  • "What shipped this week? Share it."
  • "Create a changelog from v1.2 to v1.3"
  • "Share what we deployed today"

Prerequisites

which uselink || echo "MISSING"
test -f ~/.uselink/config.json && echo "OK" || echo "NO_CONFIG"

Workflow

1. Determine range

Between tags:

git tag --sort=-version:refname | head -5
git log <old-tag>..<new-tag> --oneline --no-merges

Time-based (last week, last sprint):

git log --since="7 days ago" --oneline --no-merges

Since last deploy (if deploy tags exist):

git log $(git describe --tags --abbrev=0)..HEAD --oneline --no-merges

If no range specified, default to the last 7 days.

2. Gather data

# All commits in range
git log <range> --format="%H|%an|%s|%ai" --no-merges

# PRs merged in range (if gh is available)
gh pr list --state merged --search "merged:>=<start-date>" --limit 100 \
  --json number,title,author,labels,mergedAt 2>/dev/null

# Group by conventional commit type
git log <range> --oneline --no-merges | grep -c "^[a-f0-9]* feat"
git log <range> --oneline --no-merges | grep -c "^[a-f0-9]* fix"

3. Categorize changes

Group into sections by commit prefix or PR labels:

Category Commit prefix / label Icon
New Features feat, feature
Bug Fixes fix, bugfix 🐛
Improvements refactor, perf, improve
Documentation docs 📝
Infrastructure ci, build, chore, deps 🔧
Breaking Changes BREAKING in body, ! suffix ⚠️

If commits don't follow conventional format, categorize by reading the diff.

4. Generate HTML

Write to /tmp/uselink-changelog-<version>-<timestamp>.html.

<!-- Version header -->
<div class="card">
  <h3>{{VERSION_OR_TITLE}}</h3>
  <p class="muted">{{DATE_RANGE}} · {{COMMIT_COUNT}} commits · {{CONTRIBUTOR_COUNT}} contributors</p>
</div>

<!-- Highlights (top 3-5 most important changes) -->
<h2>Highlights</h2>
<div class="card">
  <ul>
    <li><strong>{{HIGHLIGHT}}</strong> — {{ONE_SENTENCE_DESCRIPTION}}</li>
  </ul>
</div>

<!-- New Features -->
<h2>✨ New Features</h2>
<div class="card">
  <ul><li>{{FEATURE_DESCRIPTION}} <span class="muted">(#{{PR_NUM}})</span></li></ul>
</div>

<!-- Bug Fixes -->
<h2>🐛 Bug Fixes</h2>
<div class="card">
  <ul><li>{{FIX_DESCRIPTION}} <span class="muted">(#{{PR_NUM}})</span></li></ul>
</div>

<!-- Improvements -->
<h2>⚡ Improvements</h2>
<div class="card">
  <ul><li>{{IMPROVEMENT}}</li></ul>
</div>

<!-- Breaking Changes (if any) -->
<h2>⚠️ Breaking Changes</h2>
<div class="card">
  <ul><li><strong>{{BREAKING}}</strong> — {{MIGRATION_NOTES}}</li></ul>
</div>

<!-- Contributors -->
<h2>Contributors</h2>
<p>{{CONTRIBUTOR_LIST}}</p>

Read the full file on GitHub · 148 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.

  1. 10d ago First seen · 148 lines · 50 tokens per session scan A d84004786baf

Subscribe to this mod's changes

uselink-changelog is a skill published in the GitHub repository compilet-dev/agent-skill-uselink (2 stars, last pushed 3mo ago), licensed MIT. It adds 50 tokens to every session and 1,320 once invoked, about $0.0003 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-31.

Related

Other skills, from other repositories

release

Guide through the Cortex TMS release process — version bump, changelog, sync, tag, publish. Every step requires user approval.

cortex-tms/cortex-tms · 29 tokens

surface-after-care

Regelmäßiger Pflegedurchlauf für ein bereits veröffentlichtes GitHub-Repository (Stufe 1, günstig und oft wiederholbar): zuerst alle Distributionsflächen des Projekts ermitteln (npm, PyPI, Registries, Marketplaces, Stores, Website) und Änderungen später dorthin spiegeln, dann Topics setzen, Privacy-Gate, Dokumente auf…

ellmos-ai/skills · 283 tokens

yolo-finish

Use when a feature is implemented and verified, to land it. Default path is PR + CI check, with the ship gate confirming before the irreversible merge; fast-local is the escape hatch. Includes the risk classifier whose hard triggers always stop for a human. Triggers on "ship it", "land this", "open a PR", or as the…

CoriChui/yolo · 82 tokens

changelog-generator

Generate CHANGELOG.md from git history grouped by Conventional Commit types. Triggers on "generate changelog", "write changelog", "release notes".

luqiang-code/claude-code-skills · 33 tokens

version-bump

Automated semantic versioning and release workflow for Claude Code plugins. Handles version increments across package.json, marketplace.json, plugin.json manifests, build verification, git tagging, GitHub releases, and changelog generation. NPM publishing is the final human-required handoff because the maintainer…

thedotmack/claude-mem · 64 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