New: 98,000+ skills indexed from GitHub repos with 100+ stars · every skill safety-checkedBrowse top skillsTop skills
Esc to closeBrowse all skills
Submit a skillBrowse skills
Submit a skillBrowse skills

Agent skill

Testing Changes

by pnpm in 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…

MITAuto-check passedDevelopment

Install Testing Changes

skills CLI
$ npx skills add pnpm/pnpm --skill testing-changes -a claude-code

Project install by default; add -g for ~/.claude/skills/.

GitHub CLI
$ gh skill install pnpm/pnpm testing-changes --agent claude-code

Project scope by default; add --scope user for a personal install. Needs GitHub CLI 2.90.0 or later (public preview).

Manual copy
$ git clone --depth 1 https://github.com/pnpm/pnpm.git skills-src && mkdir -p .claude/skills && cp -r skills-src/.agents/skills/testing-changes .claude/skills/testing-changes && rm -rf skills-src

Use ~/.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/

Facts

Skill name
testing-changes
GitHub stars
37k
Token cost
~1.1k tokens
SKILL.md length
575 words
Files
1
Skills in repo
7
Repo updated
First seen
Licence
MIT

At a glance

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…

  • Verifying a change before committing
  • SKILL.md covers Rust (pnpm/, pnpr/), TypeScript (pnpm11/), Both stacks and Reporting
  • Calls pnpm, just and cargo
  • Deciding what to run after an edit

What it does

Testing Changes is an agent skill from 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 anything. Use whenever verifying a change before committing or pushing, or when deciding what to run after an edit.

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. It works with pnpm, Rust, TypeScript and npm. The repository describes itself as: Fast, disk space efficient package manager. The licence is MIT.

When your agent uses it

  • Verifying a change before committing
  • Deciding what to run after an edit

Example prompts

  • “/testing-changes”

What it can do on your machine

Read from SKILL.md and the folder at commit 142365b. 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:

    • pnpm
    • just
    • cargo
    • node

    From the folder's file list and the shell code blocks in SKILL.md.

  • Network

    No URLs in SKILL.md. Its commands use pnpm, 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

Testing Changes loads about 1.1k tokens when it runs. Until then it costs about 81 tokens; SKILL.md has 575 words of instructions outside code blocks.

Always · name and description, kept in context so the agent knows when to use it
~81
When it runs · the whole SKILL.md, loaded when a task matches
~1.1k

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 142365b, republished under its MIT licence (© pnpm). 575 words, ~1,143 tokens.

Download SKILL.mdSave it as .claude/skills/testing-changes/SKILL.md (or your agent's skills folder).
name
testing-changes
description
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 anything. Use whenever verifying a change before committing or pushing, or when deciding what to run after an edit.

Testing a change

Run what the change affects. CI runs the full suite on three platforms for every pull request, so the local job is fast feedback, not a second gate. The per-commit checks are in pnpm/CONTRIBUTING.md.

Rust (pnpm/, pnpr/)

Run the tests through the root package.json scripts from the repository root: pnpm test:rust-affected, pnpm test:rust, pnpm test:rust-smoke. They wrap the just recipes and node scripts named below, pass their arguments through, and let a task concurrency group (concurrencyGroups in pnpm-workspace.yaml) hold the runs of every worktree on the machine to a limit it can carry. A bare cargo or just slips past that limit.

Run pnpm test:rust-affected (just test-affected). It decides three things for you: it selects every pnpr-* crate together, it refuses to scope a change that reaches files every crate compiles against and points at just ready instead, and it runs the smoke profile in place of dependents it did not select. It prints what it selected and what it left out; --help lists its flags.

What it cannot decide is which end-to-end tests exercise your change. Smoke gives breadth across areas, not depth in the one you touched, so for a user-visible change add the suite modules for that area:

sh
pnpm test:rust-affected -- -p pnpm-cli -E 'test(catalog::)'

Each file under crates/cli/tests/suite/ is a module of one test target, so test(<file_stem>::) selects that file's tests.

For anything narrower, pnpm test:rust (node pnpm/scripts/run-rust-tests.mjs) takes the same arguments cargo nextest run does — -p <crate> for one crate, -E 'test(<name>)' for one test. Prefer -p over a package() filterset: -p restricts what cargo builds, a filterset only selects among binaries that were built anyway.

Show full SKILL.md (308 more words)Show less
Gotchas that make a scoped run lie
  • Run the CLI's tests through pnpm test:rust, not bare cargo nextest. It strips npm_config_* and pnpm_config_* and points XDG_CONFIG_HOME and the auth npmrc at a throwaway directory, as just test does. A bare run lets your own npmrc reach the tests, which fails for you and nobody else.
  • pnpr-* crates must be selected together. Cargo unifies features across the selection, so a lone pnpr-* crate builds without pnpr's default backend features and its backend tests skip silently. just test-pnpr selects the whole set.
  • Snapshots. insta snapshots change only for a reason. Read the diff, then cargo insta review. Never accept blindly.
  • Killed runs leak fixtures. An interrupted run abandons temp trees, each holding a per-test store. just sweep-test-temp clears the ones older than an hour.
  • known_failures modules hold ported tests for unimplemented behavior; just known-failures lists them. A failure there is expected, a pass is not.

Do not reach for nextest's rdeps() to widen a selection. pnpm-cli holds a third of the workspace's tests and sits downstream of nearly every crate, so rdeps() on anything core selects 84% or more of the suite. Restructuring that target is pnpm/pnpm#14984.

TypeScript (pnpm11/)

sh
pnpm --filter <package_name> test                                 # one package
pnpm --filter <package_name> test <file_path>                     # one file
pnpm --filter <package_name> test <file_path> -t <name_pattern>   # one case

The end-to-end tests in pnpm11/pnpm/test/ run the bundled pnpm11/pnpm/dist/pnpm.mjs, not each package's lib/. After changing any TypeScript package, rebuild the bundle before running them:

sh
pnpm --filter pnpm run compile

Skip that and the run tests the previous bundle, passing without ever touching your change.

Both stacks

A bug present in both pnpm v11 and v12 is fixed in both, so it is tested in both. Run the TypeScript test for the scenario and the Rust test for the same scenario before calling the fix done.

Reporting

Name what you ran. "Ran pnpm-lockfile plus the catalog e2e module; did not run the full workspace suite" is an honest report. "Tests pass" after a single-crate run is not.

© 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/testing-changes of pnpm/pnpm.

Open the folder on GitHubat commit 142365b

Compare with similar skills

Testing Changes 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.

Testing Changes compared with similar skills
SkillStarsUsed inTokensAuto-checkLicenceRepo updated
Testing Changes this skillpnpm/pnpm37k—~1.1kAutomated safety check: PassMIT
Link Workspace Packagesnomcopter/react-mosaic4.8k6 repos~760Automated safety check: PassCustom licence
Pnpm Engineteambit/bit18k—~1.9kAutomated safety check: PassCustom licence
Linea Dependency MaintenanceConsensys-Incorporated/linea-attestation-registry1771 repos~3.7kAutomated safety check: WarnMIT
Releaseseasonedcc/remix-forms514—~1.3kAutomated safety check: PassMIT
TS SDK Authormindfold-ai/Trellis15k—~6.1kAutomated safety check: PassMIT

Similar skills

  • Link Workspace Packages

    nomcopter/react-mosaic

    Link workspace packages in monorepos (npm, yarn, pnpm, bun).

    4.8k GitHub starsUsed in 6 repos~760 tokens
    DevelopmentAuto-check passed

  • Pnpm Engine

    teambit/bit

    Work on the pnpm Rust engine (@pnpm/napi, the pacquet crates) that bit install runs through.

    18k GitHub stars~1.9k tokensUpdated today
    DevelopmentAuto-check passed

  • Linea Dependency Maintenance

    Consensys-Incorporated/linea-attestation-registry

    Safely plan and execute dependency maintenance for JavaScript/TypeScript (npm, pnpm) and GitHub Actions, including npm lockfiles, pnpm workspaces, catalogs, overrides, SHA-pinned action versions…

    177 GitHub starsUsed in 1 repo~3.7k tokens
    DevelopmentAuto-check: warnings

  • Release

    seasonedcc/remix-forms

    Release a new version of the remix-forms npm package. An agent skill from seasonedcc/remix-forms.

    514 GitHub stars~1.3k tokensUpdated 5 mo ago
    DevelopmentAuto-check passed

  • TS SDK Author

    mindfold-ai/Trellis

    Design, build, verify, and publish production-grade TypeScript SDKs as npm packages inside a pnpm monorepo.

    15k GitHub stars~6.1k tokensUpdated 9 days ago
    DevelopmentAuto-check passed

  • Prepare Rslint npm Release

    web-infra-dev/rslint

    Prepare a stable release PR for the unified rslint npm packages by updating package versions and rule/TypeScript release metadata.

    460 GitHub stars~1.5k tokensUpdated today
    DevelopmentAuto-check passed

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.

    37k GitHub stars~2.2k tokensUpdated today
    Auto-check passed

  • 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.

    37k GitHub stars~2.8k tokensUpdated today
    Auto-check passed

  • 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.

    37k GitHub stars~648 tokensUpdated today
    Auto-check passed

  • Implement Change

    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.

    37k GitHub stars~1.1k tokensUpdated today
    Auto-check passed

  • 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.

    37k GitHub stars~796 tokensUpdated today
    Auto-check passed

  • 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.

    37k GitHub stars~2.9k tokensUpdated today
    Auto-check passed

Works with

Categories

Questions about Testing Changes

What does Testing Changes do?

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…. Testing Changes is an agent skill from 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 anything.

When should I use Testing Changes?

Testing Changes fits situations like: verifying a change before committing; deciding what to run after an edit.

How do I install Testing Changes in Claude Code?

Run `npx skills add pnpm/pnpm --skill testing-changes -a claude-code`. Or copy the skill folder (.agents/skills/testing-changes in pnpm/pnpm) into .claude/skills/testing-changes in your project. Claude Code loads it when a task matches its description.

How do I install Testing Changes in Codex?

Run `npx skills add pnpm/pnpm --skill testing-changes -a codex`. Or copy the skill folder (.agents/skills/testing-changes in pnpm/pnpm) into .agents/skills/testing-changes in your project. Codex loads it when a task matches its description.

Can I use Testing Changes 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 testing-changes -a cursor` (or -a gemini-cli, github-copilot or opencode for the others). To copy it by hand, put the folder in .cursor/skills/testing-changes, .gemini/skills/testing-changes, .github/skills/testing-changes and .opencode/skills/testing-changes in your project.

What does Testing Changes need to run?

Going by SKILL.md and its folder, Testing Changes needs the command-line tools its instructions call (pnpm, just, cargo and node).

Does Testing Changes 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 Testing Changes 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 Testing Changes use?

Testing Changes 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 Testing Changes use?

About 1.1k tokens (SKILL.md is roughly 4.6k 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 Testing Changes?

Skills that share tags, products or a category with Testing Changes: Link Workspace Packages (nomcopter/react-mosaic, 4.8k stars), Pnpm Engine (teambit/bit, 18k stars), Linea Dependency Maintenance (Consensys-Incorporated/linea-attestation-registry, 177 stars) and Release (seasonedcc/remix-forms, 514 stars). The comparison table on this page puts their stars, adoption, token cost, safety result and licence side by side.

Who maintains Testing Changes?

pnpm (a GitHub organization) maintains it in pnpm/pnpm, which has 36,758 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.