superplane-changelog

Generate user-focused changelogs from merged commits in SuperPlane repositories.

5.0k|530|Updated May 7, 2025
One-click install
npx skills add https://github.com/superplanehq/superplane --skill superplane-changelog
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: superplane-changelog
Source: https://github.com/superplanehq/superplane/tree/main/.cursor/skills/superplane-changelog
Command: npx skills add https://github.com/superplanehq/superplane --skill superplane-changelog

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill requires git, and includes scripts (resource) components.

What problem does it solve?

This Skill automates the creation of user-focused changelogs from merged commits in SuperPlane, making it easy to communicate new features, improvements, and bug fixes to users.

Core Features & Use Cases

  • Changelog Generation: Automatically generate changelogs from merged commits in SuperPlane repositories.
  • Customizable Time Range: Specify the time range for the changelog, including date ranges and version tags.
  • User-Friendly Output: Outputs a markdown file with a consistent structure and tone, suitable for user-facing communication.

Quick Start

Generate a changelog for the past week using the superplane-changelog skill.

Frequently Asked Questions about superplane-changelog

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

FAQPage Schema
How do I generate a changelog from merged git commits?

To generate a changelog from merged git commits, you can use this Skill to analyze commit history within a specified time range and output a structured markdown file. It requires Git to retrieve the commit data.

Can I specify a date range for changelog generation?

Yes, you can specify a time range for changelog generation by providing custom date ranges or version tags. The Skill processes merged commits within these defined boundaries to structure the output.

What is the output format for automated commit analysis?

The output format for automated commit analysis is a user-friendly markdown file. It structures the extracted merged commits into a consistent tone suitable for user-facing communication.

Do I need Git installed to analyze commit history for version control?

Yes, you need Git installed to analyze commit history for version control. The Skill depends on Git directly to retrieve and manipulate the merged commit data required for changelog creation.

What's the best way to automate user-facing release notes from SuperPlane commits?

The best way to automate user-facing release notes from SuperPlane commits is to use this Skill to parse merged commit messages and format them into a structured markdown changelog.