How do I install the Figma Generate Changelog skill?

Run npx skillmds@latest add southleft/figma-generate-changelog in your terminal (requires Node.js), paste this page's agent-chat prompt into Claude, Cursor, or any MCP-connected agent, or download the SKILL.md file and copy it into your agent's skills directory.

Is Figma Generate Changelog safe to use?

This skill has not completed SkillMD's automated safety review yet. SkillMD never runs a skill's scripts for you; review the SKILL.md before installing.

Which AI agents work with Figma Generate Changelog?

This skill is tagged as working with Claude Code, Claude.ai, OpenAI Codex. SKILL.md is an open format, so most agents that read a skills directory can load it too.

Is Figma Generate Changelog free to use?

Yes. Installing skills from SkillMD is free, and the skill stays under its author's original license.

Who published Figma Generate Changelog?

southleft (@southleft) published this skill. Their other Agent Skills are listed on their SkillMD profile.

Figma Generate Changelog by southleft

Name: Figma Generate Changelog
Author: 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.

southleft Updated Sep 17, 2026

File contents

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

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

Workflow

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

../figma-version-history/scripts/list-versions.sh ABC123def456

Generate the changelog with scripts/generate-changelog.mjs:

# 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:

node scripts/generate-changelog.mjs --file ABC123def456 --from 4096761871 --to current \
  > CHANGELOG-figma.md

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 …)".

---name: figma-generate-changelogdescription: 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.---# figma-generate-changelog — markdown changelog between two versionsBuilds 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](../figma-version-history/SKILL.md) for the structured diff and the endpoint reference.## Derive the file key```bashFILE_KEY=$(echo "$FILE_URL" | sed -E 's#.*/(design|file)/([A-Za-z0-9]+).*#\2#')```## Workflow1. **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`](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 …)".

Frequently asked questions