Agent skill

Verify Changes

by 389ds in 389ds/389-ds-base

Verify a 389-ds-base change by routing through the environment's build/test skill — static Python gates plus, via that skill, C compile, cmocka, RPM build and pytest suites, cargo tests, and the…

Custom licenceAuto-check passedTesting & QA

Install Verify Changes

skills CLI
$ npx skills add 389ds/389-ds-base --skill verify-changes -a claude-code

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

GitHub CLI
$ gh skill install 389ds/389-ds-base verify-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/389ds/389-ds-base.git skills-src && mkdir -p .claude/skills && cp -r skills-src/.agents/skills/verify-changes .claude/skills/verify-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
verify-changes
GitHub stars
294
Token cost
~1.9k tokens
SKILL.md length
942 words
Files
2 (incl. references)
Skills in repo
7
Repo updated
First seen
Licence
Custom licence

At a glance

Verify a 389-ds-base change by routing through the environment's build/test skill — static Python gates plus, via that skill, C compile, cmocka, RPM build and pytest suites, cargo tests, and the…

  • Works in 3 steps: Route through the environment's… → Static gates (read-only, safe on any… → Which CI checks cover what you touched
  • Asked to test this change
  • SKILL.md covers 1. Route through the…, 2. Static gates (read-only,…, 3. Which CI checks cover what… and Reference: the CI commands,…, plus 1 more section
  • Calls make, git and npm

What it does

Verify Changes is an agent skill from 389ds/389-ds-base. Verify a 389-ds-base change by routing through the environment's build/test skill — static Python gates plus, via that skill, C compile, cmocka, RPM build and pytest suites, cargo tests, and the Cockpit UI build, picking the right checks for what was touched. Use when asked to test this change, build this, run the tests, run CI locally, or check nothing regressed before a PR. Never configure, build, or run tests directly - developer setups differ (prefixes, containers, VMs) and the server builds and runs only on…

Its SKILL.md is about 1.9k tokens, which your agent loads only when the skill is triggered. The skill folder holds 2 other files, including reference files (for example `references/container-recipe.md`).

It sits in Testing & QA, covering Unit testing. It works with pytest, Linux and Python. The repository describes itself as: The enterprise-class Open Source LDAP server for Linux.

When your agent uses it

  • Asked to test this change
  • Check nothing regressed before a PR

Example prompts

  • “/verify-changes”

Requirements

  • Python 3
  • Node.js
  • Docker

Workflow steps

3 steps, taken from the step headings in SKILL.md.

  1. Route through the environment's build/test skill FIRST
  2. Static gates (read-only, safe on any machine — always run for Python or test changes)
  3. Which CI checks cover what you touched

What it can do on your machine

Read from SKILL.md and the folder at commit cb60126. 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
    • git
    • npm
    • uv
    • python3
    • bash
    • dnf
    • npx

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

  • Network

    No URLs in SKILL.md. Its commands use git, npm, uv and npx, 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 Changes loads about 1.9k tokens when it runs, and up to ~3.6k if it reads all its reference files. Until then it costs about 161 tokens; SKILL.md has 942 words of instructions outside code blocks.

Always · name and description, kept in context so the agent knows when to use it
~161
When it runs · the whole SKILL.md, loaded when a task matches
~1.9k
With references · SKILL.md plus every file in references/, read only if the agent opens them
~3.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 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

Its licence (Custom licence) doesn't allow us to republish the file, so here is its outline and opening line. It has 942 words (~1,876 tokens).

“Look through the available skills for one that builds or tests 389-ds-base in this environment (a container wrapper, VM scripts, a prefix-based setup — names vary per developer).”

— opening of SKILL.md by 389ds, Custom licence
name
verify-changes

Read the full SKILL.md on GitHub

Files

SKILL.md and 1 other file (references) in .agents/skills/verify-changes of 389ds/389-ds-base.

  • SKILL.md
  • references/container-recipe.md

Open the folder on GitHubat commit cb60126

Compare with similar skills

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

Verify Changes compared with similar skills
SkillStarsUsed inTokensAuto-checkLicenceRepo updated
Verify Changes this skill389ds/389-ds-base294—~1.9kAutomated safety check: PassCustom licence
Adk Verify Snippetsgoogle/adk-python22k—~1.4kAutomated safety check: PassApache-2.0
Hermetic Python Unit TestsdimensionalOS/dimos4.6k—~1.4kAutomated safety check: PassCustom licence
ONNX Runtime Test Runnermicrosoft/onnxruntime22k—~1.8kAutomated safety check: PassMIT
Simple Modern Uvjlevy/simple-modern-uv301—~1.9kAutomated safety check: PassMIT
Test Coverage Reviewareed1192/finance-news-aggregator149—~2.6kAutomated safety check: PassMIT

Similar skills

  • Adk Verify Snippets

    google/adk-python

    Official

    Checks that every Python code block in a Markdown file actually compiles and runs, by extracting each block to a temporary file, executing it in an isolated subprocess, and writing a pass/fail…

    22k GitHub stars~1.4k tokensUpdated today
    Testing & QAAuto-check passed
  • Hermetic Python Unit Tests

    dimensionalOS/dimos

    Rules for writing, fixing and reviewing pytest unit tests that are hermetic: behavior-focused, deterministic, isolated and cheap to run.

    4.6k GitHub stars~1.4k tokensUpdated today
    Testing & QAAuto-check passed
  • ONNX Runtime Test Runner

    microsoft/onnxruntime

    Official

    Runs and debugs ONNX Runtime tests: Google Test executables for C++ and unittest or pytest for Python, with filters and build-directory guidance.

    22k GitHub stars~1.8k tokensUpdated today
    Testing & QAAuto-check passed
  • Simple Modern Uv

    jlevy/simple-modern-uv

    Start, selectively modernize, fully migrate, or update Python projects using simple-modern-uv practices: uv, ruff, BasedPyright, pytest, GitHub Actions CI, and tag-driven PyPI publishing.

    301 GitHub stars~1.9k tokensUpdated 1 mo ago
    Testing & QAAuto-check passed
  • Test Coverage Review

    areed1192/finance-news-aggregator

    Audit, plan, write, and verify unit tests for Python projects using pytest.

    149 GitHub stars~2.6k tokensUpdated 5 mo ago
    Testing & QAAuto-check passed
  • Official

    Runs the ONNX Runtime transformers Python tests against a GPU wheel and proves the cuDNN flash attention path was used rather than a silent fallback.

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

More from 389ds/389-ds-base

  • Commit And PR

    389ds/389-ds-base

    Commit and open a PR the 389-ds-base way — "Issue NNNN - summary" subject, Bug Description/Fix Description body, Fixes:/Relates: trailer, AI-attribution trailer, and squash-merge etiquette.

    294 GitHub stars~1k tokensUpdated yesterday
    Auto-check passed
  • Write Test

    389ds/389-ds-base

    Add or extend a pytest integration test for 389 Directory Server under dirsrvtests/.

    294 GitHub stars~1.8k tokensUpdated yesterday
    Auto-check passed
  • Add CLI Option

    389ds/389-ds-base

    Add or change a dsconf/dsctl/dsidm/dscreate flag, subcommand, or noun in src/lib389 — argparse wiring, argtoattr maps, lib389 allowlists, generated man pages, Cockpit coupling, and clu tests.

    294 GitHub stars~1.6k tokensUpdated yesterday
    Auto-check passed
  • Add Config Attribute

    389ds/389-ds-base

    Add, rename, or wire a server config attribute end to end - a core cn=config attribute (the slap.h/libglobs.c chain) or a plugin config-entry attribute - including the schema line, defaults, upgrade…

    294 GitHub stars~1.7k tokensUpdated yesterday
    Auto-check passed
  • Touch Backend

    389ds/389-ds-base

    Rules for modifying back-ldbm database code under the dual-backend (BDB + LMDB) architecture.

    294 GitHub stars~1.3k tokensUpdated yesterday
    Auto-check passed
  • UI Expose Attribute

    389ds/389-ds-base

    Expose a server setting in the Cockpit web console (389-console) or change web UI behavior.

    294 GitHub stars~1.6k tokensUpdated yesterday
    Auto-check passed

Categories

Questions about Verify Changes

What does Verify Changes do?

Verify a 389-ds-base change by routing through the environment's build/test skill — static Python gates plus, via that skill, C compile, cmocka, RPM build and pytest suites, cargo tests, and the…. Verify Changes is an agent skill from 389ds/389-ds-base. Verify a 389-ds-base change by routing through the environment's build/test skill — static Python gates plus, via that skill, C compile, cmocka, RPM build and pytest suites, cargo tests, and the Cockpit UI build, picking the right checks for what was touched.

When should I use Verify Changes?

Verify Changes fits situations like: asked to test this change; check nothing regressed before a PR.

How do I install Verify Changes in Claude Code?

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

How do I install Verify Changes in Codex?

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

Can I use Verify 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 389ds/389-ds-base --skill verify-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/verify-changes, .gemini/skills/verify-changes, .github/skills/verify-changes and .opencode/skills/verify-changes in your project.

What does Verify Changes need to run?

Going by SKILL.md and its folder, Verify Changes needs the command-line tools its instructions call (make, git, npm, uv, python3 and bash). Our summary lists: Python 3; Node.js; Docker.

Does Verify Changes access the network?

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

Is Verify 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 Verify Changes use?

Verify Changes has a licence file (the repository's licence) that doesn't match a standard licence. Read it on GitHub before reusing the skill.

How many tokens does Verify Changes use?

About 1.9k tokens (SKILL.md is roughly 7.5k characters). Agents keep only the skill's name and description in context until a task matches; then they load SKILL.md in full. Its references folder adds about 1.8k tokens, read only when the agent opens those files.

What are the alternatives to Verify Changes?

Skills that share tags, products or a category with Verify Changes: Adk Verify Snippets (google/adk-python, 22k stars), Hermetic Python Unit Tests (dimensionalOS/dimos, 4.6k stars), ONNX Runtime Test Runner (microsoft/onnxruntime, 22k stars) and Simple Modern Uv (jlevy/simple-modern-uv, 301 stars). The comparison table on this page puts their stars, adoption, token cost, safety result and licence side by side.

Who maintains Verify Changes?

389ds (a GitHub organization) maintains it in 389ds/389-ds-base, which has 294 GitHub stars. The repository holds 7 skills in this directory. The repository was last updated on October 6, 2026.

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