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 re
npx skills add southleft/figma-console-mcp-skills --skill figma-generate-changelog --agent claude-code
Same command for any agent — swap --agent for codex, cursor, copilot.
Weekly change comes from our own snapshots, not the repository page — it measures attention, not adoption.
# 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](../figma-version-history/SKILL.md) for the structured diff and the endpoint reference. ## Derive the file ke
- Setup & skill boundaries
- Derive the file key
- Workflow
- What it captures
- Notes
node scripts/generate-changelog.mjs --file ABC123def456 --from 4096761871 --to current node scripts/generate-changelog.mjs --file ABC123def456 --from 4096761871 --to 4096800000 \ node scripts/generate-changelog.mjs --file ABC123def456 --from 4096761871 --to current \
What does the figma-generate-changelog 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 re
How do I install it?
Run `npx skills add southleft/figma-console-mcp-skills --skill figma-generate-changelog --agent claude-code` — it drops the skill into your project so the agent can pick it up. Swap the --agent value for codex, cursor or copilot if you use one of those.
Where does this skill come from?
From southleft/figma-console-mcp-skills, a repository with 67 stars. We read it straight from the repository tree rather than a submitted listing, so what you see here is what is actually published.
Is a popular skill a good skill?
Not necessarily. Stars measure attention, not adoption — a repository can trend for a week and be abandoned. That is why we show the weekly change from our own snapshots next to the total, instead of a single flattering number.