New: 97,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

Verdaccio Change Testing Selector

by verdaccio in verdaccio/verdaccio

Figures out which rebuild and test suites actually cover a change in the verdaccio monorepo, instead of a scoped run that passes untested.

MITAuto-check: warningsTesting & QA

Install Verdaccio Change Testing Selector

The automated check flagged lines worth reading first. See the safety section below.

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

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

GitHub CLI
$ gh skill install verdaccio/verdaccio 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/verdaccio/verdaccio.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
18k
Token cost
~1.6k tokens
SKILL.md length
619 words
Files
1
Skills in repo
8
Repo updated
First seen
Licence
MIT

At a glance

Figures out which rebuild and test suites actually cover a change in the verdaccio monorepo, instead of a scoped run that passes untested.

  • Deciding what to run after editing a verdaccio package
  • SKILL.md covers The one rule: rebuild before…, Selecting the run, End-to-end and Gotchas that make a run lie, plus 1 more section
  • Calls pnpm, git and node
  • Verifying a change before committing or pushing

What it does

Because packages import each other through their build output rather than src, this skill insists on rebuilding every touched package and its dependents with a filtered pnpm build before testing; otherwise a test runs against a stale build and passes without ever exercising the change.

It maps a diff to the suites that actually prove it: package tests, the dependents' tests, the API integration suite, the e2e CLI battery, or the Cypress UI suite for a client- or UI-visible change. It always goes through each package's own test script rather than bare vitest, since some packages set required environment variables, and it flags when a docs-only or agent-config-only PR never triggers CI at all so a green check isn't mistaken for one that ran.

When your agent uses it

  • Deciding what to run after editing a verdaccio package
  • Verifying a change before committing or pushing
  • Checking why a scoped test run passed without covering a change

Example prompts

  • “What should I run after editing packages/store?”
  • “Verify my change to the api package before I push.”
  • “Did this docs-only PR actually trigger CI?”

Requirements

  • pnpm

What it can do on your machine

Read from SKILL.md and the folder at commit 2d3bcca. 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
    • git
    • 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 and git, 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

Verdaccio Change Testing Selector loads about 1.6k tokens when it runs. Until then it costs about 117 tokens; SKILL.md has 619 words of instructions outside code blocks.

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

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: warnings

The automated check found patterns that need a careful read before installing.

  • WarningMentions a credentials file (SSH keys, cloud or package-manager tokens)SKILL.md:97
    s on your machine usually comes from `~/.npmrc` or the global pnpm config.

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 verdaccio/verdaccio at commit 2d3bcca, republished under its MIT licence (© verdaccio). 619 words, ~1,605 tokens.

Download SKILL.mdSave it as .claude/skills/testing-changes/SKILL.md (or your agent's skills folder).
name
testing-changes
description
Select and run the checks that actually cover a change in the verdaccio monorepo — rebuild the touched packages, run their tests and their dependents' tests, the api integration suite, the e2e CLI battery or the Cypress UI suite when the change is client- or UI-visible — and recognise 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 pipeline (lint, format, build, tests on Node.js 24 and 26, Docker build, the e2e CLI matrix, Cypress) on a ready PR whose diff matches ci.yml's paths: filter — packages/**, tests/**, docker-examples/**, package.json, pnpm-workspace.yaml, vite.lib.config.mjs, .changeset/**, or the workflow file itself. A docs-only or .agents//.claude/-only PR does not trigger CI at all; don't cite a green check that never ran. The local job is fast, honest feedback either way, not a second full gate. What matters is that the run you choose exercises the code you changed.

The one rule: rebuild before you test

Packages import each other through build/ (exports in every package.json), not src. A test in packages/api that imports @verdaccio/store runs against packages/store/build/. After editing store, an api run that skips the rebuild tests the old build and passes without touching your change.

bash
pnpm build                                      # everything, once per checkout
pnpm --filter @verdaccio/store build            # the package you edited
pnpm --filter "@verdaccio/store..." build       # it plus what it depends on

Selecting the run

Find the packages the diff touches, then test them and their dependents:

bash
git diff --name-only origin/master...HEAD | cut -d/ -f1-3 | sort -u

pnpm --filter "[origin/master]" build           # packages changed since master
pnpm --filter "...[origin/master]" test         # those packages and everything that depends on them

Narrower runs, once the touched packages are rebuilt:

bash
pnpm --filter @verdaccio/store test                                # one package
pnpm --filter @verdaccio/store test test/versions.spec.ts          # one file
pnpm --filter @verdaccio/store test test/versions.spec.ts -t 'tag' # one case
pnpm --filter @verdaccio/store test -- --coverage=false            # faster

Always go through the package's test script, not bare vitest: some packages set environment the tests rely on (TZ=utc for logger, ui-theme, ui-components; NODE_ENV=test for memory; a longer timeout for store).

Map the change to the suites that prove it:

Change touchesRun
A helper in core, config, url, tarball, ...That package, then pnpm --filter "...@verdaccio/<pkg>" test for the dependents
A route in packages/api or packages/web@verdaccio/api integration tests (test/integration, supertest against initializeServer)
store, local-storage, proxy (packument, tarball)Those packages, @verdaccio/api, then the e2e CLI battery for the affected client flow
auth, htpasswd, auth-memory, tokens, 2FAThose packages, @verdaccio/api (login, token, tfa, profile specs), e2e for login/publish
config, cli, node-api, verdaccioThose packages, then start the server (pnpm start or node packages/verdaccio/bin/verdaccio)
UI (ui-theme, ui-components, web)@verdaccio/ui-components, @verdaccio/ui-theme, then pnpm e2e:ui:local
Anything a package manager observes./scripts/e2e-cli-local.sh <pm> for each client the change can affect
Plugin interfaces in @verdaccio/typespnpm type-check across the workspace, the bundled plugins' tests

Always finish with pnpm lint and pnpm format:check; the pre-commit hook enforces them on staged files, CI on everything.

Show full SKILL.md (273 more words)Show less

End-to-end

The CLI battery is @verdaccio/e2e-cli (repository verdaccio/e2e-tests). Locally:

bash
pnpm build
./scripts/e2e-cli-local.sh npm@11       # also npm@10, npm@12, pnpm@10, pnpm@11, yarn-classic, yarn-modern@4, bun, deno

It starts a fresh registry on port 4873, runs the client scenarios, and cleans up. CI runs the whole matrix; run at least the client the reporter used and npm@11 when a change touches publish, install, tarballs, dist-tags, search, or auth.

The UI battery is Cypress: pnpm e2e:ui:local (headless) or pnpm e2e:ui:local:open. Docker-based flows (pnpm docker, e2e/docker) need a running Docker daemon.

Gotchas that make a run lie

  • Stale build (above). If a test passes when you expected a failure, rebuild the package you changed and run again.
  • Network is blocked. vitest.setup.mjs disallows every host except localhost via nock. Nock: Disallowed net connect means the code under test reached the network; mock the uplink, do not widen the allow-list.
  • A port left behind. A killed e2e run can leave a registry on port 4873 (check with lsof -i :4873), and the next run then tests the wrong process.
  • Global package-manager settings. A user-level minimumReleaseAge or registry override changes what pnpm install and the e2e clients do; a failure that only happens on your machine usually comes from ~/.npmrc or the global pnpm config.
  • fail-fast in CI. A test job failing on Node.js 26 cancels the Node.js 24 job; read the failed log, not the cancelled one.
  • Disabled tests. Files named *.__disabled__.ts and disabled_test/ folders are not run; a pass there proves nothing.

Reporting

Name what you ran and what you did not. "Rebuilt store, ran store and api integration tests plus the e2e battery with npm@11; did not run the UI suite" is an honest report. "Tests pass" after one package's run is not.

© verdaccio, 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 verdaccio/verdaccio.

Open the folder on GitHubat commit 2d3bcca

Compare with similar skills

Verdaccio Change Testing Selector 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.

Verdaccio Change Testing Selector compared with similar skills
SkillStarsUsed inTokensAuto-checkLicenceRepo updated
Verdaccio Change Testing Selector this skillverdaccio/verdaccio18k—~1.6kAutomated safety check: WarnMIT
DeerFlow Smoke Testbytedance/deer-flow83k—~2.5kAutomated safety check: NotesMIT
Testingweb-infra-dev/rstest505—~2.1kAutomated safety check: PassMIT
Pnpmmoeru-ai/airi50k2 repos~1kAutomated safety check: WarnMIT
PnpmJetBrains/skills3636 repos~742Automated safety check: WarnNone
MongoDB Source Connector E2E Harnessairbytehq/airbyte22k—~1.9kAutomated safety check: PassCustom licence

Similar skills

  • DeerFlow Smoke Test

    bytedance/deer-flow

    Walks through an end-to-end smoke test of a DeerFlow deployment: pull the latest code, deploy with Docker or locally, verify services, run health checks and write a report.

    83k GitHub stars~2.5k tokensUpdated today
    Testing & QAAuto-check: notes

  • Testing

    web-infra-dev/rstest

    Testing workflow for the Rstest monorepo. An agent skill from web-infra-dev/rstest.

    505 GitHub stars~2.1k tokensUpdated 7 days ago
    Testing & QAAuto-check passed

  • Pnpm

    moeru-ai/airi

    Node.js package manager with strict dependency resolution. An agent skill from moeru-ai/airi.

    50k GitHub starsUsed in 2 repos~1k tokens
    DevelopmentAuto-check: warnings

  • Pnpm

    JetBrains/skills

    Official

    Node.js package manager with strict dependency resolution. An agent skill from JetBrains/skills.

    363 GitHub starsUsed in 6 repos~742 tokens
    DevelopmentAuto-check: warnings

  • MongoDB Source Connector E2E Harness

    airbytehq/airbyte

    Official

    Starts a throwaway MongoDB 7.0 replica set and runs the Airbyte spec, check, discover and read commands against source-mongodb-v2 images for local end-to-end testing.

    22k GitHub stars~1.9k tokensUpdated today
    Testing & QAAuto-check passed

  • source-mssql E2E Test Harness

    airbytehq/airbyte

    Official

    Stands up a throwaway local SQL Server 2022 backend, applies SQL fixtures and runs Airbyte spec, check, discover and read against source-mssql images.

    22k GitHub stars~4.4k tokensUpdated today
    Testing & QAAuto-check passed

More from verdaccio/verdaccio

All 8 skills in this repo

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

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

  • Verdaccio PR Review

    verdaccio/verdaccio

    Reviews an existing verdaccio/verdaccio pull request end to end, verifies each finding and reports whether it is mergeable, optionally fixing it on the PR branch.

    18k GitHub stars~1.7k tokensUpdated today
    Auto-check passed

  • Verdaccio Issue Triage

    verdaccio/verdaccio

    Triages an incoming verdaccio/verdaccio issue against the code, the affected release line and related issues, and picks labels from the repository's existing taxonomy.

    18k GitHub stars~2.4k tokensUpdated today
    Auto-check passed

  • Verdaccio Code Review

    verdaccio/verdaccio

    Reviews a verdaccio diff, branch or PR against the repository's review guide, verifies each finding in the code and reports only actionable issues.

    18k GitHub stars~853 tokensUpdated today
    Auto-check passed

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

    18k GitHub stars~1.3k tokensUpdated today
    Auto-check passed

  • Verdaccio Plugin Maintenance

    verdaccio/verdaccio

    Maintains Verdaccio's bundled plugins and the plugin contracts in @verdaccio/core, and diagnoses plugin loading problems.

    18k GitHub stars~3k tokensUpdated today
    Auto-check passed

Works with

Categories

Questions about Verdaccio Change Testing Selector

What does Verdaccio Change Testing Selector do?

Figures out which rebuild and test suites actually cover a change in the verdaccio monorepo, instead of a scoped run that passes untested. Because packages import each other through their build output rather than src, this skill insists on rebuilding every touched package and its dependents with a filtered pnpm build before testing; otherwise a test runs against a stale build and passes without ever exercising the change.

When should I use Verdaccio Change Testing Selector?

Verdaccio Change Testing Selector fits situations like: deciding what to run after editing a verdaccio package; verifying a change before committing or pushing; checking why a scoped test run passed without covering a change.

How do I install Verdaccio Change Testing Selector in Claude Code?

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

How do I install Verdaccio Change Testing Selector in Codex?

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

Can I use Verdaccio Change Testing Selector 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 verdaccio/verdaccio --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 Verdaccio Change Testing Selector need to run?

Going by SKILL.md and its folder, Verdaccio Change Testing Selector needs the command-line tools its instructions call (pnpm, git and node). Our summary lists: pnpm.

Does Verdaccio Change Testing Selector access the network?

SKILL.md contains no URLs. Its commands use git, which can reach the network depending on how they are called. This is read from the text; nothing was executed.

Is Verdaccio Change Testing Selector safe to install?

Our automated static check of SKILL.md flagged 1 warning(s): mentions a credentials file (ssh keys, cloud or package-manager tokens). Read the flagged lines before installing; the check is not a guarantee either way.

What licence does Verdaccio Change Testing Selector use?

Verdaccio Change Testing Selector 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 Verdaccio Change Testing Selector use?

About 1.6k tokens (SKILL.md is roughly 6.4k 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 Verdaccio Change Testing Selector?

Skills that share tags, products or a category with Verdaccio Change Testing Selector: DeerFlow Smoke Test (bytedance/deer-flow, 83k stars), Testing (web-infra-dev/rstest, 505 stars), Pnpm (moeru-ai/airi, 50k stars) and Pnpm (JetBrains/skills, 363 stars). The comparison table on this page puts their stars, adoption, token cost, safety result and licence side by side.

Who maintains Verdaccio Change Testing Selector?

verdaccio (a GitHub organization) maintains it in verdaccio/verdaccio, which has 17,913 GitHub stars. The repository holds 8 skills in this directory. The repository was last updated on October 6, 2026.

Source: verdaccio/verdaccio on GitHub. Facts on this page come from the repository at the commit we read; the author's words are quoted as theirs.