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.
A skill your agent uses whenever the user asks about changelogs, Changesets, release notes, conventional commits, commit messages for release notes, or making user-visible project changes that…
Install Changeset Changelog
$ npx skills add jmfederico/pi-web --skill changeset-changelog -a claude-codeProject install by default; add -g for ~/.claude/skills/.
$ gh skill install jmfederico/pi-web changeset-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/jmfederico/pi-web.git skills-src && mkdir -p .claude/skills && cp -r skills-src/.agents/skills/changeset-changelog .claude/skills/changeset-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 "changeset-changelog" agent skill from https://github.com/jmfederico/pi-web/tree/main/.agents/skills/changeset-changelog into .claude/skills/changeset-changelog/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "changeset-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/jmfederico/pi-web/tree/main/.agents/skills/changeset-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 jmfederico/pi-web --skill changeset-changelog -a codexProject install goes to .agents/skills/; add -g for ~/.codex/skills/.
$ gh skill install jmfederico/pi-web changeset-changelog --agent codexProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/jmfederico/pi-web.git skills-src && mkdir -p .agents/skills && cp -r skills-src/.agents/skills/changeset-changelog .agents/skills/changeset-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 "changeset-changelog" agent skill from https://github.com/jmfederico/pi-web/tree/main/.agents/skills/changeset-changelog into .agents/skills/changeset-changelog/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "changeset-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 jmfederico/pi-web --skill changeset-changelog -a cursorProject install goes to .agents/skills/; add -g for ~/.cursor/skills/.
$ gh skill install jmfederico/pi-web changeset-changelog --agent cursorProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/jmfederico/pi-web.git skills-src && mkdir -p .cursor/skills && cp -r skills-src/.agents/skills/changeset-changelog .cursor/skills/changeset-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 "changeset-changelog" agent skill from https://github.com/jmfederico/pi-web/tree/main/.agents/skills/changeset-changelog into .cursor/skills/changeset-changelog/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "changeset-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/jmfederico/pi-web.git --path .agents/skills/changeset-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 jmfederico/pi-web --skill changeset-changelog -a gemini-cliProject install goes to .agents/skills/; add -g for ~/.gemini/skills/.
$ gh skill install jmfederico/pi-web changeset-changelog --agent gemini-cliProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/jmfederico/pi-web.git skills-src && mkdir -p .gemini/skills && cp -r skills-src/.agents/skills/changeset-changelog .gemini/skills/changeset-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 "changeset-changelog" agent skill from https://github.com/jmfederico/pi-web/tree/main/.agents/skills/changeset-changelog into .gemini/skills/changeset-changelog/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "changeset-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 jmfederico/pi-web changeset-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 jmfederico/pi-web --skill changeset-changelog -a github-copilotProject install goes to .agents/skills/; add -g for ~/.copilot/skills/.
$ git clone --depth 1 https://github.com/jmfederico/pi-web.git skills-src && mkdir -p .github/skills && cp -r skills-src/.agents/skills/changeset-changelog .github/skills/changeset-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 "changeset-changelog" agent skill from https://github.com/jmfederico/pi-web/tree/main/.agents/skills/changeset-changelog into .github/skills/changeset-changelog/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "changeset-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 jmfederico/pi-web --skill changeset-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 jmfederico/pi-web changeset-changelog --agent opencodeProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/jmfederico/pi-web.git skills-src && mkdir -p .opencode/skills && cp -r skills-src/.agents/skills/changeset-changelog .opencode/skills/changeset-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 "changeset-changelog" agent skill from https://github.com/jmfederico/pi-web/tree/main/.agents/skills/changeset-changelog into .opencode/skills/changeset-changelog/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "changeset-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
changeset-changelog- GitHub stars
- 869
- Token cost
- ~1.5k tokens
- SKILL.md length
- 689 words
- Files
- 2
- Skills in repo
- 7
- Repo updated
- First seen
- Licence
- MIT
At a glance
A skill your agent uses whenever the user asks about changelogs, Changesets, release notes, conventional commits, commit messages for release notes, or making user-visible project changes that…
- The user asks about changelogs
- SKILL.md covers Core rules, When a changeset is needed, How to create a changeset and Choosing patch/minor/major, plus 3 more sections
- Calls npm and changeset
- Conventional commits
What it does
Changeset Changelog is an agent skill from jmfederico/pi-web. Use this skill whenever the user asks about changelogs, Changesets, release notes, conventional commits, commit messages for release notes, or making user-visible project changes that should appear in a future npm/GitHub release. Trigger when preparing commits or PRs that include features, fixes, docs users rely on, package behavior changes, CLI changes, install changes, or release process changes. This skill keeps CHANGELOG.md generated at release time instead of manually edited during development.
Its SKILL.md is about 1.5k tokens, which your agent loads only when the skill is triggered. The skill folder holds 2 other files (for example `evals/evals.json`).
It sits in Development, covering Changelog and release notes and Commit messages. It works with npm and GitHub. The repository describes itself as: Web UI for Pi Coding Agent that keeps sessions alive in real workspaces. The licence is MIT.
When your agent uses it
- The user asks about changelogs
- Conventional commits
- Commit messages for release notes
- Making user-visible project changes that should appear in a future npm/GitHub release
Example prompts
- “/changeset-changelog”
What it can do on your machine
Read from SKILL.md and the folder at commit 2961669. 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:
npmchangeset
From the folder's file list and the shell code blocks in SKILL.md.
Network
No URLs in SKILL.md. Its commands use npm, which can reach the network depending on how they are called.
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
Changeset Changelog loads about 1.5k tokens when it runs. Until then it costs about 131 tokens; SKILL.md has 689 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 jmfederico/pi-web at commit 2961669, republished under its MIT licence (© jmfederico). 689 words, ~1,481 tokens.
Download SKILL.mdSave it as
.claude/skills/changeset-changelog/SKILL.md (or your agent's skills folder). This skill also uses 1 other file; get the full folder from GitHub.- name
- changeset-changelog
- description
- Use this skill whenever the user asks about changelogs, Changesets, release notes, conventional commits, commit messages for release notes, or making user-visible project changes that should appear in a future npm/GitHub release. Trigger when preparing commits or PRs that include features, fixes, docs users rely on, package behavior changes, CLI changes, install changes, or release process changes. This skill keeps CHANGELOG.md generated at release time instead of manually edited during development.
Changeset changelog workflow
This project uses Changesets so release notes are collected as small per-change markdown files during development and converted into CHANGELOG.md during release prep. This avoids multiple branches editing the same CHANGELOG.md section.
Core rules
- For user-visible changes, add a
.changeset/*.mdfragment. - Do not manually edit
CHANGELOG.mdduring normal feature/fix work. Letchangeset versiongenerate or update it during release prep. - Use Conventional Commit style for commit messages when committing, but do not rely on commit messages as the only changelog source.
- Write release notes for users, not as raw implementation logs.
When a changeset is needed
Create a changeset for changes that affect users, operators, package consumers, or release/install behavior, including:
- New features or UI behavior
- Bug fixes users can observe
- CLI, package exports, install, service, or configuration changes
- Documentation users rely on for setup or usage
- Dependency/runtime requirement changes
- Release-process changes that future maintainers need to see
A changeset is usually not needed for purely internal refactors, tests, lint-only changes, or build cleanup unless the user wants them recorded.
A changeset is also not needed for changes that are not part of what a pi-web release ships to users. The release is the published npm package, and its contents are an allowlist defined by the files field in package.json (plus package.json itself). Anything outside that allowlist never reaches package consumers, so it cannot be a user-visible release change. This includes repo-only material such as agent skills under .agents/ and skills/, internal docs, CI config, and developer tooling. If you are unsure whether a path ships, check it against package.json files (or run npm pack --dry-run); when a change lives entirely outside the published files, skip the changeset unless the user explicitly wants it recorded.
When in doubt, ask briefly or create a patch changeset with a clear note.
How to create a changeset
Prefer the CLI when interaction is practical:
npm run changesetFor non-interactive agent work, create a file manually under .changeset/ with a unique kebab-case name:
---
"@jmfederico/pi-web": patch
---
Fix session command handling so browser/API restarts do not interrupt active Pi sessions.Use the package name from package.json; for this repo it is @jmfederico/pi-web.
Show full SKILL.md (348 more words)Show less
Choosing patch/minor/major
This repo uses CalVer shaped as semver: MAJOR.YYYYMM.PATCH (for example, 1.202605.3). The semver minor position is the release month, not feature size. Because only the first component represents breaking compatibility, choose Changeset bump types this way:
patch: all non-breaking changes, including bug fixes, docs corrections, polish, release-process improvements, small compatible behavior changes, and new backward-compatible user-facing capabilities.minor: do not use for this repo. The release workflow setsYYYYMMfrom the release date.major: use only when the user explicitly requests a breaking/major release. Breaking changes can include changes to CLI, install expectations, package API, config, data formats, or supported runtime behavior.
If you believe a change is breaking but the user has not explicitly requested a major release, pause and ask the user to confirm whether to release it as a breaking major version or change the work so it remains non-breaking. Do not infer or perform a major version bump on your own.
During release prep, the npm release skill always computes the version from the release date (MAJOR.YYYYMM.PATCH) and increments PATCH only when another release already exists for that major/month. Do not ask whether to choose a patch increase or a date change for normal releases.
Writing good changeset text
Keep entries concise and user-facing:
- Start with an imperative or past-tense summary of the user impact.
- Mention the affected area when useful: sessions, web UI, CLI, install, extensions, release workflow.
- Avoid internal-only details like file names unless they help users.
- Avoid vague notes like “misc fixes” or “update code”.
Good examples:
Preserve active Pi sessions when the web/API development service restarts.Add a project-local release workflow skill that publishes npm packages through GitHub Actions instead of local publishing.Poor examples:
Changed sessionCommandService.ts.Fix stuff.Conventional Commit guidance
When asked to commit, use Conventional Commit style:
feat: add persistent session reconnect handlingfix: preserve queued commands across API restartsdocs: document systemd user serviceschore(release): v1.202605.4
Keep commits and changesets aligned, but remember their audiences differ:
- Commit message: developer history.
- Changeset text: future release notes for users.
Release prep handoff
During release prep, use the npm-release-via-github-actions skill. It should run:
npm run release:versionThat consumes .changeset/*.md, updates package.json / lockfile versions, and generates or updates CHANGELOG.md. Publishing still happens only through GitHub Actions after a GitHub Release is published.
© jmfederico, MIT. Rendered from Markdown: HTML in the file is shown as text, images as links, and headings moved down two levels. Raw file
Files
SKILL.md and 1 other file in .agents/skills/changeset-changelog of jmfederico/pi-web.
- SKILL.md
- evals/evals.json
Open the folder on GitHubat commit 2961669
Compare with similar skills
Changeset 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 |
|---|---|---|---|---|---|---|
| Changeset Changelog this skilljmfederico/pi-web | 869 | — | ~1.5k | Automated safety check: Pass | MIT | |
| Verdaccio Pull Request Workflowverdaccio/verdaccio | 18k | — | ~1.9k | Automated safety check: Pass | MIT | |
| Release WorkflowCaldis/react-zmage | 946 | — | ~3.6k | Automated safety check: Notes | MIT | |
| Codemie Releasecodemie-ai/codemie-code | 294 | — | ~1.8k | Automated safety check: Pass | Apache-2.0 | |
| Automate Commit Based Gh Release Changelogjd-solanki/slidev-theme-dracula | 161 | — | ~470 | Automated safety check: Pass | None | |
| Cutting A ReleaseTriliumNext/Trilium | 38k | — | ~3.2k | Automated safety check: Pass | AGPL-3.0 |
Similar skills
Release Workflow
Caldis/react-zmage
A skill your agent uses when the user wants to ship a new version of react-zmage to npm.
Codemie Release
codemie-ai/codemie-code
Release a new version of CodeMie CLI. An agent skill from codemie-ai/codemie-code.
Automate Commit Based Gh Release Changelog
jd-solanki/slidev-theme-dracula
Automate GitHub release creation and changelog generation from Conventional Commits using changelogithub — includes GitHub release mechanics, tag-based triggers, required permissions, and…
Cutting A Release
TriliumNext/Trilium
A skill your agent uses when cutting, preparing, or debugging a Trilium release — bumping the monorepo version, tagging, or diagnosing a failed "Release" workflow run.
Hunk Release Workflow
modem-dev/hunk
Maintainer workflow for preparing, publishing, verifying and curating Hunk releases, with confirmation gates before tags, publishes and public edits.
More from jmfederico/pi-web
npm Release Via GitHub Actions
jmfederico/pi-web
A skill your agent uses whenever the user asks for a new npm version, npm release, package release, new release, version bump, publishing to npm, cutting a GitHub release, tagging a release, or…
Testing Guide
jmfederico/pi-web
Repository-specific testing guide. An agent skill from jmfederico/pi-web.
Code Quality Architecture
jmfederico/pi-web
Project code quality and architecture expectations for implementation, refactoring, planning, and code review.
Documentation Guide
jmfederico/pi-web
Repository documentation placement and writing guidance. An agent skill from jmfederico/pi-web.
Relay
jmfederico/pi-web
Carry work across a chain of fresh agent contexts using a shared goal, compact baton, and durable record.
Relay Runner
jmfederico/pi-web
Prepare and run Relay legs in Pi: keep the goal, baton, and log durable, then hand off to one fresh session or stop visibly.
Related
Categories
Questions about Changeset Changelog
What does Changeset Changelog do?
A skill your agent uses whenever the user asks about changelogs, Changesets, release notes, conventional commits, commit messages for release notes, or making user-visible project changes that…. Changeset Changelog is an agent skill from jmfederico/pi-web. Use this skill whenever the user asks about changelogs, Changesets, release notes, conventional commits, commit messages for release notes, or making user-visible project changes that should appear in a future npm/GitHub release.
When should I use Changeset Changelog?
Changeset Changelog fits situations like: the user asks about changelogs; conventional commits; commit messages for release notes; making user-visible project changes that should appear in a future npm/GitHub release.
How do I install Changeset Changelog in Claude Code?
Run `npx skills add jmfederico/pi-web --skill changeset-changelog -a claude-code`. Or copy the skill folder (.agents/skills/changeset-changelog in jmfederico/pi-web) into .claude/skills/changeset-changelog in your project. Claude Code loads it when a task matches its description.
How do I install Changeset Changelog in Codex?
Run `npx skills add jmfederico/pi-web --skill changeset-changelog -a codex`. Or copy the skill folder (.agents/skills/changeset-changelog in jmfederico/pi-web) into .agents/skills/changeset-changelog in your project. Codex loads it when a task matches its description.
Can I use Changeset 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 jmfederico/pi-web --skill changeset-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/changeset-changelog, .gemini/skills/changeset-changelog, .github/skills/changeset-changelog and .opencode/skills/changeset-changelog in your project.
What does Changeset Changelog need to run?
Going by SKILL.md and its folder, Changeset Changelog needs the command-line tools its instructions call (npm and changeset).
Does Changeset Changelog access the network?
SKILL.md contains no URLs. Its commands use npm, which can reach the network depending on how they are called. This is read from the text; nothing was executed.
Is Changeset 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 Changeset Changelog use?
Changeset 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 Changeset Changelog use?
About 1.5k tokens (SKILL.md is roughly 5.9k 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 Changeset Changelog?
Skills that share tags, products or a category with Changeset Changelog: Verdaccio Pull Request Workflow (verdaccio/verdaccio, 18k stars), Release Workflow (Caldis/react-zmage, 946 stars), Codemie Release (codemie-ai/codemie-code, 294 stars) and Automate Commit Based Gh Release Changelog (jd-solanki/slidev-theme-dracula, 161 stars). The comparison table on this page puts their stars, adoption, token cost, safety result and licence side by side.
Who maintains Changeset Changelog?
jmfederico (a GitHub user) maintains it in jmfederico/pi-web, which has 869 GitHub stars. The repository holds 7 skills in this directory. The repository was last updated on October 9, 2026.
Source: jmfederico/pi-web on GitHub. Facts on this page come from the repository at the commit we read; the author's words are quoted as theirs.