Borrowing it
Nothing to install: this file belongs to jmrplens/gitlab-mcp-server. Take a copy, put it at the same path in your own repository, and replace the rules that are about this project with yours.
curl -O https://raw.githubusercontent.com/jmrplens/gitlab-mcp-server/main/.github/skills/generate-release-notes/SKILL.mdgit clone --depth 1 https://github.com/jmrplens/gitlab-mcp-serverWrote 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.
[](https://agentmods.dev/skills/jmrplens/gitlab-mcp-server/generate-release-notes)<a href="https://agentmods.dev/skills/jmrplens/gitlab-mcp-server/generate-release-notes"><img src="https://agentmods.dev/badge/skills/jmrplens/gitlab-mcp-server/generate-release-notes/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.
<a href="https://agentmods.dev/skills/jmrplens/gitlab-mcp-server/generate-release-notes"><img src="https://agentmods.dev/badge/skills/jmrplens/gitlab-mcp-server/generate-release-notes.svg" alt="Reviewed on agentmods" width="80" height="20"></a>- NVIDIA SkillSpector pass
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.00067 | $0.01395 |
| Opus 5.5 | $0.00027 | $0.00558 |
| Sonnet 5.5 | $0.00013 | $0.00279 |
| Haiku 4.5 | $0.00007 | $0.00139 |
Grade A, and why
generate-release-notes 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 1mo 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.
How it starts
The opening of the file, as written. The whole thing — 170 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Generate Release Notes
Overview
Generate polished, categorized release notes for a GitLab project by comparing two Git refs. This skill orchestrates multiple MCP tools to gather commits, merged merge requests, and diffs, then produces human-readable release notes.
When to Use
- Creating release notes for a new tag or version
- Summarizing changes between any two Git references (tags, branches, SHAs)
- Preparing changelog entries for a release
- Reviewing what changed between deployments
Prerequisites
- A GitLab project accessible via the MCP server
- Two valid Git refs (tags, branches, or commit SHAs) to compare
Workflow
Step 1: Identify the Project and Refs
Determine the project ID (or namespace/project path) and the two refs to compare.
Common patterns:
- Tag to tag:
v1.0.0→v1.1.0 - Tag to branch:
v1.0.0→main - Branch to branch:
release/1.0→release/1.1 - Commit to tag:
abc1234→v1.1.0
Step 2: Gather Data (Choose One Approach)
Approach A: Manual Orchestration (Recommended)
Orchestrate the tools manually and categorize the results yourself. The tool names below are the meta surface (GITLAB_MCP_TOOL_SURFACE=meta); on the default dynamic surface the same calls go through gitlab_execute_action with the canonical action IDs repository.compare and merge_request.list, and on the individual surface the tools are gitlab_repository_compare and gitlab_mr_list:
-
Compare refs to get commits and diffs:
Use gitlab_repository with action "compare": - project_id: <project_id> - from: <base_ref> - to: <target_ref> -
Search for merged MRs in the change range:
Use gitlab_merge_request with action "list": - project_id: <project_id> - state: "merged" - per_page: 100 -
Correlate commits with MRs to enrich the data.
-
Categorize changes based on MR labels, commit prefixes, and descriptions.
Approach B: Use the MCP Prompt
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.
- 1mo ago Changed feb698e2806e
- 1mo ago First seen · 170 lines · 67 tokens per session scan A b2f9d06ef854
generate-release-notes is a skill published in the GitHub repository jmrplens/gitlab-mcp-server (46 stars, last pushed today), licensed MIT. It adds 67 tokens to every session and 1,395 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-08-30.
Other skills, from other repositories
hmem-release
Pre-publish checklist for hmem: skills synced, version bumped, tests green, nothing forgotten. Use before npm publish or when the user says 'release', 'publish', 'push a release', or 'neue Version'.
breaking-changes
Detects breaking changes between two git refs and generates a migration guide.
release-notes
Generates release notes from commits since the last tag.
changelog
Updates CHANGELOG.md with commits since the last entry.
tag-release
Bumps version in package.json (or equivalent), creates a git tag, and pushes.
goal-release
Cut a release end to end: use the draft-release skill to open the release PR and draft GitHub release, wait for CI to turn green, run the merge-pr skill to merge the release PR, then update the Homebrew formula from the published release assets. Use when the user wants to draft and merge a release in one go, or…