status

Predict next semantic version and generate release notes from Git commit history.

2|1|Updated Feb 15, 2026

Search Tags:#release #semantic-versioning #release-notes #conventional-commits #version-bump #git-analysis

Ready to run

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

💬 Prompt for ChatGPT / Claude Chat▼

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

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Preview the upcoming release by analyzing the Git history to predict the next version bump and compile release notes, enabling proactive planning and communication.

Core Features & Use Cases

Preview upcoming version bumps and categorize commits into breaking changes, features, fixes, and other.
Generate concise release previews for stakeholders, sprint planning, and QA readiness.
Integrate with release planning workflows to validate readiness before tagging.

Quick Start

Run the status check to display the latest tag and the predicted next version.

Frequently Asked Questions about status

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

FAQPage Schema

How do I predict the next semantic version from git history?▼

To predict the next semantic version from git history, the tool parses commits since the latest tag, evaluates breaking changes and features, and computes the required version bump automatically.

How to generate release notes from conventional commits?▼

Generating release notes from conventional commits involves grouping parsed commit messages by type, such as features and fixes, to output a concise categorized summary for stakeholders.

Does this release preview tool work with non-conventional commits?▼

Yes, the release preview tool works with non-conventional commits by grouping them separately under an 'Other' category, ensuring they are still included in the pre-release review summary.

What is the best way to prepare sprint planning using git analysis?▼

The best way to prepare sprint planning using git analysis is to preview upcoming version bumps and categorize commits to validate release readiness and communicate stakeholder updates.

When do I need a pre-release version bump preview?▼

You need a pre-release version bump preview when validating project readiness before tagging, enabling proactive planning and clear stakeholder communications during release workflows.