skills.rest
kpab
kpabCOMMUNITY
Explore all skills by this author →
GitHub

safe-formatter

Generate Markdown release notes from categorized pull request titles.

Updated Jul 5, 2026
Search Tags:#version control#release notes#Markdown#code documentation#PR formatting
One-click install
npx skills add https://github.com/kpab/skilldrift-vendor-lab --skill safe-formatter
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: safe-formatter
Source: https://github.com/kpab/skilldrift-vendor-lab/tree/main/skills/safe-formatter
Command: npx skills add https://github.com/kpab/skilldrift-vendor-lab --skill safe-formatter

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This Skill automates the process of formatting a list of merged pull requests into tidy Markdown release notes, making it easier to document changes and track contributions.

Core Features & Use Cases

  • Markdown Release Notes: Automatically generates Markdown-formatted release notes from PR titles.
  • Categorization: Groups PR titles by prefix (e.g., 'feat:', 'fix:', 'chore:').
  • Quick Start: Ideal for teams managing multiple contributions in a project's repository.

Quick Start

Use the safe-formatter skill to format the release notes for the merged PRs in the current branch.

Frequently Asked Questions about safe-formatter

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

FAQPage Schema
How do I format pull requests into Markdown release notes?▼

To format pull requests into Markdown release notes, you provide a list of merged PR titles. The tool parses and processes these titles to automatically categorize and generate structured Markdown documentation for your project changes.

How does PR title categorization work for code documentation?▼

PR title categorization works by parsing and processing standard prefixes like 'feat:', 'fix:', and 'chore:'. It groups the pull requests by these prefixes to generate organized Markdown release notes with distinct sections for features, fixes, and chores.

What is the best way to document project contributions from merged PRs?▼

The best way to document project contributions is automating the creation of Markdown release notes from a list of merged PR titles. This categorizes pull requests by type, making it easier to track changes and document contributions in your repository.

Can I group PR titles by prefix to separate features and fixes?▼

Yes, you can group PR titles by prefix to separate features and fixes. The tool specifically categorizes pull requests by recognizing title prefixes like 'feat:', 'fix:', and 'chore:' to generate structured Markdown release notes.

Do I need a specific version control setup to generate Markdown release notes?▼

No specific version control setup is required beyond having a list of merged pull request titles. The tool processes the provided PR titles and prefixes directly to categorize them and output Markdown release notes.

Why are my pull request prefixes not categorizing correctly in the release notes?▼

Pull request prefixes may not categorize correctly if the titles lack recognizable prefixes like 'feat:', 'fix:', or 'chore:'. The tool requires parsing standard PR title prefixes to successfully group and format them into Markdown release notes.

Related Skills

Explore More Software Engineering Skills→
wojonswojons
4

git-release

Generate release notes and version bumps from merged Git pull requests.

Community
Intermediate
ChoshimWyChoshimWy
8

app-store-changelog

Extract user-visible release notes from git history since the latest tag.

Community
Intermediate
robhowleyrobhowley
5

open-pr

Generate pull request titles and descriptions from conventional commit messages.

Community
Intermediate
meirmmeirm
13

writing-release-notes

Generate categorized markdown release notes from git history and version files.

Community
Advanced