SkillVaultskills Browse all 1,000+ skills

Writing · Version 1.0.0 · Reviewed 2026-08-02

Repository Changelog Generator

Make the reader act on release-range selection and change deduplication with evidence, explicit trade-offs, and a verification plan.

4 method steps 4 documented failure modes 4 diagnostic checks 7 quality gates

Generates a versioned changelog from commit history and pull requests, deduplicating squash merges, categorizing user impact, and preserving links to authoritative changes.

₹199 one-time

Get this skill archive

Install in your AI coding tool

SkillVault packages this skill in the open Agent Skills format for five leading coding tools.

What this skill helps you do

  • Release-range selection
  • Change deduplication
  • Audience-focused changelog

How Repository Changelog Generator works

You provide

Source material, audience, and the decision it supports

It inspects

Facts, gaps, and unstated assumptions for release-range selection

It decides

A change deduplication draft organized around the next action

You verify

Every claim traced back to the supplied source

What it checks first

Repository Changelog Generator generates a versioned changelog from commit history and pull requests, deduplicating squash merges, categorizing user impact, and preserving links to authoritative changes. Use it when the work involves Release-range selection, Change deduplication, Audience-focused changelog.

  1. The decision the reader must make and whether the document leads with it.
  2. Which claims are measured, which are derived, and which are assumed.
  3. Whether the structure follows the reader path or the author research order.
  4. Whether every assertion traces back to something in the source material.

Failure modes it recognizes

  • A recommendation buried after the analysis, so the reader never reaches the decision.
  • Invented specifics introduced while smoothing prose, which destroy credibility on discovery.
  • Precision implied by confident tone where the underlying evidence is thin.
  • Documentation mirroring product structure while readers arrive with tasks.

Answers it will reject

  • Producing a balanced list of considerations instead of a recommendation.
  • Restating the question with more words as though it were analysis.
  • Writing for the approver rather than for the person who must act.

Decision rules it applies

  • Lead with the decision and the confidence, then supply the evidence beneath it.
  • Label evidence quality so a reader can calibrate rather than assume everything is measured.
  • Cut anything that does not change the reader decision or action.

Evidence it asks for

  • Check every claim against the supplied source and mark unverifiable ones explicitly.
  • Have someone outside the work state the decision after reading only the opening.
  • Verify the document answers the question that was actually asked.

The method inside

  1. Identify the reader decision before drafting
  2. Lead with the conclusion and strongest evidence
  3. Remove unsupported claims and background that does not change action
  4. Check traceability, ambiguity, and the explicit ask

Deliverables

  • Release-range selection revised draft
  • Change deduplication source and logic check
  • Audience-focused changelog approval-ready version

Evidence requirements

  • Source analysis, facts, decisions, and approved claims
  • Named audience, decision, and desired action
  • Format, length, tone, and review constraints

Quality gates

  • Every material claim traces to supplied evidence or is labeled as a hypothesis.
  • The response follows the declared deliverable contract.
  • No execution, access, measurement, or verification is invented.
  • Secrets and personal data are redacted rather than repeated.
  • The user receives a concrete independent verification step.
  • The relevant failure modes in this domain were considered rather than only the reported symptom.
  • No listed anti-pattern was recommended as a solution.

Example task

Input

Generate the changelog since the previous release tag and group changes for users, operators, and maintainers without listing every internal commit.

Expected output

Verify the previous and target tags, collapse commits already represented by one pull request, and classify by observable impact rather than label alone. Breaking changes, migrations, deprecations, and security fixes receive explicit action text and links; internal refactors stay concise...

Boundaries and compatibility

Ideal for

  • Release-range selection: produce a decision or artifact grounded in supplied evidence.
  • Change deduplication: produce a decision or artifact grounded in supplied evidence.
  • Audience-focused changelog: produce a decision or artifact grounded in supplied evidence.

Out of scope

  • Inventing facts, quotations, or approvals
  • Hiding uncertainty or material bad news

Agent compatibility

  • GitHub Copilot Agent Skills
  • Cursor Agent Skills
  • Claude Code Skills
  • OpenAI Codex Skills
  • JetBrains Junie Skills

Tool policy: Advisory by default. No tools are assumed. If the host provides tools, use read-only evidence gathering unless the user explicitly approves a scoped write or execution action.