Agent skill

Verify Change

by exelearning in exelearning/exelearning

Choose and run the appropriate eXeLearning checks for a diff, including the final code gates or guidance-only validation.

AGPL-3.0Auto-check passedTesting & QA

Install Verify Change

skills CLI
$ npx skills add exelearning/exelearning --skill verify-change -a claude-code

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

GitHub CLI
$ gh skill install exelearning/exelearning 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/exelearning/exelearning.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
146
Token cost
~676 tokens
SKILL.md length
297 words
Files
1
Skills in repo
17
Repo updated
First seen
Licence
AGPL-3.0

At a glance

Choose and run the appropriate eXeLearning checks for a diff, including the final code gates or guidance-only validation.

  • Testing & QA work in your project
  • SKILL.md covers Focused checks while editing and Final code gates
  • Calls make, bun and git

What it does

Verify Change is an agent skill from exelearning/exelearning. Choose and run the appropriate eXeLearning checks for a diff, including the final code gates or guidance-only validation.

Its SKILL.md is about 680 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 Testing & QA. It works with Vitest. The repository describes itself as: eXeLearning is an AGPL-licensed free/libre tool to create and publish open educational resources. The licence is AGPL-3.0.

When your agent uses it

  • Testing & QA work in your project

Example prompts

  • “/verify-change”

What it can do on your machine

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

    • make
    • bun
    • git

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

  • Network

    No URLs in SKILL.md. Its commands use 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 676 tokens when it runs. Until then it costs about 34 tokens; SKILL.md has 297 words of instructions outside code blocks.

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

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 exelearning/exelearning at commit 319b5d2, republished under its AGPL-3.0 licence (© exelearning). 297 words, ~676 tokens.

Download SKILL.mdSave it as .claude/skills/verify-change/SKILL.md (or your agent's skills folder).
name
verify-change
description
Choose and run the appropriate eXeLearning checks for a diff, including the final code gates or guidance-only validation.

Verify a change

Inspect git status, staged/unstaged changes and the diff against the PR base. Read Makefile, package.json, bunfig.toml, vitest.config.mts and the affected CI workflows before quoting a command. Keep validation isolated from other worktrees' ports, databases and shared temporary directories.

Focused checks while editing

ChangeFirst checkAdditional evidence
src/, backend scripts or Electron JSColocated bun test <spec>Changed success/error paths and cleanup
public/app/, browser libraries/iDevicesbun x vitest run <test.js>Round-trip or DOM behavior; do not run under Bun test
src/db/Query/migration/helper specsEvery supported dialect for dialect-sensitive behavior
src/shared/export/Export/provider/renderer specsZIP contents, manifests, browser and server paths
Yjs/WebSocketServer Bun + client Vitest specsSeparate-user collaboration fixture, late join/reconnect
Static/embedding/previewCapabilities/bridge/preview testsStatic E2E and host save/load flow
Workflowsactionlint on changed YAMLTriggers, token permissions, untrusted-input handling
Architecture docsmake architecture-checkTracking IDs and links; no generated index
Agent guidance onlyFrontmatter, relative links, diff -r .agents/skills .claude/skills (no symlinks)Referenced paths/commands, archive exclusions, upstream provenance

Final code gates

The mandatory gates are the Definition of Done in AGENTS.md. A focused test passing does not replace them. Use Firefox as well for browser-specific changes, and follow the existing TypeScript iDevice's Vitest harness rather than switching runners. Inspect the actual coverage reports/Codecov patch result, not just an aggregate percentage. make test-unit covers Bun only; make test-frontend runs Vitest and make test-coverage runs both.

For documentation/skill-only changes, executable-line coverage and application E2E are not applicable. Validate instructions against actual source and commands instead. Changed workflow/package logic still needs its syntax/behavior check. Never run make package merely to validate guidance: it changes versions and can publish depending on its arguments/environment.

Report required checks with pass/fail/not-run and reasons. Separate environment failures from product failures using evidence; fix relevant failures without weakening gates or changing unrelated dependencies.

© exelearning, AGPL-3.0. 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/verify-change of exelearning/exelearning.

Open the folder on GitHubat commit 319b5d2

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 skillexelearning/exelearning146—~676Automated safety check: PassAGPL-3.0
Test Writing WorkflowiOfficeAI/AionUi33k1 repos~1.2kAutomated safety check: PassApache-2.0
Vitestsupabase/supabase111k12 repos~1.1kAutomated safety check: PassApache-2.0
Test GuardamElnagdy/guard-skills1.3k2 repos~2.1kAutomated safety check: PassMIT
Control UI E2Eopenclaw/openclaw392k—~2.9kAutomated safety check: PassMIT
Adding LLM MCP ToolsTriliumNext/Trilium38k—~2.5kAutomated safety check: PassAGPL-3.0

Similar skills

  • Test Writing Workflow

    iOfficeAI/AionUi

    Sets the test-writing workflow for the repository: risk-first scenario lists, behavior-focused Vitest tests, a full run before each commit and a coverage target.

    33k GitHub starsUsed in 1 repo~1.2k tokens
    Testing & QAAuto-check passed
  • Vitest

    supabase/supabase

    Official

    Vitest API and config reference (Jest-compatible) — mocking with vi., spies, fake timers, coverage configuration, fixtures, snapshots, and test filtering.

    111k GitHub starsUsed in 12 repos~1.1k tokens
    Testing & QAAuto-check passed
  • Test Guard

    amElnagdy/guard-skills

    Reviews newly written or edited tests against nine rules that cut test bloat, such as mock-heavy checks and near-duplicate cases, before they are committed.

    1.3k GitHub starsUsed in 2 repos~2.1k tokens
    Testing & QAAuto-check passed
  • Control UI E2E

    openclaw/openclaw

    A skill your agent uses when designing, testing, fixing, or extending the OpenClaw Control UI GUI, including UI stress-test galleries with feedback inputs, Vitest + Playwright end-to-end checks…

    392k GitHub stars~2.9k tokensUpdated today
    Testing & QAAuto-check passed
  • Adding LLM MCP Tools

    TriliumNext/Trilium

    A skill your agent uses when adding, changing, or reviewing an LLM/MCP tool in Trilium (the defineTools definitions under packages/trilium-core/src/services/llm/tools/ —…

    38k GitHub stars~2.5k tokensUpdated today
    Testing & QAAuto-check passed
  • Concept Page Test Writer

    leonardomso/33-js-concepts

    Generates Vitest tests for every runnable code example on a JavaScript concept documentation page, following a four-phase extraction and conversion process.

    67k GitHub stars~5.5k tokensUpdated 27 days ago
    Testing & QAAuto-check passed

More from exelearning/exelearning

All 17 skills in this repo
  • E2E Test

    exelearning/exelearning

    Write or debug repository Playwright specs, including isolated projects, preview frames and multi-user fixtures.

    146 GitHub stars~1.1k tokensUpdated yesterday
    Auto-check passed
  • Frontend Module

    exelearning/exelearning

    Change vanilla JavaScript UI modules in public/app/, including DOM state, events and localization.

    146 GitHub stars~867 tokensUpdated yesterday
    Auto-check passed
  • I18n

    exelearning/exelearning

    Add or change source-level localized strings using (), c() or the Nunjucks trans filter; not catalog extraction.

    146 GitHub stars~812 tokensUpdated yesterday
    Auto-check passed
  • Idevice

    exelearning/exelearning

    Create or modify an eXeLearning iDevice, including edition/export data, legacy compatibility, assets, TypeScript bundles and teardown.

    146 GitHub stars~1.7k tokensUpdated yesterday
    Auto-check passed
  • Websocket Yjs

    exelearning/exelearning

    Change eXeLearning shared document mutations, WebSocket rooms, snapshots, reconnects or concurrent editing behavior.

    146 GitHub stars~759 tokensUpdated yesterday
    Auto-check passed
  • API V1

    exelearning/exelearning

    Add or change external REST API v1 endpoints and their documented authentication/authorization contracts.

    146 GitHub stars~427 tokensUpdated yesterday
    Auto-check passed

Works with

Categories

Questions about Verify Change

What does Verify Change do?

Choose and run the appropriate eXeLearning checks for a diff, including the final code gates or guidance-only validation. Verify Change is an agent skill from exelearning/exelearning. Choose and run the appropriate eXeLearning checks for a diff, including the final code gates or guidance-only validation.

When should I use Verify Change?

Verify Change fits situations like: testing & QA work in your project.

How do I install Verify Change in Claude Code?

Run `npx skills add exelearning/exelearning --skill verify-change -a claude-code`. Or copy the skill folder (.agents/skills/verify-change in exelearning/exelearning) 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 exelearning/exelearning --skill verify-change -a codex`. Or copy the skill folder (.agents/skills/verify-change in exelearning/exelearning) 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 exelearning/exelearning --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 (make, bun and git).

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 AGPL-3.0 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 676 tokens (SKILL.md is roughly 2.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: Test Writing Workflow (iOfficeAI/AionUi, 33k stars), Vitest (supabase/supabase, 111k stars), Test Guard (amElnagdy/guard-skills, 1.3k stars) and Control UI E2E (openclaw/openclaw, 392k stars). The comparison table on this page puts their stars, adoption, token cost, safety result and licence side by side.

Who maintains Verify Change?

exelearning (a GitHub organization) maintains it in exelearning/exelearning, which has 146 GitHub stars. The repository holds 17 skills in this directory. The repository was last updated on October 7, 2026.

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