React Router Release Notes Prep
remix-run/react-router
Polishes pending React Router change files before the versioning scripts run, and decides whether a long-form What's Changed section is warranted.
Generate concise, user-facing changelog entries for Microlink by inspecting git commits across relevant repositories.
Install Generate Changelog
$ npx skills add microlinkhq/www --skill generate-changelog -a claude-codeProject install by default; add -g for ~/.claude/skills/.
$ gh skill install microlinkhq/www generate-changelog --agent claude-codeProject scope by default; add --scope user for a personal install. Needs GitHub CLI 2.90.0 or later (public preview).
$ git clone --depth 1 https://github.com/microlinkhq/www.git skills-src && mkdir -p .claude/skills && cp -r skills-src/.agents/skills/generate-changelog .claude/skills/generate-changelog && rm -rf skills-srcUse ~/.claude/skills/ instead of .claude/skills for a personal install. The folder must contain SKILL.md.
Claude Code skills documentation · loads skills from .claude/skills/
Install the "generate-changelog" agent skill from https://github.com/microlinkhq/www/tree/master/.agents/skills/generate-changelog into .claude/skills/generate-changelog/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "generate-changelog", then confirm the skill loads.Claude Code copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
$skill-installer install https://github.com/microlinkhq/www/tree/master/.agents/skills/generate-changelogType this inside Codex. $skill-installer <name> installs a curated skill from openai/skills. The installer writes to $CODEX_HOME/skills (default ~/.codex/skills). Restart Codex if the skill does not show up.
$ npx skills add microlinkhq/www --skill generate-changelog -a codexProject install goes to .agents/skills/; add -g for ~/.codex/skills/.
$ gh skill install microlinkhq/www generate-changelog --agent codexProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/microlinkhq/www.git skills-src && mkdir -p .agents/skills && cp -r skills-src/.agents/skills/generate-changelog .agents/skills/generate-changelog && rm -rf skills-srcUse ~/.agents/skills/ instead of .agents/skills for a personal install.
Codex skills documentation · loads skills from .agents/skills/
Install the "generate-changelog" agent skill from https://github.com/microlinkhq/www/tree/master/.agents/skills/generate-changelog into .agents/skills/generate-changelog/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "generate-changelog", then confirm the skill loads.Codex copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
$ npx skills add microlinkhq/www --skill generate-changelog -a cursorProject install goes to .agents/skills/; add -g for ~/.cursor/skills/.
$ gh skill install microlinkhq/www generate-changelog --agent cursorProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/microlinkhq/www.git skills-src && mkdir -p .cursor/skills && cp -r skills-src/.agents/skills/generate-changelog .cursor/skills/generate-changelog && rm -rf skills-srcUse ~/.cursor/skills/ instead of .cursor/skills for a personal install.
Cursor skills documentation · loads skills from .cursor/skills/, .agents/skills/, .claude/skills/, .codex/skills/
Install the "generate-changelog" agent skill from https://github.com/microlinkhq/www/tree/master/.agents/skills/generate-changelog into .cursor/skills/generate-changelog/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "generate-changelog", then confirm the skill loads.Cursor copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
$ gemini skills install https://github.com/microlinkhq/www.git --path .agents/skills/generate-changelog--scope user (default) or --scope workspace; --path is the subfolder of the repo that holds the skill; --consent skips the security confirmation prompt.
$ npx skills add microlinkhq/www --skill generate-changelog -a gemini-cliProject install goes to .agents/skills/; add -g for ~/.gemini/skills/.
$ gh skill install microlinkhq/www generate-changelog --agent gemini-cliProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/microlinkhq/www.git skills-src && mkdir -p .gemini/skills && cp -r skills-src/.agents/skills/generate-changelog .gemini/skills/generate-changelog && rm -rf skills-srcUse ~/.gemini/skills/ instead of .gemini/skills for a personal install, then run /skills reload.
Gemini CLI skills documentation · loads skills from .gemini/skills/, .agents/skills/
Install the "generate-changelog" agent skill from https://github.com/microlinkhq/www/tree/master/.agents/skills/generate-changelog into .gemini/skills/generate-changelog/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "generate-changelog", then confirm the skill loads.Gemini CLI copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
$ gh skill install microlinkhq/www generate-changelogInstalls for Copilot at project scope by default; add --scope user for a personal install. Preview a skill first with gh skill preview. Needs GitHub CLI 2.90.0 or later (public preview).
$ npx skills add microlinkhq/www --skill generate-changelog -a github-copilotProject install goes to .agents/skills/; add -g for ~/.copilot/skills/.
$ git clone --depth 1 https://github.com/microlinkhq/www.git skills-src && mkdir -p .github/skills && cp -r skills-src/.agents/skills/generate-changelog .github/skills/generate-changelog && rm -rf skills-srcUse ~/.copilot/skills/ instead of .github/skills for a personal install. Commit .github/skills so cloud agent and code review can use it.
GitHub Copilot skills documentation · loads skills from .github/skills/, .claude/skills/, .agents/skills/
Install the "generate-changelog" agent skill from https://github.com/microlinkhq/www/tree/master/.agents/skills/generate-changelog into .github/skills/generate-changelog/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "generate-changelog", then confirm the skill loads.GitHub Copilot copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
$ npx skills add microlinkhq/www --skill generate-changelog -a opencodeOpenCode documents no install command of its own. Project install goes to .agents/skills/; add -g for ~/.config/opencode/skills/.
$ gh skill install microlinkhq/www generate-changelog --agent opencodeProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/microlinkhq/www.git skills-src && mkdir -p .opencode/skills && cp -r skills-src/.agents/skills/generate-changelog .opencode/skills/generate-changelog && rm -rf skills-srcUse ~/.config/opencode/skills/ instead of .opencode/skills for a personal install.
OpenCode skills documentation · loads skills from .opencode/skills/, .claude/skills/, .agents/skills/
Install the "generate-changelog" agent skill from https://github.com/microlinkhq/www/tree/master/.agents/skills/generate-changelog into .opencode/skills/generate-changelog/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "generate-changelog", then confirm the skill loads.OpenCode copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
Facts
- Skill name
generate-changelog- GitHub stars
- 142
- Token cost
- ~1.9k tokens
- SKILL.md length
- 739 words
- Files
- 1
- Skills in repo
- 6
- Repo updated
- First seen
- Licence
- MIT
At a glance
Generate concise, user-facing changelog entries for Microlink by inspecting git commits across relevant repositories.
- Works in 8 steps: Determine the cutoff date → Read the current changelog → Scan repositories for commits → …
- Tasks that involve Changelog and release notes
- SKILL.md covers When to use and Steps
- Calls git; reaches unavatar.io and browserless.js.org
What it does
Generate Changelog is an agent skill from microlinkhq/www. Generate concise, user-facing changelog entries for Microlink by inspecting git commits across relevant repositories.
Its SKILL.md is about 1.9k tokens, which your agent loads only when the skill is triggered. It is a single SKILL.md file with no bundled scripts.
It sits in Development, covering Changelog and release notes and Commit messages. The repository describes itself as: AI-ready infrastructure for interacting with the web. Built on real browsers. Exposed through a single API. The licence is MIT.
When your agent uses it
- Tasks that involve Changelog and release notes
- Tasks that involve Commit messages
Example prompts
- “/generate-changelog”
Workflow steps
8 steps, taken from the step headings in SKILL.md.
What it can do on your machine
Read from SKILL.md and the folder at commit d160a67. It shows what the files ask for, not the result of running them.
Tool permissions
Pre-approves nothing: there is no allowed-tools line, so your agent's usual permission prompts apply.
From allowed-tools in the SKILL.md frontmatter.
Runs code
Shell commands in SKILL.md call:
git
From the folder's file list and the shell code blocks in SKILL.md.
Network
Hosts in commands or code, which the agent is likely to contact:
unavatar.iobrowserless.js.orgmetascraper.js.org
From URLs in SKILL.md, links to its own repository left out.
Credentials
Names no API keys, tokens, secrets or passwords.
From names ending in _API_KEY, _TOKEN, _SECRET, _KEY or _PASSWORD in SKILL.md.
Context cost
Generate Changelog loads about 1.9k tokens when it runs. Until then it costs about 34 tokens; SKILL.md has 739 words of instructions outside code blocks.
Estimates: characters ÷ 4, the usual rule of thumb; real counts depend on the model's tokenizer. Scripts and assets cost tokens only if the agent reads them.
Safety
Auto-check passed
The automated check found no risky patterns in SKILL.md.
Automated static check — not a guarantee. Review scripts before installing. It scans the text of SKILL.md for risky patterns (piping downloads into a shell, reading credential files, hidden Unicode, destructive commands); files beside SKILL.md are not scanned.
SKILL.md
The full file from microlinkhq/www at commit d160a67, republished under its MIT licence (© microlinkhq). 739 words, ~1,924 tokens.
Download SKILL.mdSave it as
.claude/skills/generate-changelog/SKILL.md (or your agent's skills folder).- name
- generate-changelog
- description
- Generate concise, user-facing changelog entries for Microlink by inspecting git commits across relevant repositories.
Generate Changelog
Generate concise, user-facing changelog entries for src/content/fragments/changelog.md by inspecting git commits across all Microlink repositories since the last changelog edit.
When to use
Run this skill when you need to update the changelog with recent changes. It scans all relevant repos and produces entries grouped by month. The changelog is read newest to oldest — both across months and within each month section.
Steps
1. Determine the cutoff date
Find the last time the changelog file was modified:
git log -1 --format="%ai" -- src/content/fragments/changelog.mdUse that date as the --after boundary for all repo scans.
2. Read the current changelog
Read src/content/fragments/changelog.md to understand the existing format and identify which months already have entries (to avoid duplicates).
3. Scan repositories for commits
Scan commits after the cutoff date across these repo groups:
Microlink repos at ~/Projects/microlink/:
| Repo | Changelog relevance |
|---|---|
api | API features, fixes, new parameters, resolution improvements |
metascraper | New integrations, detection improvements |
browserless | Major versions, Puppeteer upgrades, new packages |
mql | SDK changes, new features |
sdk | SDK changes |
www | New pages, landings, tools, blog posts |
html-get | Extraction improvements |
gateway | Dashboard changes (only if user-facing) |
openkey | Releases |
splashy | Releases |
youtube-dl-exec | Releases |
tinyspawn | Releases |
geolocation | UI changes, new features |
fonts | New features |
cards | New presets |
skills | New skills (only if user-facing) |
microlink | SDK and CLI — new methods, commands, flags, output formats |
function | Microlink Function SDK — new packages, API changes, runtime updates |
google | Releases, new Google product support |
is-antibot | Major versions (improves API antibot resolution) |
oembed-spec | Major versions only |
unavatar repos at ~/Projects/unavatar/:
| Repo | Changelog relevance |
|---|---|
unavatar | New providers, new features (public library) |
api | API changes, new endpoints |
www | Website changes |
For each repo, run:
cd <repo-path> && git log --format="%h %ad %s" --date=format:"%Y-%m-%d" --after="<cutoff>" --no-merges4. Filter for user-facing changes
Include commits that match:
feat:orfeat(...):— new features- New pages, landings, tools in
www - New providers or integrations
- New presets (cards)
- Major version releases
- Blog posts
- Significant
fix:commits that affect user-visible behavior (resolution, rendering, extraction) perf:commits with user-visible impact (e.g., Puppeteer upgrade)
Exclude commits that are purely internal:
chore: update dependencies/build(deps):— dependency bumpschore(release):— release tags (use them to identify versions, not as entries)ci:/build:— CI and build configtest:— test-only changeschore(statsd):/chore(sentry):— observability internalschore(k8s):/chore(base):— infrastructurerefactor:— unless it changes user-facing behaviorRevert— unless it reverts a user-facing feature
Show full SKILL.md (371 more words)Show less
5. Group by month and compose entries
Group changes by month (### Month YYYY).
Within each month, sort entries newest first (reverse chronological). Use commit dates from the repo scans to determine order. When a change spans multiple repos on the same day, any stable order is fine — what matters is that earlier-in-the-month entries appear lower in the section.
Do not group by product within a month. The reader scans top-to-bottom from most recent to oldest.
When multiple user-facing changes ship on different dates under the same product (e.g., three dashboard updates across a week), prefer one entry per change so each line sits at the correct chronological position. Avoid rolling them into a single composite entry unless they shipped together.
Product link conventions (for writing entries, not for ordering):
[Microlink](/)— website pages, landings, tools[Microlink API](/docs/api/getting-started/overview)— API features and fixes[Browserless](https://browserless.js.org)— include version when relevant[Metascraper](https://metascraper.js.org)— include version when relevant[Microlink MQL](/docs/mql/getting-started/overview)— MQL changes[Microlink SDK](/docs/sdk/getting-started/overview)— SDK changes[Microlink OSS](/oss)— other OSS releases[unavatar.io](https://unavatar.io)— providers and features
6. Entry format rules
Each entry follows this format:
- [Product](link): Description.Specific conventions:
- unavatar providers: link to
https://unavatar.io/<provider>(e.g.,[Steam](https://unavatar.io/steam)). Group multiple providers in a single entry. - Browserless/Metascraper versions: include version in product name (e.g.,
[Browserless v13](https://browserless.js.org)). Use release tags to determine version numbers. - API parameters: link to the parameter docs page when available (e.g.,
[function](/docs/api/parameters/function)). - www pages: link to the page path (e.g.,
[embed](/embed),[pricing](/pricing)). - Blog posts: use format
[Microlink Blog](/blog): Published [Title](/blog/slug). - Keep it concise: one line per entry, describe the user impact, not the implementation.
- No internal jargon: avoid mentioning Redis, Kubernetes, Datadog, Sentry, statsd, etc.
7. Present entries for review
Show the proposed entries to the user before editing the file. Ask if any entries should be added, removed, or reworded.
8. Insert into changelog
- New month: prepend the
### Month YYYYsection at the top of the file, before the first existing month header. Sort all entries in that section newest first. - Existing month: merge new entries into the matching month section and re-sort the entire section newest first. Do not append new entries at the bottom — that puts the freshest changes last, which is the wrong reading order.
- Older months: do not modify entries in months that are not being updated.
© microlinkhq, MIT. Rendered from Markdown: HTML in the file is shown as text, images as links, and headings moved down two levels. Raw file
Files
Just SKILL.md in .agents/skills/generate-changelog of microlinkhq/www.
Open the folder on GitHubat commit d160a67
Compare with similar skills
Generate Changelog next to the 5 skills that share the most tags, products or categories with it. Stars are the repository's; “used in” counts other GitHub owners with a copy.
| Skill | Stars | Used in | Tokens | Auto-check | Licence | Repo updated |
|---|---|---|---|---|---|---|
| Generate Changelog this skillmicrolinkhq/www | 142 | — | ~1.9k | Automated safety check: Pass | MIT | |
| React Router Release Notes Prepremix-run/react-router | 57k | — | ~1.1k | Automated safety check: Pass | MIT | |
| Git Workflow and Versioningaddyosmani/agent-skills | 103k | 2 repos | ~3.5k | Automated safety check: Notes | MIT | |
| Verdaccio Pull Request Workflowverdaccio/verdaccio | 18k | — | ~1.9k | Automated safety check: Pass | MIT | |
| Commitizencommitizen-tools/commitizen | 3.5k | — | ~839 | Automated safety check: Pass | MIT | |
| Commit And PR Messagessuperplanehq/superplane | 7.7k | — | ~1.6k | Automated safety check: Pass | Custom licence |
Similar skills
Git Workflow and Versioning
addyosmani/agent-skills
Sets git habits for every change: short-lived branches, atomic commits with descriptive messages, clean pull requests, plus versioning, tagging and changelogs for releases.
Verdaccio Pull Request Workflow
verdaccio/verdaccio
Takes a change through a verdaccio pull request: branch, local checks, changeset, title and body, labels, CI and review rounds, and ports to other release lines.
Commitizen
commitizen-tools/commitizen
A skill your agent uses for tasks involving Conventional Commits, commit message validation, Commitizen configuration, semantic version bumps, changelog generation, or CI/release automation with the…
Commit And PR Messages
superplanehq/superplane
Write Git commit messages and pull request titles/descriptions using the Chris Beams / Tim Pope conventions (subject/body split, ~50-char subject, imperative mood, why-not-how body) plus ASD-STE100…
Plane Release Notes Generator
makeplane/plane
Builds categorized release notes for a Plane release pull request from its commits and writes them into the PR description, for both the plane-cloud and plane-ee repos.
More from microlinkhq/www
Customer Story
microlinkhq/www
Scaffold a customer story page under src/pages/use-cases/customers/ from the CustomerStory module.
Guide Authoring
microlinkhq/www
Create or revise docs guides under src/content/docs/guides with runnable MDX examples.
Use Case Landing
microlinkhq/www
Create or improve use-case landing pages under src/pages/use-cases/ from the UseCaseStory module.
Verify
microlinkhq/www
Verify UI changes in microlink/www by driving the Gatsby dev server with agent-browser.
Alternative Landing
microlinkhq/www
Create or improve competitor alternative pages under src/pages/alternative/.
Related
Categories
Questions about Generate Changelog
What does Generate Changelog do?
Generate concise, user-facing changelog entries for Microlink by inspecting git commits across relevant repositories. Generate Changelog is an agent skill from microlinkhq/www. Generate concise, user-facing changelog entries for Microlink by inspecting git commits across relevant repositories.
When should I use Generate Changelog?
Generate Changelog fits situations like: tasks that involve Changelog and release notes; tasks that involve Commit messages.
How do I install Generate Changelog in Claude Code?
Run `npx skills add microlinkhq/www --skill generate-changelog -a claude-code`. Or copy the skill folder (.agents/skills/generate-changelog in microlinkhq/www) into .claude/skills/generate-changelog in your project. Claude Code loads it when a task matches its description.
How do I install Generate Changelog in Codex?
Run `npx skills add microlinkhq/www --skill generate-changelog -a codex`. Or copy the skill folder (.agents/skills/generate-changelog in microlinkhq/www) into .agents/skills/generate-changelog in your project. Codex loads it when a task matches its description.
Can I use Generate Changelog in Cursor, Gemini CLI or GitHub Copilot?
Cursor, Gemini CLI, GitHub Copilot and OpenCode also load SKILL.md folders. With the skills CLI, run `npx skills add microlinkhq/www --skill generate-changelog -a cursor` (or -a gemini-cli, github-copilot or opencode for the others). To copy it by hand, put the folder in .cursor/skills/generate-changelog, .gemini/skills/generate-changelog, .github/skills/generate-changelog and .opencode/skills/generate-changelog in your project.
What does Generate Changelog need to run?
Going by SKILL.md and its folder, Generate Changelog needs the command-line tools its instructions call (git).
Does Generate Changelog access the network?
SKILL.md names 3 domains. In commands or code: unavatar.io, browserless.js.org and metascraper.js.org; the agent is likely to contact these when it follows the instructions. This is read from the text; nothing was executed.
Is Generate Changelog safe to install?
Our automated static check of SKILL.md found no risky patterns, such as piping downloads into a shell, reading credential files or hidden Unicode. It is not a guarantee. Review the folder before installing.
What licence does Generate Changelog use?
Generate Changelog is published under the MIT licence (the repository's licence). It allows redistribution, so the full SKILL.md is shown on this page.
How many tokens does Generate Changelog use?
About 1.9k tokens (SKILL.md is roughly 7.7k characters). Agents keep only the skill's name and description in context until a task matches; then they load SKILL.md in full.
What are the alternatives to Generate Changelog?
Skills that share tags, products or a category with Generate Changelog: React Router Release Notes Prep (remix-run/react-router, 57k stars), Git Workflow and Versioning (addyosmani/agent-skills, 103k stars), Verdaccio Pull Request Workflow (verdaccio/verdaccio, 18k stars) and Commitizen (commitizen-tools/commitizen, 3.5k stars). The comparison table on this page puts their stars, adoption, token cost, safety result and licence side by side.
Who maintains Generate Changelog?
microlinkhq (a GitHub organization) maintains it in microlinkhq/www, which has 142 GitHub stars. The repository holds 6 skills in this directory. The repository was last updated on October 7, 2026.
Source: microlinkhq/www on GitHub. Facts on this page come from the repository at the commit we read; the author's words are quoted as theirs.