create

Analyze commits, PRs, and tags to propose versions and generate release notes.

2|1|Updated Feb 15, 2026
One-click install
npx skills add https://github.com/ondrasek/cc-plugins --skill create-ondrasek
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: create
Source: https://github.com/ondrasek/cc-plugins/tree/main/plugins/github-releases/skills/create
Command: npx skills add https://github.com/ondrasek/cc-plugins --skill create-ondrasek

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes references (resource) components.

What problem does it solve?

Release management can be error-prone and time-consuming. This skill automates version determination and release notes generation to ensure consistent, properly drafted GitHub releases.

Core Features & Use Cases

  • Version determination: analyzes commits, PRs, and tags to propose the correct semantic version bump.
  • Release notes generation: builds notes from templates and merged PRs or commits.
  • Preview and approval: shows the full release draft (tag, title, notes, draft status) and waits for user confirmation before creation.
  • Draft-by-default releases: creates as draft unless explicitly asked to publish.
  • Scope awareness for monorepos: supports per-package release workflows when project structure requires it.

Quick Start

Ask Claude to create a release for the current repository, specify the target branch and optional version, and confirm publishing.

Frequently Asked Questions about create

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

FAQPage Schema
How do I automate GitHub release notes generation from conventional commits?

You can automate GitHub release notes generation by analyzing commit history to determine semantic version bumps and assembling comprehensive release drafts. This skill proposes versions and builds notes from merged PRs before creation.

How does semantic versioning work when determining release bumps from tags and PRs?

Semantic versioning for release bumps works by analyzing existing repository tags, commit history, and merged PRs to propose the correct version increment. The skill applies conventional commit rules to determine the required version bump.

Can I create GitHub releases as drafts by default to review before publishing?

Yes, you can create GitHub releases as drafts by default to review before publishing. The skill presents a full release preview including tag, title, and notes, waiting for explicit user confirmation before creating the release.

Does this release management approach support monorepos with per-package versioning?

Yes, this release management approach supports monorepos with per-package versioning. The skill provides scope awareness to handle per-package release workflows when your project structure requires independent package versions and releases.

What is the best way to manage GitHub release versioning without manual changelog errors?

The best way to manage GitHub release versioning without manual changelog errors is to automate version determination and release notes generation. This ensures consistent, properly drafted GitHub releases by analyzing commits and applying tag conventions.