Verdaccio Change Implementation
verdaccio/verdaccio
A workflow for implementing a Verdaccio bug fix, feature or refactor: pick the release lines, check existing options, edit the owning layer, test and add a changeset.
Implement a pnpm feature, bug fix, or refactor by checking existing capabilities, prioritizing code reuse and deduplication, assessing architecture impact, and validating the final change.
Install Implement Change
$ npx skills add pnpm/pnpm --skill implement-change -a claude-codeProject install by default; add -g for ~/.claude/skills/.
$ gh skill install pnpm/pnpm implement-change --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/pnpm/pnpm.git skills-src && mkdir -p .claude/skills && cp -r skills-src/.agents/skills/implement-change .claude/skills/implement-change && 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 "implement-change" agent skill from https://github.com/pnpm/pnpm/tree/main/.agents/skills/implement-change into .claude/skills/implement-change/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "implement-change", 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/pnpm/pnpm/tree/main/.agents/skills/implement-changeType 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 pnpm/pnpm --skill implement-change -a codexProject install goes to .agents/skills/; add -g for ~/.codex/skills/.
$ gh skill install pnpm/pnpm implement-change --agent codexProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/pnpm/pnpm.git skills-src && mkdir -p .agents/skills && cp -r skills-src/.agents/skills/implement-change .agents/skills/implement-change && rm -rf skills-srcUse ~/.agents/skills/ instead of .agents/skills for a personal install.
Codex skills documentation · loads skills from .agents/skills/
Install the "implement-change" agent skill from https://github.com/pnpm/pnpm/tree/main/.agents/skills/implement-change into .agents/skills/implement-change/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "implement-change", 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 pnpm/pnpm --skill implement-change -a cursorProject install goes to .agents/skills/; add -g for ~/.cursor/skills/.
$ gh skill install pnpm/pnpm implement-change --agent cursorProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/pnpm/pnpm.git skills-src && mkdir -p .cursor/skills && cp -r skills-src/.agents/skills/implement-change .cursor/skills/implement-change && 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 "implement-change" agent skill from https://github.com/pnpm/pnpm/tree/main/.agents/skills/implement-change into .cursor/skills/implement-change/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "implement-change", 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/pnpm/pnpm.git --path .agents/skills/implement-change--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 pnpm/pnpm --skill implement-change -a gemini-cliProject install goes to .agents/skills/; add -g for ~/.gemini/skills/.
$ gh skill install pnpm/pnpm implement-change --agent gemini-cliProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/pnpm/pnpm.git skills-src && mkdir -p .gemini/skills && cp -r skills-src/.agents/skills/implement-change .gemini/skills/implement-change && 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 "implement-change" agent skill from https://github.com/pnpm/pnpm/tree/main/.agents/skills/implement-change into .gemini/skills/implement-change/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "implement-change", 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 pnpm/pnpm implement-changeInstalls 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 pnpm/pnpm --skill implement-change -a github-copilotProject install goes to .agents/skills/; add -g for ~/.copilot/skills/.
$ git clone --depth 1 https://github.com/pnpm/pnpm.git skills-src && mkdir -p .github/skills && cp -r skills-src/.agents/skills/implement-change .github/skills/implement-change && 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 "implement-change" agent skill from https://github.com/pnpm/pnpm/tree/main/.agents/skills/implement-change into .github/skills/implement-change/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "implement-change", 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 pnpm/pnpm --skill implement-change -a opencodeOpenCode documents no install command of its own. Project install goes to .agents/skills/; add -g for ~/.config/opencode/skills/.
$ gh skill install pnpm/pnpm implement-change --agent opencodeProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/pnpm/pnpm.git skills-src && mkdir -p .opencode/skills && cp -r skills-src/.agents/skills/implement-change .opencode/skills/implement-change && 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 "implement-change" agent skill from https://github.com/pnpm/pnpm/tree/main/.agents/skills/implement-change into .opencode/skills/implement-change/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "implement-change", 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
implement-change- GitHub stars
- 37k
- Token cost
- ~1.1k tokens
- SKILL.md length
- 556 words
- Files
- 1
- Skills in repo
- 7
- Repo updated
- First seen
- Licence
- MIT
At a glance
Implement a pnpm feature, bug fix, or refactor by checking existing capabilities, prioritizing code reuse and deduplication, assessing architecture impact, and validating the final change.
- Asked to implement a change in this repository
- SKILL.md covers Understand the problem before…, Assess the architecture, Prioritize reuse and… and Implement and validate
- Instructions only: no scripts, shell commands, URLs or credentials in SKILL.md
- Tasks that involve Data cleaning
What it does
Implement Change is an agent skill from pnpm/pnpm. Implement a pnpm feature, bug fix, or refactor by checking existing capabilities, prioritizing code reuse and deduplication, assessing architecture impact, and validating the final change. Use when asked to implement a change in this repository.
Its SKILL.md is about 1.1k 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 Data cleaning and Debugging. It works with pnpm. The repository describes itself as: Fast, disk space efficient package manager. The licence is MIT.
When your agent uses it
- Asked to implement a change in this repository
- Tasks that involve Data cleaning
- Tasks that involve Debugging
Example prompts
- “/implement-change”
What it can do on your machine
Read from SKILL.md and the folder at commit 3da5bd3. 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
No scripts in the folder and no shell commands in SKILL.md.
From the folder's file list and the shell code blocks in SKILL.md.
Network
No URLs in SKILL.md.
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
Implement Change loads about 1.1k tokens when it runs. Until then it costs about 66 tokens; SKILL.md has 556 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 pnpm/pnpm at commit 3da5bd3, republished under its MIT licence (© pnpm). 556 words, ~1,123 tokens.
Download SKILL.mdSave it as
.claude/skills/implement-change/SKILL.md (or your agent's skills folder).- name
- implement-change
- description
- Implement a pnpm feature, bug fix, or refactor by checking existing capabilities, prioritizing code reuse and deduplication, assessing architecture impact, and validating the final change. Use when asked to implement a change in this repository.
Implement a change
Apply PHILOSOPHY.md, AGENTS.md, and the relevant product instructions and style guides. Keep repository policy in those sources; this skill connects implementation to the testing-changes and review-code workflows.
Understand the problem before adding code
Establish the intended behavior and concrete success criteria from the user's request, reproduction, or specification. Determine which products and versions are affected using the repository's development policy. Reproduce bugs before choosing a fix when practical.
Always assess whether existing capabilities available to the affected product can solve the problem. For pnpm CLI work, consider combinations of commands, configuration, hooks, and workspace capabilities. For pnpr, assess its registry architecture, flags, and configuration. Consider applicable shared components across the repository as reuse candidates. Check their actual behavior against the success criteria. Prefer an existing capability when it fully solves the problem; explain how to use it and any limits. If it only partly solves the problem, identify the gap and extend the owning feature when that produces a cohesive design. Do not add a parallel feature merely because the request suggests a new setting or command. Respect an explicitly requested behavior that existing capabilities do not provide.
Assess the architecture
Before adding any new feature, analyze its effect on the overall architecture, not just the file being edited. Trace the affected data flow and responsibilities across commands, configuration, resolution, storage, or other relevant layers. Identify where the behavior belongs, which existing abstractions it extends, and how it interacts with related features and shared state or formats.
Summarize the architectural fit and meaningful tradeoffs before substantial implementation. Consider whether the change adds competing sources of truth, blurs a boundary, or introduces special cases other features will need to understand. Prefer a coherent extension over a local workaround. Keep necessary refactoring bounded to the change; architectural analysis is not authorization for an unrelated redesign.
Show full SKILL.md (250 more words)Show less
Prioritize reuse and deduplication
Search for similar behavior, helpers, and tests before writing non-trivial logic. Inspect the relevant product and shared utilities, including callers of candidate helpers. Prioritize removing duplication over adding another copy.
If the needed logic already exists, reuse it. If it is not reusable yet, extract the common behavior into the appropriate shared helper or package and update the affected callers. When consolidating stable features would break compatibility, temporary duplication may remain until the next major version; identify the intended shared abstraction and consolidation point. Experimental features can be consolidated immediately. Apply the same check to similar logic introduced by the change. Preserve meaningful differences in contracts; do not force unrelated behavior into a generic abstraction merely because the code looks alike. Follow the repository's dependency placement and library reuse rules.
Implement and validate
Implement the smallest cohesive change that satisfies the intended behavior. Add tests that exercise its observable contract and relevant interactions, and update documentation and changesets when repository policy requires them.
Use testing-changes to select and run appropriate checks. Investigate failures. Then use review-code on the complete diff, fix verified findings, and rerun checks affected by the fixes. Reassess reuse and architectural fit against the final implementation.
Report what changed, existing capabilities considered, the reuse or extraction chosen, material architectural implications, and validation limits. Scale the explanation to the change. Commit, push, or open a PR only when the user or calling workflow authorizes it; use pull-requests when taking the change through a PR.
© pnpm, 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/implement-change of pnpm/pnpm.
Open the folder on GitHubat commit 3da5bd3
Compare with similar skills
Implement Change 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 |
|---|---|---|---|---|---|---|
| Implement Change this skillpnpm/pnpm | 37k | — | ~1.1k | Automated safety check: Pass | MIT | |
| Verdaccio Change Implementationverdaccio/verdaccio | 18k | — | ~1.3k | Automated safety check: Pass | MIT | |
| Evlog Log Analyzerevloghq/evlog | 1.9k | — | ~2.4k | Automated safety check: Pass | MIT | |
| Optimizeopenplayerjs/openplayerjs | 649 | — | ~1.9k | Automated safety check: Pass | MIT | |
| Failure Diagnosis LoopTotoro-jam/battle-tested-patterns | 343 | — | ~319 | Automated safety check: Pass | MIT | |
| Update Depsviclafouch/meme-studio | 110 | — | ~2.6k | Automated safety check: Pass | None |
Similar skills
Evlog Log Analyzer
evloghq/evlog
Reads the structured wide-event logs that evlog writes to .evlog/logs/ so the agent can debug errors, find slow requests and explain what the app did.
Optimize
openplayerjs/openplayerjs
Find and safely apply ONE worthwhile code optimization (reuse, simplification, efficiency, or a dead-weight cleanup) somewhere in packages//src, with new regression tests proving behavior is…
Failure Diagnosis Loop
Totoro-jam/battle-tested-patterns
Walks the agent through a fixed loop for failing tests and build errors: reproduce, isolate, hypothesize, instrument, fix, verify, then add a regression test.
Update Deps
viclafouch/meme-studio
Audit all outdated dependencies with detailed research on changelogs, breaking changes, bug fixes, and deprecations.
OpenWork Desktop CDP Driver
different-ai/openwork
Drives a running OpenWork desktop window over CDP from the shell to evaluate JS, take screenshots, start sessions and send prompts for hand checks.
More from pnpm/pnpm
Pull Requests
pnpm/pnpm
Take a change through a pull request in the pnpm repository — opening it, then staying with it after every push until CI is green and the review round is quiet.
Release Notes
pnpm/pnpm
Curate a pending release page - merging entries that describe one change, dropping notes for defects that never shipped, ordering by importance, and checking the version the intents ask for.
Testing Changes
pnpm/pnpm
Run the tests that cover a change in the pnpm repository, in the Rust workspace (pnpm/, pnpr/) or the TypeScript CLI (pnpm11/), and recognize the cases where a scoped run passes without testing…
Review Code
pnpm/pnpm
Review a pnpm diff or pull request against the repository review guide and product conventions, verify findings, and report actionable issues.
Review And Fix PR
pnpm/pnpm
Review and fix an existing pnpm pull request, rebase it, commit and push fixes, then follow CI and review to completion.
Triage
pnpm/pnpm
Triage an incoming GitHub issue against the pnpm codebase and related open issues, then apply exactly one implementation-readiness label using pnpm's state: taxonomy.
Related
Works with
Categories
Questions about Implement Change
What does Implement Change do?
Implement a pnpm feature, bug fix, or refactor by checking existing capabilities, prioritizing code reuse and deduplication, assessing architecture impact, and validating the final change. Implement Change is an agent skill from pnpm/pnpm. Implement a pnpm feature, bug fix, or refactor by checking existing capabilities, prioritizing code reuse and deduplication, assessing architecture impact, and validating the final change.
When should I use Implement Change?
Implement Change fits situations like: asked to implement a change in this repository; tasks that involve Data cleaning; tasks that involve Debugging.
How do I install Implement Change in Claude Code?
Run `npx skills add pnpm/pnpm --skill implement-change -a claude-code`. Or copy the skill folder (.agents/skills/implement-change in pnpm/pnpm) into .claude/skills/implement-change in your project. Claude Code loads it when a task matches its description.
How do I install Implement Change in Codex?
Run `npx skills add pnpm/pnpm --skill implement-change -a codex`. Or copy the skill folder (.agents/skills/implement-change in pnpm/pnpm) into .agents/skills/implement-change in your project. Codex loads it when a task matches its description.
Can I use Implement Change 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 pnpm/pnpm --skill implement-change -a cursor` (or -a gemini-cli, github-copilot or opencode for the others). To copy it by hand, put the folder in .cursor/skills/implement-change, .gemini/skills/implement-change, .github/skills/implement-change and .opencode/skills/implement-change in your project.
What does Implement Change need to run?
SKILL.md names no scripts, command-line tools or credentials: Implement Change is instructions for the agent only.
Does Implement Change access the network?
SKILL.md contains no URLs. Any network use would come from the scripts or tools the agent runs. This is read from the text; nothing was executed.
Is Implement Change 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 Implement Change use?
Implement Change 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 Implement Change use?
About 1.1k tokens (SKILL.md is roughly 4.5k 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 Implement Change?
Skills that share tags, products or a category with Implement Change: Verdaccio Change Implementation (verdaccio/verdaccio, 18k stars), Evlog Log Analyzer (evloghq/evlog, 1.9k stars), Optimize (openplayerjs/openplayerjs, 649 stars) and Failure Diagnosis Loop (Totoro-jam/battle-tested-patterns, 343 stars). The comparison table on this page puts their stars, adoption, token cost, safety result and licence side by side.
Who maintains Implement Change?
pnpm (a GitHub organization) maintains it in pnpm/pnpm, which has 36,755 GitHub stars. The repository holds 7 skills in this directory. The repository was last updated on October 7, 2026.
Source: pnpm/pnpm on GitHub. Facts on this page come from the repository at the commit we read; the author's words are quoted as theirs.