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

Verify Change

by druxt in druxt/druxt.js

Runs the druxt.js verification gate (lint, build, unit tests and the checks for whatever else changed) and reports the real results.

MITAuto-check passedDevelopment

Install Verify Change

skills CLI
$ npx skills add druxt/druxt.js --skill verify-change -a claude-code

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

GitHub CLI
$ gh skill install druxt/druxt.js verify-change --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/druxt/druxt.js.git skills-src && mkdir -p .claude/skills && cp -r skills-src/.agents/skills/verify-change .claude/skills/verify-change && 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
verify-change
GitHub stars
114
Token cost
~916 tokens
SKILL.md length
408 words
Files
2
Skills in repo
7
Repo updated
First seen
Licence
MIT

At a glance

Runs the druxt.js verification gate (lint, build, unit tests and the checks for whatever else changed) and reports the real results.

  • A druxt.js lint
  • SKILL.md covers The gate, Checks for what changed, Failing checks and Commits, plus 1 more section
  • Calls yarn, git and make
  • Test check fails

What it does

Verify Change is an agent skill from druxt/druxt.js. Runs the druxt.js verification gate (lint, build, unit tests and the checks for whatever else changed) and reports the real results. Use when a druxt.js lint, build or test check fails or when asked what to check after a change. Also use it before a commit, before opening or updating a pull request, and before saying a change is done. For a failing skill check, use write-skill.

Its SKILL.md is about 920 tokens, which your agent loads only when the skill is triggered. The skill folder holds 2 other files (for example `evals/tests.yaml`).

It sits in Development, covering Linting and formatting, Unit testing and Pull requests. The repository describes itself as: The Fully Decoupled Drupal Framework. The licence is MIT.

When your agent uses it

  • A druxt.js lint
  • Test check fails
  • Asked what to check after a change

Example prompts

  • “/verify-change”

What it can do on your machine

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

    • yarn
    • git
    • make

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

  • Network

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

Verify Change loads about 916 tokens when it runs. Until then it costs about 99 tokens; SKILL.md has 408 words of instructions outside code blocks.

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

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 druxt/druxt.js at commit a225990, republished under its MIT licence (© druxt). 408 words, ~916 tokens.

Download SKILL.mdSave it as .claude/skills/verify-change/SKILL.md (or your agent's skills folder). This skill also uses 1 other file; get the full folder from GitHub.
name
verify-change
description
Runs the druxt.js verification gate (lint, build, unit tests and the checks for whatever else changed) and reports the real results. Use when a druxt.js lint, build or test check fails or when asked what to check after a change. Also use it before a commit, before opening or updating a pull request, and before saying a change is done. For a failing skill check, use write-skill.

Verify a change

A change is done when the checks CI runs have passed on your machine, in this session, and you can show the output. A check you have not run has not passed.

The gate

Run it from the repository root, in this order, for every change:

bash
yarn lint && yarn build && yarn test:unit

yarn build must produce dist/ output for every package. CI builds before it runs the unit tests, so do the same.

Checks for what changed

What changedAlso run
Any Markdown, including changesetsyarn lint:md, yarn lint:prose, yarn lint:cspell
Source comments or JSDocyarn lint:prose, yarn lint:cspell
package.json or yarn.lockyarn install --immutable, yarn lint:knip, yarn lint:audit
renovate.jsonyarn lint:renovate
examples/ manifestsyarn lint:examples
Package output sizeyarn bundlewatch, after yarn build
.agents/skills/ or AGENTS.mdyarn lint:skills
scripts/releaseyarn release:check:test
scripts/perf-audityarn perf:audit:test under Node 22

The end-to-end tests run in CI against a Drupal backend. To run them locally, start the backend with (cd examples/drupal && make build), then run yarn example:druxt-site:test from the repository root. See examples/drupal/.devtools/README.md.

Failing checks

  • Fix the cause. Leave the check, its configuration and its threshold as they are.
  • When a test fails because behaviour changed, fix the code, not the test. Change an assertion only for a change that is meant to happen, and confirm that first: read the whole commit message, and ask its author when the change isn't yours.
  • Leave uncommitted work you didn't make in place. Ask before running git restore, git checkout -- . or git clean on it, and wait for the answer.
  • Never skip the git hooks, delete or skip a test, or add an eslint-disable comment to get a check to pass.
  • If a check is wrong, fix the check in a separate commit and say why in the pull request.
  • If it also fails on a clean develop, it is not your change's failure. Say so, with the output from both runs.
Show full SKILL.md (95 more words)Show less

Commits

The pre-commit, commit-msg and pre-push hooks run a subset of these checks. Let them run. Commit under the git identity of the person you work for. Leave AI attribution out of the message, such as a Co-Authored-By: Claude trailer or a session link. yarn lint:commit --from upstream/develop --to HEAD checks the messages on the branch.

Report

State each command and its result, with the failing output when there is any. Write "the gate passed" only after it has passed in this session. When you could not run a check, name it and say why.

© druxt, 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/verify-change of druxt/druxt.js.

  • SKILL.md
  • evals/tests.yaml

Open the folder on GitHubat commit a225990

Compare with similar skills

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

Verify Change compared with similar skills
SkillStarsUsed inTokensAuto-checkLicenceRepo updated
Verify Change this skilldruxt/druxt.js114—~916Automated safety check: PassMIT
Adk Setupgoogle/adk-python22k—~993Automated safety check: NotesApache-2.0
Testing Blocksadobe/skills196—~2.4kAutomated safety check: PassApache-2.0
Kedro Babysitkedro-org/kedro11k—~4kAutomated safety check: PassCustom licence
WooCommerce Dev Cyclewoocommerce/woocommerce11k3 repos~431Automated safety check: PassCustom licence
Dep Validateblokadaorg/blokada3.3k—~5.7kAutomated safety check: NotesMPL-2.0

Similar skills

  • Adk Setup

    google/adk-python

    Official

    Sets up a local ADK Python development environment in a git clone of the open-source adk-python repository: a uv virtual environment, all dependency extras, pre-commit hooks, and a first unit-test…

    22k GitHub stars~993 tokensUpdated today
    DevelopmentAuto-check: notes

  • Testing Blocks

    adobe/skills

    Use this when you have made AEM Edge Delivery Services code changes to blocks, scripts, or styles and need to validate them before opening a pull request.

    196 GitHub stars~2.4k tokensUpdated yesterday
    DevelopmentAuto-check passed

  • Kedro Babysit

    kedro-org/kedro

    Run Kedro's local lint / format / type-check / tests on changed files (uses the project's pre-commit hooks, ruff, mypy, pytest, lint-imports, detect-secrets, Make targets — in the right venv), or…

    11k GitHub stars~4k tokensUpdated yesterday
    DevelopmentAuto-check passed

  • WooCommerce Dev Cycle

    woocommerce/woocommerce

    Workflow for WooCommerce development: run PHP and JavaScript tests, lint and fix code style on the current branch, and follow guides for i18n and markdown.

    11k GitHub starsUsed in 3 repos~431 tokens
    DevelopmentAuto-check passed

  • Dep Validate

    blokadaorg/blokada

    A skill your agent uses to validate risky dependency bumps end to end as a local or cloud-launched agent.

    3.3k GitHub stars~5.7k tokensUpdated yesterday
    DevelopmentAuto-check: notes

  • Implementing Lint Rules

    flint-fyi/flint

    Implements ESLint-style lint rules with proper AST handling, targeted reporting, and comprehensive unit tests.

    312 GitHub stars~857 tokensUpdated today
    DevelopmentAuto-check passed

More from druxt/druxt.js

  • Add Changeset

    druxt/druxt.js

    Writes the changeset that versions a druxt.js package change and becomes its changelog entry.

    114 GitHub stars~763 tokensUpdated today
    Auto-check passed

  • Address Review

    druxt/druxt.js

    Works through review comments and failing CI on a druxt.js pull request, fixing or answering each one until the pull request is green and every thread has a reply.

    114 GitHub stars~600 tokensUpdated today
    Auto-check passed

  • Open PR

    druxt/druxt.js

    Prepares and opens a druxt.js pull request from a contributor's fork against develop, with a Conventional Commits title and the repository's template filled in.

    114 GitHub stars~771 tokensUpdated today
    Auto-check passed

  • Start Work

    druxt/druxt.js

    Sets up a druxt.js change before the first edit, from the issue to a feature branch off develop, a short spec and a failing test.

    114 GitHub stars~887 tokensUpdated today
    Auto-check passed

  • Triage Issue

    druxt/druxt.js

    Sorts a druxt.js issue by type and package, and reproduces it against the example Drupal backend or with a failing unit test before writing up the findings.

    114 GitHub stars~763 tokensUpdated today
    Auto-check passed

  • Write Skill

    druxt/druxt.js

    Creates or changes a druxt.js contributor skill in .agents/skills, with its evals and the tests that gate it.

    114 GitHub stars~926 tokensUpdated today
    Auto-check passed

Categories

Questions about Verify Change

What does Verify Change do?

Runs the druxt.js verification gate (lint, build, unit tests and the checks for whatever else changed) and reports the real results. js.js verification gate (lint, build, unit tests and the checks for whatever else changed) and reports the real results.

When should I use Verify Change?

Verify Change fits situations like: A druxt.js lint; test check fails; asked what to check after a change.

How do I install Verify Change in Claude Code?

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

How do I install Verify Change in Codex?

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

Can I use Verify 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 druxt/druxt.js --skill verify-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/verify-change, .gemini/skills/verify-change, .github/skills/verify-change and .opencode/skills/verify-change in your project.

What does Verify Change need to run?

Going by SKILL.md and its folder, Verify Change needs the command-line tools its instructions call (yarn, git and make).

Does Verify Change 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 Verify 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 Verify Change use?

Verify 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 Verify Change use?

About 916 tokens (SKILL.md is roughly 3.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 Verify Change?

Skills that share tags, products or a category with Verify Change: Adk Setup (google/adk-python, 22k stars), Testing Blocks (adobe/skills, 196 stars), Kedro Babysit (kedro-org/kedro, 11k stars) and WooCommerce Dev Cycle (woocommerce/woocommerce, 11k stars). The comparison table on this page puts their stars, adoption, token cost, safety result and licence side by side.

Who maintains Verify Change?

druxt (a GitHub organization) maintains it in druxt/druxt.js, which has 114 GitHub stars. The repository holds 7 skills in this directory. The repository was last updated on October 8, 2026.

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