Figma Generate Changelog logo

Figma Generate Changelog

Organization
southleft
figma-generate-changelog

Generate a human-readable markdown changelog between two Figma file versions — pages added/removed/renamed plus per-component changes, enriched with author handles and timestamps, ready to paste into release notes, PRs, or Storybook MDX. Use when the user wants prose history — triggers: 'generate a Figma changelog', 'write release notes from Figma', 'what changed between these versions in markdown', 'summarize Figma changes for the PR', 'changelog between version A and B', 'design changelog since last release'. Uses the Figma REST API + a personal access token because version history is NOT reachable via the Plugin API / use_figma / the native Figma MCP. For raw structured diff JSON use figma-version-history; to find which version introduced a specific change use figma-blame-node.

Overview

Publishersouthleft
Repositoryfigma-console-mcp-skills
Skill namefigma-generate-changelog
Stars
94
Forks
4
Bundled files
1
LicenseMIT
Links
  • Markdown instructions

    A SKILL.md file the model loads on demand, so it only costs tokens when a request actually matches.

  • Works with any LLM

    AI skills are plain Markdown, not provider-specific code, so this works with GPT, Claude, Gemini, Grok, or a local model.

  • 1 bundled files

    Scripts, templates, and references the model can read while it works. Files are read-only and never executed.

  • Open source

    Published by southleft on GitHub. Read the source before you install it.

Installation

Install the Figma Generate Changelog AI skill in TypingMind to use it with any LLM, or drop it into another agent that reads SKILL.md.

1

Install in TypingMind

TypingMind installs a skill straight from its GitHub folder — it reads SKILL.md, bundles the resource files, and stores the result locally.

  1. Open the app and go to Plugins → Skills.
  2. Choose "Install from GitHub".
  3. Paste the skill folder URL below and confirm.
    https://github.com/southleft/figma-console-mcp-skills/tree/main/skills/figma-generate-changelog
  4. Enable the skill in any chat where you want it available.
Plugins → Skills → Add skill → From GitHub URL, then paste the folder URL and press Continue.
2

Install in another agent

Any agent that reads the Agent Skills format can use this skill — copy the folder into that agent's skills directory.

Claude Code — .claude/skills
git clone --depth 1 https://github.com/southleft/figma-console-mcp-skills.git /tmp/figma-console-mcp-skills
mkdir -p .claude/skills
cp -r /tmp/figma-console-mcp-skills/skills/figma-generate-changelog .claude/skills/figma-generate-changelog
Restart Claude Code after copying so it picks up the new skill.

Use it in TypingMind

Enable Figma Generate Changelog in any TypingMind chat and the model takes it from there. Its name and description sit in the system prompt, and the moment a request matches, the model loads the full instructions itself — you never invoke it by hand, and it costs no tokens until it is actually used.

The model loads Figma Generate Changelog on its own as soon as a request matches it.

Works with any AI model

AI skills are plain Markdown instructions rather than provider-specific code, so Figma Generate Changelog is not tied to the model it was written for. Install it once in TypingMind and use it with GPT-5, Claude, Gemini, Grok, DeepSeek, Mistral, Llama, or a local model you run yourself — all on your own API keys.

  • Loaded only when it is needed

    The system prompt carries just the name and description. The instructions are fetched on the first matching request, so an idle skill costs nothing.

  • Switch models mid-chat

    Because the skill is instructions rather than code, changing model does not break it — the next model reads the same SKILL.md.

Skill instructions

This is the SKILL.md content the model loads. Read it before installing — a skill is instructions your model will follow.

figma-generate-changelog — markdown changelog between two versions

Builds on the same version diff as figma-version-history, then formats it as release-notes-style markdown and enriches each version reference with the author handle, label, and timestamp.

Setup — terminal + token required. This skill runs shell commands, so it works in Claude Code (including the "Code" tab inside Claude Desktop), Cursor, Codex, or Gemini CLI — it does not run in plain Claude Desktop or claude.ai chat (no shell). The Figma connector's OAuth login does not authorize these REST calls, so you must supply your own Figma personal access token: in Figma go to Settings → Security → Personal access tokens, generate one with scope File content: read (plus File versions: read), then set it in your shell: export FIGMA_TOKEN="figd_…". The script reads it from the environment at runtime — never put the token in a skill file.

Setup & skill boundaries

  • All requests use X-Figma-Token: $FIGMA_TOKEN against https://api.figma.com.
  • Related: figma-version-history for the structured diff and the endpoint reference.

Derive the file key

bash
FILE_KEY=$(echo "$FILE_URL" | sed -E 's#.*/(design|file)/([A-Za-z0-9]+).*#\2#')

Workflow

  1. Pick the two versions. List them first if you don't have the IDs:

    bash
    ../figma-version-history/scripts/list-versions.sh ABC123def456
  2. Generate the changelog with scripts/generate-changelog.mjs:

    bash
    # Page-level changelog against HEAD
    node scripts/generate-changelog.mjs --file ABC123def456 --from 4096761871 --to current
    
    # Include per-component changes, detailed bullets
    node scripts/generate-changelog.mjs --file ABC123def456 --from 4096761871 --to 4096800000 \
      --components 695:313,420:88 --mode detailed

    By default it prints markdown to stdout. Pass --json to get { markdown, data } (the structured diff alongside the rendered text). Redirect to a file for release notes:

    bash
    node scripts/generate-changelog.mjs --file ABC123def456 --from 4096761871 --to current \
      > CHANGELOG-figma.md
  3. Modes mirror the diff: summary (one punchy line of counts), standard (sectioned with counts, default), detailed (full per-property and per-binding bullets).

What it captures

  • A header with From / To version refs — label (or (unlabeled)), date, and author handle — plus the span in days. Author/label come from one extra cheap call to the versions list.
  • A Page Structure section: pages added / removed / renamed.
  • A Components section (when --components is passed): per-component change counts and bullets for renames, description changes, children added/removed, componentPropertyDefinitions changes, and variable-binding changes.
  • A Notes section listing the diff's known blind spots (instances on the canvas, raw layout/visual props, variable VALUE changes, style content — none of which Figma REST exposes for historical versions).

Notes

  • Author enrichment is best-effort: it pages the versions list up to ~200 entries back to find each version's metadata. If a version is older than that lookback (or Figma system-attributed), the ref degrades gracefully to the version id.
  • current/HEAD references render as "Current state (last modified …)".

Bundled files

The model reads these on demand while the skill is loaded. They are exposed as readable files and are never executed.

Frequently asked questions

What does the Figma Generate Changelog AI skill do?

Generate a human-readable markdown changelog between two Figma file versions — pages added/removed/renamed plus per-component changes, enriched with author handles and timestamps, ready to paste into release notes, PRs, or Storybook MDX. Use when the user wants prose history — triggers: 'generate a Figma changelog', 'write release notes from Figma', 'what changed between these versions in markdown', 'summarize Figma changes for the PR', 'changelog between version A and B', 'design changelog since last release'. Uses the Figma REST API + a personal access token because version history is NOT...

Why use Figma Generate Changelog on TypingMind?

Because you install it once and use it with any model. Figma Generate Changelog is plain Markdown rather than provider-specific code, so the same skill runs on GPT-5, Claude, Gemini, Grok, or a local model — and you can switch model mid-chat without it breaking. TypingMind runs on your own API keys, so you pay providers directly instead of a per-seat subscription, and your skills and chats stay in your own storage.

How do I install Figma Generate Changelog in TypingMind?

Open Plugins → Skills → Install from GitHub in TypingMind and paste https://github.com/southleft/figma-console-mcp-skills/tree/main/skills/figma-generate-changelog. TypingMind reads its SKILL.md and bundles its files and installs it as a skill you can enable per chat.

Which AI models can use Figma Generate Changelog?

Any model you connect in TypingMind. AI skills are plain Markdown instructions rather than provider-specific code, so GPT, Claude, Gemini, Grok, and local models can all load this skill when a request matches it.

How many AI models can I use with Figma Generate Changelog?

As many as you like. As long as a model supports skills, you can use Figma Generate Changelog with it — GPT, Claude, Gemini, Grok, DeepSeek, Mistral, Llama and more — all on TypingMind with your own API keys.

Is the Figma Generate Changelog AI skill free?

Yes. It is published on GitHub by southleft under the MIT license. You only pay your own AI provider for the tokens you use.

What are AI skills?

An AI skill is a reusable instruction bundle that teaches an AI model how to do one specific task. It follows the open Agent Skills format: a SKILL.md file with a name and description, plus any scripts, templates or reference files the model may need. The model reads the instructions only when your request matches the skill, so an installed skill costs nothing until it is used.

How are AI skills different from plugins or MCP servers?

A plugin or MCP server gives a model new tools to call — code that runs somewhere and returns a result. An AI skill gives the model knowledge and process instead: how to approach a task, which steps to follow, what good output looks like. Skills are plain Markdown, so they need no server, no API key and no runtime, and they work with any model.

View all

Set up your own AI workspace now

Get notified about new features and future giveaways by subscribing to our newsletter 👇