configure

Generates GitHub release note categories and validates them via previewed PIPES.

2|1|Updated Feb 15, 2026

Search Tags:#automation #github #configuration #release #labels #release-notes

Ready to run

npx skills add https://github.com/ondrasek/cc-plugins --skill configure-ondrasek

💬 Prompt for ChatGPT / Claude Chat▼

Please help me install this Agent Skill.
Skill: configure
Source: https://github.com/ondrasek/cc-plugins/tree/main/plugins/github-releases/skills/configure
Command: npx skills add https://github.com/ondrasek/cc-plugins --skill configure-ondrasek

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes references (resource) components.

What problem does it solve?

The capability automates the setup of GitHub release notes configuration by generating a standard .github/release.yml, enabling consistent categorization of changes across a project.

Core Features & Use Cases

Analyze repo labels and recent PR history to map changes to release note categories.
Preview the generated configuration before writing and support safe upgrades when a release.yml already exists.
Validate by generating preview notes after applying the new config and provide guidance for any adjustments.

Quick Start

Use the configure flow to generate and apply the .github/release.yml file for automatic release notes.

Frequently Asked Questions about configure

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

FAQPage Schema

How do I generate a GitHub release notes configuration file for my repository?▼

To generate a GitHub release notes configuration, this Skill analyzes your repository's labels and PR history to automatically create a .github/release.yml file that categorizes changes for structured release notes.

How does GitHub categorize pull requests in automatically generated release notes?▼

GitHub categorizes pull requests in generated release notes by mapping existing repository labels to specific change categories defined within a .github/release.yml configuration file.

Can I preview the release notes configuration before writing the .github/release.yml file?▼

Yes, you can preview the generated release notes configuration before applying it, and the Skill also validates the setup by generating preview notes to ensure the categorization works correctly before finalizing.

Do I need the gh CLI and git installed to automate my release notes workflow?▼

Yes, you need both the gh and git tooling installed, along with repository access, so the Skill can inspect your existing labels, pull request history, and any current release.yml file to adapt categories accurately.

What happens if a .github/release.yml file already exists in my repository?▼

If a .github/release.yml file already exists, the Skill provides overwrite safety by supporting safe upgrades, allowing you to preview and validate changes before the existing configuration is replaced.

Why are my GitHub release notes not categorizing changes properly?▼

Improper categorization in GitHub release notes often occurs when the .github/release.yml configuration does not correctly map repository labels to change categories, an issue this Skill resolves by analyzing PR history and adapting labels.