Android API Diff
gkd-kit/gkd
Looks up Android framework Java and AIDL APIs across versions with the android-api-diff CLI: signatures, availability, source files and hidden-API access code.
Find and run the checks a change owes, from what it touches and what that can reach.
Apache-2.0Auto-check passed
Install Verify Changes
$ npx skills add epam/cloud-pipeline --skill verify-changes -a claude-codeProject install by default; add -g for ~/.claude/skills/.
$ gh skill install epam/cloud-pipeline 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/epam/cloud-pipeline.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/epam/cloud-pipeline/tree/develop/.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/epam/cloud-pipeline/tree/develop/.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 epam/cloud-pipeline --skill verify-changes -a codexProject install goes to .agents/skills/; add -g for ~/.codex/skills/.
$ gh skill install epam/cloud-pipeline verify-changes --agent codexProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/epam/cloud-pipeline.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/epam/cloud-pipeline/tree/develop/.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 epam/cloud-pipeline --skill verify-changes -a cursorProject install goes to .agents/skills/; add -g for ~/.cursor/skills/.
$ gh skill install epam/cloud-pipeline verify-changes --agent cursorProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/epam/cloud-pipeline.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/epam/cloud-pipeline/tree/develop/.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/epam/cloud-pipeline.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 epam/cloud-pipeline --skill verify-changes -a gemini-cliProject install goes to .agents/skills/; add -g for ~/.gemini/skills/.
$ gh skill install epam/cloud-pipeline verify-changes --agent gemini-cliProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/epam/cloud-pipeline.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/epam/cloud-pipeline/tree/develop/.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 epam/cloud-pipeline 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 epam/cloud-pipeline --skill verify-changes -a github-copilotProject install goes to .agents/skills/; add -g for ~/.copilot/skills/.
$ git clone --depth 1 https://github.com/epam/cloud-pipeline.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/epam/cloud-pipeline/tree/develop/.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 epam/cloud-pipeline --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 epam/cloud-pipeline verify-changes --agent opencodeProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/epam/cloud-pipeline.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/epam/cloud-pipeline/tree/develop/.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.
Facts
- Skill name
verify-changes- GitHub stars
- 162
- Token cost
- ~748 tokens
- SKILL.md length
- 344 words
- Files
- 1
- Skills in repo
- 8
- Repo updated
- First seen
- Licence
- Apache-2.0
At a glance
Find and run the checks a change owes, from what it touches and what that can reach.
- Calls npm, git and python
What it does
Verify Changes is an agent skill from epam/cloud-pipeline. Find and run the checks a change owes, from what it touches and what that can reach. Use after editing any file, when about to call a change finished, or when asked whether something passes.
Its SKILL.md is about 750 tokens, which your agent loads only when the skill is triggered. It is a single SKILL.md file with no bundled scripts.
It works with Gradle. The repository describes itself as: Cloud agnostic genomics analysis, scientific computation and storage platform. The licence is Apache-2.0.
Example prompts
- “/verify-changes”
Requirements
- Python 3
What it can do on your machine
Read from SKILL.md and the folder at commit 5017688. 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:
npmgitpython
From the folder's file list and the shell code blocks in SKILL.md.
Network
No URLs in SKILL.md. Its commands use npm 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 Changes loads about 748 tokens when it runs. Until then it costs about 51 tokens; SKILL.md has 344 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.
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 epam/cloud-pipeline at commit 5017688, republished under its Apache-2.0 licence (© epam). 344 words, ~748 tokens.
Download SKILL.mdSave it as
.claude/skills/verify-changes/SKILL.md (or your agent's skills folder).- name
- verify-changes
- description
- Find and run the checks a change owes, from what it touches and what that can reach. Use after editing any file, when about to call a change finished, or when asked whether something passes.
Verifying a change
The Verify step. Decide what to run from the diff itself — the paths in it, and what those paths can reach.
A Gradle module's dependents owe their tests as well as the module's own. Their build.gradle is
what names them:
grep -rl 'project(.:core.)' --include=build.gradle .Some declare it as project(path: ":x", configuration: "y") instead, so treat that as a starting list
rather than a complete one.
Never the whole platform. buildAll, buildAllFast, distZip/distTar, buildDoc, the
bootRepackage/buildUI/buildPipe artifact tasks and everything under e2e/ cost between an hour
and half a day, and belong to post-merge CI or to release time by hand. Never escalate to a heavier
check because a lighter one was unavailable.
A change inside e2e/gui is the exception: the tests it touches are the check it owes. Read
e2e/gui/AGENTS.md first.
A partial toolchain is the normal case here. Most contributors have one language's tooling and not the others, so you satisfy a check by running it or by recording that the tool was absent. A declared skip is a correct outcome; a silent one is not.
Ask the module for its check. settings.gradle lists every Gradle subproject: run
./gradlew :<module>:test where its build.gradle gives it a test task, and
./gradlew :<module>:checkstyleMain :<module>:checkstyleTest :<module>:pmdMain :<module>:pmdTest
where it has Java sources — each task carries the module prefix; unprefixed, those four are the
whole platform. Several Python modules have neither — their runner is named in that module's
AGENTS.md or README.md.
What departs from that:
client/ — the runners in client/AGENTS.md → "Checks", then the verify-client-live skill
where it applies.
client/src/themes/ — also npm run gui-themes-prepare && git diff --exit-code -- src/themes,
and commit what it regenerates.
api, elasticsearch-agent — tests need a live PostgreSQL, configured in
api/src/test/resources/test-application.properties and
elasticsearch-agent/src/test/resources/test-application.properties.
workflows/pipe-common/, scripts/ —
cd workflows/pipe-common && export PYTHONPATH=$PYTHONPATH:$PWD && python -m pytest
Any AGENTS.md, CLAUDE.md, .claude/, .cursor/, .github/instructions/, .agents/ —
.agents/skills/modifying-instructions/scripts/verify-instructions.sh
e2e/gui/ — e2e/gui/AGENTS.md, and its own e2e/gui/gradlew: a standalone build, so no root
:<module>: task reaches it.
Where that search finds nothing, nothing else will check the path later either — deploy/, docs/
and the rest of e2e/ are the large cases — so reading the diff is the verification.
© epam, Apache-2.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-changes of epam/cloud-pipeline.
Open the folder on GitHubat commit 5017688
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.
| Skill | Stars | Used in | Tokens | Auto-check | Licence | Repo updated |
|---|---|---|---|---|---|---|
| Verify Changes this skillepam/cloud-pipeline | 162 | — | ~748 | Automated safety check: Pass | Apache-2.0 | |
| Android API Diffgkd-kit/gkd | 43k | — | ~796 | Automated safety check: Pass | GPL-3.0 | |
| Exposed Bug Fix WorkflowJetBrains/Exposed | 9.3k | — | ~3.8k | Automated safety check: Pass | Apache-2.0 | |
| Caffeine Cache Optimization Experimentsben-manes/caffeine | 18k | — | ~2.6k | Automated safety check: Notes | Apache-2.0 | |
| Android Developmentdpconde/claude-android-skill | 336 | — | ~1.7k | Automated safety check: Pass | MIT | |
| Diagnosing Compose StabilityrosuH/EasyWatermark | 1.9k | 1 repos | ~3.3k | Automated safety check: Pass | Apache-2.0 |
Similar skills
- Official
Exposed Bug Fix Workflow
JetBrains/Exposed
Takes a GitHub or YouTrack issue for the Exposed project through reproduction, a failing test, a fix, validation and a pull request.
Caffeine Cache Optimization Experiments
ben-manes/caffeine
Runs controlled JMH experiments on the Caffeine cache to find shared contention and hot-path waste, then reviews correctness and returns a reviewable patch.
Android Development
dpconde/claude-android-skill
Create production-quality Android applications following Google's official architecture guidance and NowInAndroid best practices.
Diagnosing Compose Stability
rosuH/EasyWatermark
A skill your agent uses to diagnose Jetpack Compose stability problems by enabling and reading the Compose Compiler Reports (classes.txt, composables.txt, composables.csv, module.json).
Geb and Spock Browser Tests
apache/groovy-geb
Writes and reviews Geb browser automation specs with Spock, using Page Objects, at checkers, Modules and explicit waits, for Groovy and Gradle projects.
More from epam/cloud-pipeline
All 8 skills in this repoVerify Client Live
epam/cloud-pipeline
Open a user-visible client/ change in a browser against a real Cloud Pipeline deployment.
Configure Dev Environment
epam/cloud-pipeline
Learn which toolchains and environments this workstation has and how to invoke them, or set them up when they are missing.
Commit Changes
epam/cloud-pipeline
Required before you commit, push or open a pull request here, asked or not.
Modifying Instructions
epam/cloud-pipeline
Required before adding or changing anything an agent reads — a convention in AGENTS.md, a procedure as a skill, a pattern-scoped rule.
Plan Change
epam/cloud-pipeline
Plan the work before you edit — its phases, the model and effort each takes, and whether it is worth a plan file with a ledger beside it.
Implement Task
epam/cloud-pipeline
Start here before the first edit of any file — a one-liner and a docs change included.
Related
Works with
Questions about Verify Changes
What does Verify Changes do?
Find and run the checks a change owes, from what it touches and what that can reach. Verify Changes is an agent skill from epam/cloud-pipeline. Find and run the checks a change owes, from what it touches and what that can reach.
How do I install Verify Changes in Claude Code?
Run `npx skills add epam/cloud-pipeline --skill verify-changes -a claude-code`. Or copy the skill folder (.agents/skills/verify-changes in epam/cloud-pipeline) 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 epam/cloud-pipeline --skill verify-changes -a codex`. Or copy the skill folder (.agents/skills/verify-changes in epam/cloud-pipeline) 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 epam/cloud-pipeline --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 (npm, git and python). Our summary lists: Python 3.
Does Verify Changes access the network?
SKILL.md contains no URLs. Its commands use npm and git, 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 is published under the Apache-2.0 licence (the repository's licence). It allows redistribution, so the full SKILL.md is shown on this page.
How many tokens does Verify Changes use?
About 748 tokens (SKILL.md is roughly 3k 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 Changes?
Skills that share tags, products or a category with Verify Changes: Android API Diff (gkd-kit/gkd, 43k stars), Exposed Bug Fix Workflow (JetBrains/Exposed, 9.3k stars), Caffeine Cache Optimization Experiments (ben-manes/caffeine, 18k stars) and Android Development (dpconde/claude-android-skill, 336 stars). The comparison table on this page puts their stars, adoption, token cost, safety result and licence side by side.
Who maintains Verify Changes?
epam (a GitHub organization) maintains it in epam/cloud-pipeline, which has 162 GitHub stars. The repository holds 8 skills in this directory. The repository was last updated on October 7, 2026.
Source: epam/cloud-pipeline on GitHub. Facts on this page come from the repository at the commit we read; the author's words are quoted as theirs.