skills.rest
cobusgreyling
cobusgreylingCOMMUNITY
Explore all skills by this author →
Website𝕏@CobusGreylingZAGitHub

changelog-scan

Extract PR and commit information into a structured release notes draft.

10.0k|1.4k|Updated Jun 9, 2026
Search Tags:#changelog#version control#release notes#PR analysis#commit scanning
One-click install
npx skills add https://github.com/cobusgreyling/loop-engineering --skill changelog-scan-cobusgreyling
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: changelog-scan
Source: https://github.com/cobusgreyling/loop-engineering/tree/main/starters/changelog-drafter-opencode/skills/changelog-scan
Command: npx skills add https://github.com/cobusgreyling/loop-engineering --skill changelog-scan-cobusgreyling

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes scripts (resource) components.

What problem does it solve?

This Skill streamlines the creation of release notes by scanning merged pull requests and commits, extracting relevant information, and organizing it into a structured format.

Core Features & Use Cases

  • PR and Commit Analysis: Automatically scan for titles, labels, types, and signals from merged pull requests and commits.
  • Release Notes Drafting: Produce a categorized draft in RELEASE_NOTES_DRAFT.md for release notes.
  • State Tracking: Update changelog-drafter-state.md with the scan window for version control.
  • Use Case: Enhance your release process by automating the collection of information that typically requires manual review.

Quick Start

Run the 'changelog-scan' skill to scan for changes and generate a release notes draft.

Frequently Asked Questions about changelog-scan

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I automate release notes drafting from merged pull requests and commits?▼

You can automate release notes drafting by running a scan over merged pull requests and commits to extract titles, labels, and signals. This collected data is then organized into a categorized markdown draft for release documentation.

What is the best way to extract PR and commit information for version control documentation?▼

Extracting PR and commit information is best handled by scanning merge history with automated scripts. This captures relevant data like commit types and labels, structuring the output into a categorized format for release notes without manual review.

Do I need Git to scan commits and generate a changelog draft?▼

Yes, Git and relevant PR tracking tools are required to analyze merge history and scan commits for changelog drafting. These tools provide the necessary merge data and version control integration required to extract information accurately.

Does changelog scanning track the scan window for each release?▼

Changelog scanning tracks the scan window for each release by updating a state file. This records the analyzed timeframe for version control, ensuring subsequent scans only capture new changes since the last documented release.

What file format is used for the generated release notes draft?▼

The generated release notes draft is outputted as a markdown file named `RELEASE_NOTES_DRAFT.md`. This categorized format organizes extracted PR and commit data, making it ready for review and inclusion in final version control documentation.

Related Skills

Explore More Software Engineering Skills→
tamzitamzi

release-changelog

Generates stable Paperclip changelogs from Git commit history, GitHub pull requests, and Calab for versioning/release tracking.

Community
Advanced
frostantfrostant
42

changelog-generator

Converts git commit history into categorized, ready-to-publish markdown release notes.

Community
Intermediate
AnveioAnveio
1

task-pull-request

Automate GitHub pull request creation, reviews, feedback, and merges via gh CLI.

Community
Intermediate
mvillmowmvillmow
18

generate-changelog

Generate a Markdown changelog from git commits grouped by conventional commit types.

Community
Basic