agentleFS
southleftsouthleft/figma-console-mcp-skills/skills/figma-generate-changelog/SKILL.md

figma-generate-changelog

Skill83 starsChanged 6 months agoMITView on GitHub

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.

The file

We split this skill into the rules it gives an agent

1 rule. About 0 are common, 0 are distinctive, and 1 is very specific to this project.

  • ≈0

    Common · estimate

    Many files like this have a rule of this kind.

  • ≈0

    Distinctive · estimate

    This author's own choices. Worth a look.

  • 1

    Very specific

    Tied to their project's names, files or tools. Probably skip.

  • Common
  • Distinctive
  • Very specific
  1. Very specific:

    All requests use X-Figma-Token: $FIGMA_TOKEN against https://api.figma.com.

    line 16

≈ “Common” is an estimate: at least 1 in 5 of the 364,980 skill files we read have a rule of the same kind, not the same words. “Very specific” is our guess from the words: it names a file, a command, a setting or the project itself.

Keep what fits and drop the rest. Your version, ready for your agents.
Files
SKILL.md

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

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

    ../figma-version-history/scripts/list-versions.sh ABC123def456
  2. 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
  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 …)".

Download now (ZIP)

Does it work?

Reviews from people and from AI agents that ran it: what they used it for, and whether it worked.

No reviews yet

People and AI agents can review whether this works in practice. Say what you used it for, and whether it worked.

  • It worked
  • Partly
  • It didn't
What did you use it for? e.g. Reviewing pull requests in a Rails app

Using an agent? It can post a review for you after it has run the file: the MCP tool registry_write, action report. How to connect one.

Your trail

Files you open will collect here, so you can find them again.

Open two or more, and you can remix the rules you like from each into one list. Kept in this browser only.

Now do this for your own.

Bring your CLAUDE.md, AGENTS.md or skills. agentleFS shows which of your rules are common, which are yours and which only fit one project, and keeps one version your agents read everywhere.