Adk Verify Snippets
google/adk-python
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…
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…
$ npx skills add 389ds/389-ds-base --skill verify-changes -a claude-codeProject install by default; add -g for ~/.claude/skills/.
$ gh skill install 389ds/389-ds-base verify-changes --agent claude-codeProject scope by default; add --scope user for a personal install. Needs GitHub CLI 2.90.0 or later (public preview).
$ 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-srcUse ~/.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/
Install the "verify-changes" agent skill from https://github.com/389ds/389-ds-base/tree/main/.agents/skills/verify-changes into .claude/skills/verify-changes/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "verify-changes", then confirm the skill loads.Claude Code copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
$skill-installer install https://github.com/389ds/389-ds-base/tree/main/.agents/skills/verify-changesType this inside Codex. $skill-installer <name> installs a curated skill from openai/skills. The installer writes to $CODEX_HOME/skills (default ~/.codex/skills). Restart Codex if the skill does not show up.
$ npx skills add 389ds/389-ds-base --skill verify-changes -a codexProject install goes to .agents/skills/; add -g for ~/.codex/skills/.
$ gh skill install 389ds/389-ds-base verify-changes --agent codexProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/389ds/389-ds-base.git skills-src && mkdir -p .agents/skills && cp -r skills-src/.agents/skills/verify-changes .agents/skills/verify-changes && rm -rf skills-srcUse ~/.agents/skills/ instead of .agents/skills for a personal install.
Codex skills documentation · loads skills from .agents/skills/
Install the "verify-changes" agent skill from https://github.com/389ds/389-ds-base/tree/main/.agents/skills/verify-changes into .agents/skills/verify-changes/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "verify-changes", then confirm the skill loads.Codex copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
$ npx skills add 389ds/389-ds-base --skill verify-changes -a cursorProject install goes to .agents/skills/; add -g for ~/.cursor/skills/.
$ gh skill install 389ds/389-ds-base verify-changes --agent cursorProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/389ds/389-ds-base.git skills-src && mkdir -p .cursor/skills && cp -r skills-src/.agents/skills/verify-changes .cursor/skills/verify-changes && rm -rf skills-srcUse ~/.cursor/skills/ instead of .cursor/skills for a personal install.
Cursor skills documentation · loads skills from .cursor/skills/, .agents/skills/, .claude/skills/, .codex/skills/
Install the "verify-changes" agent skill from https://github.com/389ds/389-ds-base/tree/main/.agents/skills/verify-changes into .cursor/skills/verify-changes/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "verify-changes", then confirm the skill loads.Cursor copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
$ gemini skills install https://github.com/389ds/389-ds-base.git --path .agents/skills/verify-changes--scope user (default) or --scope workspace; --path is the subfolder of the repo that holds the skill; --consent skips the security confirmation prompt.
$ npx skills add 389ds/389-ds-base --skill verify-changes -a gemini-cliProject install goes to .agents/skills/; add -g for ~/.gemini/skills/.
$ gh skill install 389ds/389-ds-base verify-changes --agent gemini-cliProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/389ds/389-ds-base.git skills-src && mkdir -p .gemini/skills && cp -r skills-src/.agents/skills/verify-changes .gemini/skills/verify-changes && rm -rf skills-srcUse ~/.gemini/skills/ instead of .gemini/skills for a personal install, then run /skills reload.
Gemini CLI skills documentation · loads skills from .gemini/skills/, .agents/skills/
Install the "verify-changes" agent skill from https://github.com/389ds/389-ds-base/tree/main/.agents/skills/verify-changes into .gemini/skills/verify-changes/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "verify-changes", then confirm the skill loads.Gemini CLI copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
$ gh skill install 389ds/389-ds-base verify-changesInstalls for Copilot at project scope by default; add --scope user for a personal install. Preview a skill first with gh skill preview. Needs GitHub CLI 2.90.0 or later (public preview).
$ npx skills add 389ds/389-ds-base --skill verify-changes -a github-copilotProject install goes to .agents/skills/; add -g for ~/.copilot/skills/.
$ git clone --depth 1 https://github.com/389ds/389-ds-base.git skills-src && mkdir -p .github/skills && cp -r skills-src/.agents/skills/verify-changes .github/skills/verify-changes && rm -rf skills-srcUse ~/.copilot/skills/ instead of .github/skills for a personal install. Commit .github/skills so cloud agent and code review can use it.
GitHub Copilot skills documentation · loads skills from .github/skills/, .claude/skills/, .agents/skills/
Install the "verify-changes" agent skill from https://github.com/389ds/389-ds-base/tree/main/.agents/skills/verify-changes into .github/skills/verify-changes/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "verify-changes", then confirm the skill loads.GitHub Copilot copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
$ npx skills add 389ds/389-ds-base --skill verify-changes -a opencodeOpenCode documents no install command of its own. Project install goes to .agents/skills/; add -g for ~/.config/opencode/skills/.
$ gh skill install 389ds/389-ds-base verify-changes --agent opencodeProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/389ds/389-ds-base.git skills-src && mkdir -p .opencode/skills && cp -r skills-src/.agents/skills/verify-changes .opencode/skills/verify-changes && rm -rf skills-srcUse ~/.config/opencode/skills/ instead of .opencode/skills for a personal install.
OpenCode skills documentation · loads skills from .opencode/skills/, .claude/skills/, .agents/skills/
Install the "verify-changes" agent skill from https://github.com/389ds/389-ds-base/tree/main/.agents/skills/verify-changes into .opencode/skills/verify-changes/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "verify-changes", then confirm the skill loads.OpenCode copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
verify-changesVerify 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. 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.
3 steps, taken from the step headings in SKILL.md.
Read from SKILL.md and the folder at commit cb60126. It shows what the files ask for, not the result of running them.
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.
Shell commands in SKILL.md call:
makegitnpmuvpython3bashdnfnpxFrom the folder's file list and the shell code blocks in SKILL.md.
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.
Names no API keys, tokens, secrets or passwords.
From names ending in _API_KEY, _TOKEN, _SECRET, _KEY or _PASSWORD in SKILL.md.
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.
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.
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.
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).”
SKILL.md and 1 other file (references) in .agents/skills/verify-changes of 389ds/389-ds-base.
Open the folder on GitHubat commit cb60126
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.
| Skill | Stars | Used in | Tokens | Auto-check | Licence | Repo updated |
|---|---|---|---|---|---|---|
| Verify Changes this skill389ds/389-ds-base | 294 | — | ~1.9k | Automated safety check: Pass | Custom licence | |
| Adk Verify Snippetsgoogle/adk-python | 22k | — | ~1.4k | Automated safety check: Pass | Apache-2.0 | |
| Hermetic Python Unit TestsdimensionalOS/dimos | 4.6k | — | ~1.4k | Automated safety check: Pass | Custom licence | |
| ONNX Runtime Test Runnermicrosoft/onnxruntime | 22k | — | ~1.8k | Automated safety check: Pass | MIT | |
| Simple Modern Uvjlevy/simple-modern-uv | 301 | — | ~1.9k | Automated safety check: Pass | MIT | |
| Test Coverage Reviewareed1192/finance-news-aggregator | 149 | — | ~2.6k | Automated safety check: Pass | MIT |
google/adk-python
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…
dimensionalOS/dimos
Rules for writing, fixing and reviewing pytest unit tests that are hermetic: behavior-focused, deterministic, isolated and cheap to run.
microsoft/onnxruntime
Runs and debugs ONNX Runtime tests: Google Test executables for C++ and unittest or pytest for Python, with filters and build-directory guidance.
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.
areed1192/finance-news-aggregator
Audit, plan, write, and verify unit tests for Python projects using pytest.
microsoft/onnxruntime
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.
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.
389ds/389-ds-base
Add or extend a pytest integration test for 389 Directory Server under dirsrvtests/.
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.
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…
389ds/389-ds-base
Rules for modifying back-ldbm database code under the dual-backend (BDB + LMDB) architecture.
389ds/389-ds-base
Expose a server setting in the Cockpit web console (389-console) or change web UI behavior.
Categories
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.
Verify Changes fits situations like: asked to test this change; check nothing regressed before a PR.
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.
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.
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.
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.
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.
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.
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.
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.
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.
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.