New: 97,000+ skills indexed from GitHub repos with 100+ stars · every skill safety-checkedBrowse top skillsTop skills
Esc to closeBrowse all skills
Submit a skillBrowse skills
Submit a skillBrowse skills

Agent skill

Changelog PR Classifier

by warpdotdev in warpdotdev/warp

Rules for deciding whether a pull request without an explicit changelog marker belongs in the release changelog, and under which category.

AGPL-3.0Auto-check passedDevelopment

Install Changelog PR Classifier

skills CLI
$ npx skills add warpdotdev/warp --skill classify-changelog-pr -a claude-code

Project install by default; add -g for ~/.claude/skills/.

GitHub CLI
$ gh skill install warpdotdev/warp classify-changelog-pr --agent claude-code

Project scope by default; add --scope user for a personal install. Needs GitHub CLI 2.90.0 or later (public preview).

Manual copy
$ git clone --depth 1 https://github.com/warpdotdev/warp.git skills-src && mkdir -p .claude/skills && cp -r skills-src/.agents/skills/classify-changelog-pr .claude/skills/classify-changelog-pr && rm -rf skills-src

Use ~/.claude/skills/ instead of .claude/skills for a personal install. The folder must contain SKILL.md.

Claude Code skills documentation · loads skills from .claude/skills/

Facts

Skill name
classify-changelog-pr
GitHub stars
65k
Used in
1 other repo
Token cost
~1.1k tokens
SKILL.md length
561 words
Files
1
Skills in repo
46
Repo updated
First seen
Licence
AGPL-3.0

At a glance

Rules for deciding whether a pull request without an explicit changelog marker belongs in the release changelog, and under which category.

  • Works in 4 steps: Check which flag list it belongs to… → Apply the channel rules above. → If the flag is in RELEASE_FLAGS or… → …
  • Drafting release notes from a batch of unmarked pull requests
  • SKILL.md covers Categories, Decision rules and Writing changelog text
  • Instructions only: no scripts, shell commands, URLs or credentials in SKILL.md

What it does

These rules support the changelog-draft agent when a pull request carries no explicit `CHANGELOG-*` marker. Six categories are defined: NEW-FEATURE for substantial user-facing capabilities, IMPROVEMENT for noticeable enhancements, BUG-FIX for user-visible fixes, OZ for Oz and AI agent capability changes (at most 4 per release in the stable changelog), TUI for changes that affect the Warp Agent CLI, and NONE for explicit opt-outs handled upstream.

Decision rules exclude bot-authored pull requests, changes that only touch CI workflows, tests, dev tooling or internal docs, dependency bumps with no visible effect, and behavior-neutral refactors. Fixes for crashes, data loss or security issues are always included, even without a marker. TUI impact is judged separately from the regular category, using the commit subject, PR text and TUI-owned paths, and never from file paths alone. The excerpt is cut off partway through that section.

When your agent uses it

  • Drafting release notes from a batch of unmarked pull requests
  • Deciding whether a dependency bump or refactor belongs in the changelog
  • Classifying a change as a new feature, improvement or bug fix
  • Deciding whether a change also counts for the Warp Agent CLI surface

Example prompts

  • “Should the dependabot PR that bumps a lint plugin appear in this release's changelog?”
  • “This PR fixes a crash on startup. Which changelog category does it get?”
  • “This PR changes how the agent edits files. Does it also count as a TUI entry?”

Requirements

  • The changelog-draft skill, which applies these rules inline

Workflow steps

4 steps, taken from the first numbered list in SKILL.md.

  1. Check which flag list it belongs to (RELEASE_FLAGS, PREVIEW_FLAGS, DOGFOOD_FLAGS).
  2. Apply the channel rules above.
  3. If the flag is in RELEASE_FLAGS or enabled by default in app/Cargo.toml, treat it as live.
  4. Set feature_flag in the classification output to the flag name.

What it can do on your machine

Read from SKILL.md and the folder at commit f571865. It shows what the files ask for, not the result of running them.

  • Tool permissions

    Pre-approves nothing: there is no allowed-tools line, so your agent's usual permission prompts apply.

    From allowed-tools in the SKILL.md frontmatter.

  • Runs code

    No scripts in the folder and no shell commands in SKILL.md.

    From the folder's file list and the shell code blocks in SKILL.md.

  • Network

    No URLs in SKILL.md.

    From URLs in SKILL.md, links to its own repository left out.

  • Credentials

    Names no API keys, tokens, secrets or passwords.

    From names ending in _API_KEY, _TOKEN, _SECRET, _KEY or _PASSWORD in SKILL.md.

Context cost

Changelog PR Classifier loads about 1.1k tokens when it runs. Until then it costs about 54 tokens; SKILL.md has 561 words of instructions outside code blocks.

Always · name and description, kept in context so the agent knows when to use it
~54
When it runs · the whole SKILL.md, loaded when a task matches
~1.1k

Estimates: characters ÷ 4, the usual rule of thumb; real counts depend on the model's tokenizer. Scripts and assets cost tokens only if the agent reads them.

Safety

Auto-check passed

The automated check found no risky patterns in SKILL.md.

Automated static check — not a guarantee. Review scripts before installing. It scans the text of SKILL.md for risky patterns (piping downloads into a shell, reading credential files, hidden Unicode, destructive commands); files beside SKILL.md are not scanned.

SKILL.md

The full file from warpdotdev/warp at commit f571865, republished under its AGPL-3.0 licence (© warpdotdev). 561 words, ~1,078 tokens.

Download SKILL.mdSave it as .claude/skills/classify-changelog-pr/SKILL.md (or your agent's skills folder).
name
classify-changelog-pr
description
Reference guidance for classifying whether an unmarked PR should appear in the changelog and under which category. Used inline by the changelog-draft skill — not dispatched as a separate agent.

Classify Changelog PR

This document provides classification rules for PRs that lack explicit CHANGELOG-* markers. The changelog-draft agent follows these rules inline when deciding whether to include an unmarked PR.

Categories

  • NEW-FEATURE — A substantial new user-facing capability. Reserve for features that would warrant docs, marketing, or social media attention.
  • IMPROVEMENT — Enhances an existing feature in a way users would notice (performance, UX, new options).
  • BUG-FIX — Fixes a user-visible bug or regression.
  • OZ — Changes to Oz / AI agent capabilities. At most 4 per release in the stable changelog.
  • TUI — User-visible changes that impact the Warp Agent CLI/headless TUI, including shared Agent capabilities.
  • NONE — Explicitly opt out of changelog inclusion. Handled upstream by fetch_prs.py marker extraction.

Decision rules

Always exclude
  • PRs with an explicit CHANGELOG-NONE marker (contributor opted out)
  • PRs authored by known bots (dependabot, renovate, github-actions, codecov)
  • PRs that exclusively modify CI workflows (.github/workflows/), test files, or dev tooling
  • PRs that only update internal docs, comments, or README files
  • Dependency bumps with no user-facing behavior change
  • Refactors with no observable behavior change (code moves, renames, formatting)
Always include
  • PRs with explicit CHANGELOG-* markers (handled before this guidance applies)
  • PRs that fix a crash, data loss, or security issue — even without a marker
TUI surface classification
  • Treat explicit CHANGELOG-TUI and CHANGELOG-OZ markers as authoritative entries. They are independent and may coexist with each other or with regular changelog categories.
  • Determine TUI impact independently from the regular New Feature, Improvement, or Bug Fix category. A shared Agent capability may belong in both its regular category and TUI.
  • Classify a user-visible entry as impacting TUI when commit_subject contains TUI as a standalone token.
  • For stable releases, also use the PR title/body and TUI-owned paths such as crates/warp_tui or crates/warpui_core/src/elements/tui. Shared capabilities such as Agent tool-call or edit-file behavior also impact TUI when Warp Agent CLI users observe the change. If metadata is ambiguous, inspect the commit diff.
  • Do not infer TUI impact from file paths alone; confirm that Warp Agent CLI users observe the changed behavior.
  • A TUI-only entry belongs only in the TUI category. An entry that impacts both TUI and another surface should appear in both TUI and its regular category.
Show full SKILL.md (202 more words)Show less
Conditional on channel
  • Stable channel: Only include changes that are live for all users. Exclude PRs gated behind DOGFOOD_FLAGS or PREVIEW_FLAGS.
  • Preview channel: Include PRs gated behind PREVIEW_FLAGS. Still exclude DOGFOOD_FLAGS-only changes.
  • Dev channel: Include everything that's user-visible, regardless of flag gates.
Feature-flagged PRs

If a PR mentions a FeatureFlag variant in its diff or title:

  1. Check which flag list it belongs to (RELEASE_FLAGS, PREVIEW_FLAGS, DOGFOOD_FLAGS).
  2. Apply the channel rules above.
  3. If the flag is in RELEASE_FLAGS or enabled by default in app/Cargo.toml, treat it as live.
  4. Set feature_flag in the classification output to the flag name.
Confidence levels
  • high — Clear user-visible change with obvious category.
  • medium — Likely user-visible but category or scope is somewhat ambiguous.
  • low — Unclear whether users would notice; or the PR touches both internal and user-facing code. Set needs_review: true.

Writing changelog text

  • Write from the user's perspective: "Added X", "Fixed Y", "Improved Z".
  • Keep it to one sentence, ≤ 120 characters.
  • Don't reference internal implementation details, file paths, or function names.
  • Don't start with "PR" or the PR number — those are added as metadata.
  • Use active voice and present tense for new features ("Adds dark mode"), past tense for fixes ("Fixed crash on startup").

© warpdotdev, AGPL-3.0. Rendered from Markdown: HTML in the file is shown as text, images as links, and headings moved down two levels. Raw file

Files

Just SKILL.md in .agents/skills/classify-changelog-pr of warpdotdev/warp.

Open the folder on GitHubat commit f571865

Used in 1 other repository

We found 1 copy of this SKILL.md (exact, near-identical or edited) in other folders, from 1 other GitHub owner. This page covers the copy in warpdotdev/warp, which our catalogue first saw on October 7, 2026.

Compare with similar skills

Changelog PR Classifier next to the 5 skills that share the most tags, products or categories with it. Stars are the repository's; “used in” counts other GitHub owners with a copy.

Changelog PR Classifier compared with similar skills
SkillStarsUsed inTokensAuto-checkLicenceRepo updated
Changelog PR Classifier this skillwarpdotdev/warp65k1 repos~1.1kAutomated safety check: PassAGPL-3.0
StarRocks Release NotesStarRocks/starrocks12k—~1.9kAutomated safety check: NotesApache-2.0
Git Workflow and Versioningaddyosmani/agent-skills102k2 repos~3.5kAutomated safety check: NotesMIT
Verdaccio Pull Request Workflowverdaccio/verdaccio18k—~1.9kAutomated safety check: PassMIT
pybind11 Release Preparationpybind/pybind1118k—~1.7kAutomated safety check: PassCustom licence
AionUi Version BumpiOfficeAI/AionUi33k—~2.1kAutomated safety check: PassApache-2.0

Similar skills

  • StarRocks Release Notes

    StarRocks/starrocks

    Drafts English release notes for a StarRocks patch release from the PRs merged into its release branch, then opens a documentation PR and hands translation to /translate.

    12k GitHub stars~1.9k tokensUpdated today
    DevelopmentAuto-check: notes

  • Git Workflow and Versioning

    addyosmani/agent-skills

    Sets git habits for every change: short-lived branches, atomic commits with descriptive messages, clean pull requests, plus versioning, tagging and changelogs for releases.

    102k GitHub starsUsed in 2 repos~3.5k tokens
    DevelopmentAuto-check: notes

  • Verdaccio Pull Request Workflow

    verdaccio/verdaccio

    Takes a change through a verdaccio pull request: branch, local checks, changeset, title and body, labels, CI and review rounds, and ports to other release lines.

    18k GitHub stars~1.9k tokensUpdated today
    DevelopmentAuto-check passed

  • pybind11 Release Preparation

    pybind/pybind11

    Opens the pybind11 release-preparation pull request: picking the release base, bumping the version in common.h and integrating the changelog, following docs/release.rst.

    18k GitHub stars~1.7k tokensUpdated today
    DevelopmentAuto-check passed

  • AionUi Version Bump

    iOfficeAI/AionUi

    Automates an AionUi release: checks the latest AionCore release and its artifacts, updates package.json, writes the changelog, opens a PR and tags the release.

    33k GitHub stars~2.1k tokensUpdated 28 days ago
    DevelopmentAuto-check passed

  • Commit And PR Messages

    superplanehq/superplane

    Write Git commit messages and pull request titles/descriptions using the Chris Beams / Tim Pope conventions (subject/body split, ~50-char subject, imperative mood, why-not-how body) plus ASD-STE100…

    7.7k GitHub stars~1.6k tokensUpdated today
    DevelopmentAuto-check passed

More from warpdotdev/warp

All 46 skills in this repo

  • Figma Design System Builder

    warpdotdev/warp

    Builds or updates a design system in Figma from a codebase in ordered phases: discovery, variables and tokens, components, theming and documentation, with checkpoints.

    65k GitHub starsUsed in 2 repos~4.4k tokens
    Auto-check passed

  • Figma use_figma Plugin API Rules

    warpdotdev/warp

    Required groundwork before any use_figma call: the rules and reference files for running JavaScript in a Figma file through the Plugin API without common failures.

    65k GitHub starsUsed in 4 repos~4.4k tokens
    Auto-check passed

  • Warp Factory Files

    warpdotdev/warp

    Authors and edits file-based Warp software factory definitions rooted at factory.yaml, covering agents, automations, scorers and webhooks, and validates them before a pull request.

    65k GitHub starsUsed in 1 repo~2.5k tokens
    Auto-check passed

  • Figma Design to Code

    warpdotdev/warp

    Turns a Figma frame or component into production code that matches the design, using the Figma MCP server and the project's own design system.

    65k GitHub starsUsed in 4 repos~2.9k tokens
    Auto-check passed

  • Warp GUI to Agent CLI Migration

    warpdotdev/warp

    Migrates the compatible subset of settings and global file-based MCP servers from the Warp desktop app into Warp Agent CLI without exposing credentials or state.

    65k GitHub starsUsed in 1 repo~2.1k tokens
    Auto-check passed

  • Figma Design System Rules Generator

    warpdotdev/warp

    Creates project-specific design system rules from your codebase so coding agents implement Figma designs with your components, naming and tokens.

    65k GitHub starsUsed in 3 repos~4.6k tokens
    Auto-check passed

Categories

Questions about Changelog PR Classifier

What does Changelog PR Classifier do?

Rules for deciding whether a pull request without an explicit changelog marker belongs in the release changelog, and under which category. These rules support the changelog-draft agent when a pull request carries no explicit `CHANGELOG-*` marker. Six categories are defined: NEW-FEATURE for substantial user-facing capabilities, IMPROVEMENT for noticeable enhancements, BUG-FIX for user-visible fixes, OZ for Oz and AI agent capability changes (at most 4 per release in the stable changelog), TUI for changes that affect the Warp Agent CLI, and NONE for explicit opt-outs handled upstream.

When should I use Changelog PR Classifier?

Changelog PR Classifier fits situations like: drafting release notes from a batch of unmarked pull requests; deciding whether a dependency bump or refactor belongs in the changelog; classifying a change as a new feature, improvement or bug fix; deciding whether a change also counts for the Warp Agent CLI surface.

How do I install Changelog PR Classifier in Claude Code?

Run `npx skills add warpdotdev/warp --skill classify-changelog-pr -a claude-code`. Or copy the skill folder (.agents/skills/classify-changelog-pr in warpdotdev/warp) into .claude/skills/classify-changelog-pr in your project. Claude Code loads it when a task matches its description.

How do I install Changelog PR Classifier in Codex?

Run `npx skills add warpdotdev/warp --skill classify-changelog-pr -a codex`. Or copy the skill folder (.agents/skills/classify-changelog-pr in warpdotdev/warp) into .agents/skills/classify-changelog-pr in your project. Codex loads it when a task matches its description.

Can I use Changelog PR Classifier in Cursor, Gemini CLI or GitHub Copilot?

Cursor, Gemini CLI, GitHub Copilot and OpenCode also load SKILL.md folders. With the skills CLI, run `npx skills add warpdotdev/warp --skill classify-changelog-pr -a cursor` (or -a gemini-cli, github-copilot or opencode for the others). To copy it by hand, put the folder in .cursor/skills/classify-changelog-pr, .gemini/skills/classify-changelog-pr, .github/skills/classify-changelog-pr and .opencode/skills/classify-changelog-pr in your project.

What does Changelog PR Classifier need to run?

SKILL.md names no scripts, command-line tools or credentials: Changelog PR Classifier is instructions for the agent only. Our summary lists: The changelog-draft skill, which applies these rules inline.

Does Changelog PR Classifier access the network?

SKILL.md contains no URLs. Any network use would come from the scripts or tools the agent runs. This is read from the text; nothing was executed.

Is Changelog PR Classifier safe to install?

Our automated static check of SKILL.md found no risky patterns, such as piping downloads into a shell, reading credential files or hidden Unicode. It is not a guarantee. Review the folder before installing.

What licence does Changelog PR Classifier use?

Changelog PR Classifier is published under the AGPL-3.0 licence (the repository's licence). It allows redistribution, so the full SKILL.md is shown on this page.

How many tokens does Changelog PR Classifier use?

About 1.1k tokens (SKILL.md is roughly 4.3k characters). Agents keep only the skill's name and description in context until a task matches; then they load SKILL.md in full.

What are the alternatives to Changelog PR Classifier?

Skills that share tags, products or a category with Changelog PR Classifier: StarRocks Release Notes (StarRocks/starrocks, 12k stars), Git Workflow and Versioning (addyosmani/agent-skills, 102k stars), Verdaccio Pull Request Workflow (verdaccio/verdaccio, 18k stars) and pybind11 Release Preparation (pybind/pybind11, 18k stars). The comparison table on this page puts their stars, adoption, token cost, safety result and licence side by side.

Who maintains Changelog PR Classifier?

warpdotdev (a GitHub organization) maintains it in warpdotdev/warp, which has 65,380 GitHub stars. The repository holds 46 skills in this directory. The repository was last updated on October 7, 2026.

Source: warpdotdev/warp on GitHub. Facts on this page come from the repository at the commit we read; the author's words are quoted as theirs.