create-changelog

Generate and populate changelog entries within Figma using template components.

236|32|Updated Jan 23, 2026

Search Tags:#automation #changelog #documentation #design system #figma #component updates

Ready to run

npx skills add https://github.com/redongreen/uSpec --skill create-changelog-redongreen

💬 Prompt for ChatGPT / Claude Chat▼

Please help me install this Agent Skill.
Skill: create-changelog
Source: https://github.com/redongreen/uSpec/tree/main/.cursor/skills/create-changelog
Command: npx skills add https://github.com/redongreen/uSpec --skill create-changelog-redongreen

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes references (resource) components.

What problem does it solve?

This Skill automates the creation and population of changelog entries directly within Figma, eliminating the need for manual documentation and ensuring consistency in tracking component updates.

Core Features & Use Cases

Automated Changelog Generation: Creates a new changelog entry based on provided change descriptions.
Template Integration: Utilizes a predefined Figma component template for changelogs.
Structured Data Entry: Populates entries with dates, authors, and detailed change items, applying bullet formatting for clarity.
Use Case: After updating a design token or component variant, use this Skill to quickly add a new entry to the project's changelog, detailing the change and who made it.

Quick Start

Use the create changelog skill to add a new entry for a color token update.

Frequently Asked Questions about create-changelog

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

FAQPage Schema

How do I automate changelog generation for Figma design system components?▼

Automating changelog generation in Figma requires a Skill that populates entries with dates, authors, and bulleted change descriptions directly within your design files. It uses a predefined Figma component template to ensure consistent documentation of component updates.

What is the best way to track design token updates in Figma?▼

Tracking design token updates in Figma is best handled by generating structured changelog entries. This approach automatically adds new date entries and detailed change items with titles, preventing manual documentation errors and ensuring consistent version tracking.

How do I add a new changelog entry in Figma after updating a component variant?▼

To add a new changelog entry in Figma after updating a component variant, you provide the change descriptions to the automation Skill. It then populates a predefined template component with the date, author, and bulleted details of the modification.

Do I need Figma Desktop Bridge MCP to generate component changelogs?▼

Yes, generating component changelogs directly within Figma requires the Figma Desktop Bridge MCP. This connection allows the automation to populate the specific Figma template component with structured changelog data.

Can I use a custom Figma template for automated changelog documentation?▼

Automated changelog documentation integrates with a predefined Figma component template using specific template keys. You must provide these template keys for the Skill to correctly populate the changelog entries with dates and bulleted descriptions.

Why use automated changelog generation for design system files in Figma?▼

Automated changelog generation for design system files eliminates manual documentation and ensures consistency. By automatically creating structured entries with authors and change items, it maintains clear tracking of component updates without manual formatting effort.