Agent skill

Verifying Changes

by BuilderIO in BuilderIO/agent-native

Concrete, per-area proof that a change actually works before reporting it fixed, done, or "should work now" — which dev server, test command, or invocation proves a template UI change, an action, a…

No licenceAuto-check passed

Install Verifying Changes

skills CLI
$ npx skills add BuilderIO/agent-native --skill verifying-changes -a claude-code

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

GitHub CLI
$ gh skill install BuilderIO/agent-native verifying-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/BuilderIO/agent-native.git skills-src && mkdir -p .claude/skills && cp -r skills-src/.agents/skills/verifying-changes .claude/skills/verifying-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
verifying-changes
GitHub stars
7.1k
Token cost
~1.8k tokens
SKILL.md length
1,017 words
Files
1
Skills in repo
102
Repo updated
First seen
Licence
None found

At a glance

Concrete, per-area proof that a change actually works before reporting it fixed, done, or "should work now" — which dev server, test command, or invocation proves a template UI change, an action, a…

  • SKILL.md covers When this applies, Scale the verification, Do NOT report done in these… and Proof by area, plus 3 more sections
  • Calls pnpm and node

What it does

Verifying Changes is an agent skill from BuilderIO/agent-native. Concrete, per-area proof that a change actually works before reporting it fixed, done, or "should work now" — which dev server, test command, or invocation proves a template UI change, an action, a migration, a guard, or a core/package change. Use before every wrap-up, and before stopping mid-task to ask permission instead of continuing.

Its SKILL.md is about 1.8k tokens, which your agent loads only when the skill is triggered. It is a single SKILL.md file with no bundled scripts.

The repository describes itself as: A framework for building agentic apps.

Example prompts

  • “should work now”
  • “/verifying-changes”

What it can do on your machine

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

    • pnpm
    • node

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

  • Network

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

Verifying Changes loads about 1.8k tokens when it runs. Until then it costs about 89 tokens; SKILL.md has 1,017 words of instructions outside code blocks.

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

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

Without a licence we can't republish the file, so here is its outline and opening line. It has 1,017 words (~1,815 tokens).

“Before telling the user a fix, feature, or bug is done, choose the smallest proof that exercises the behavior you changed and use the row below as a guide. "I changed the code and it looks right" is not proof…”

— opening of SKILL.md by BuilderIO
name
verifying-changes
scope
dev
metadata.internal
true

Read the full SKILL.md on GitHub

Files

Just SKILL.md in .agents/skills/verifying-changes of BuilderIO/agent-native.

Open the folder on GitHubat commit be0d784

Compare with similar skills

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

Verifying Changes compared with similar skills
SkillStarsUsed inTokensAuto-checkLicenceRepo updated
Verifying Changes this skillBuilderIO/agent-native7.1k—~1.8kAutomated safety check: PassNone
Verifyasgeirtj/system_prompts_leaks69k—~3kAutomated safety check: PassCC0-1.0
Verify Before CompletionYeachan-Heo/oh-my-claudecode40k—~277Automated safety check: PassMIT
Verify Thiscursor/plugins10k2 repos~693Automated safety check: PassNone
Ruview Verifyruvnet/RuView97k—~1kAutomated safety check: NotesMIT
Proof Videoopenclaw/openclaw392k—~2.4kAutomated safety check: PassMIT

Similar skills

  • Verify

    asgeirtj/system_prompts_leaks

    Verify that a code change actually does what it's supposed to by exercising it end-to-end and observing behavior — drive the affected flow, not just tests or typecheck.

    69k GitHub stars~3k tokensUpdated yesterday
    Testing & QAAuto-check passed
  • Verify Before Completion

    Yeachan-Heo/oh-my-claudecode

    Has the agent prove that a feature, fix or refactor works, using existing tests first, then narrow commands and manual checks, and report only what was actually verified.

    40k GitHub stars~277 tokensUpdated yesterday
    Agent WorkflowsAuto-check passed
  • Verify This

    cursor/plugins

    Official

    Verify a claim with fresh local evidence: restate it falsifiably, capture baseline and treatment, compare artifacts, and return VERIFIED, NOT VERIFIED, or INCONCLUSIVE.

    10k GitHub starsUsed in 2 repos~693 tokens
    Auto-check passed
  • Ruview Verify

    ruvnet/RuView

    Verify a RuView build — full Rust workspace tests, the deterministic Python pipeline proof (SHA-256 Trust Kill Switch), firmware hash manifest, and the ADR-028 witness bundle with one-command…

    97k GitHub stars~1k tokensUpdated today
    DevelopmentAuto-check: notes
  • Proof Video

    openclaw/openclaw

    Add subtitles, captions, narration cues, or zoom to a proof video or PR recording using repo-local capture helpers and a system ffmpeg renderer.

    392k GitHub stars~2.4k tokensUpdated today
    Media & CreativeAuto-check passed
  • Verify Release

    openclaw/openclaw

    Verify regular or extended-stable OpenClaw releases against the exact publication surfaces, workflow identities, package provenance, smoke tests, and live Gateway behavior expected for that release…

    392k GitHub stars~2.4k tokensUpdated today
    Testing & QAAuto-check passed

More from BuilderIO/agent-native

All 102 skills in this repo
  • Actions

    BuilderIO/agent-native

    How to create and run agent actions. An agent skill from BuilderIO/agent-native.

    7.1k GitHub stars~4.4k tokensUpdated today
    Auto-check passed
  • Client Methods

    BuilderIO/agent-native

    Client method surface rules. An agent skill from BuilderIO/agent-native.

    7.1k GitHub stars~1.2k tokensUpdated today
    Auto-check passed
  • Adding A Feature

    BuilderIO/agent-native

    The four-area checklist every new feature must complete. An agent skill from BuilderIO/agent-native.

    7.1k GitHub stars~4k tokensUpdated today
    Auto-check passed
  • Address Feedback

    BuilderIO/agent-native

    Triage feedback from docs, issues, Slack threads, or pasted notes into verified bugs, UX proposals, unclear questions, and skipped noise.

    7.1k GitHub stars~4.4k tokensUpdated today
    Auto-check passed
  • Audit Log

    BuilderIO/agent-native

    Durable, access-scoped, append-only record of who changed what app data, when, and whether it was the agent or a human.

    7.1k GitHub stars~2k tokensUpdated today
    Auto-check passed
  • Automations

    BuilderIO/agent-native

    Event-triggered and schedule-triggered automations with natural-language conditions.

    7.1k GitHub stars~4.4k tokensUpdated today
    Auto-check passed

Questions about Verifying Changes

What does Verifying Changes do?

Concrete, per-area proof that a change actually works before reporting it fixed, done, or "should work now" — which dev server, test command, or invocation proves a template UI change, an action, a…. Verifying Changes is an agent skill from BuilderIO/agent-native. Concrete, per-area proof that a change actually works before reporting it fixed, done, or "should work now" — which dev server, test command, or invocation proves a template UI change, an action, a migration, a guard, or a core/package change.

How do I install Verifying Changes in Claude Code?

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

How do I install Verifying Changes in Codex?

Run `npx skills add BuilderIO/agent-native --skill verifying-changes -a codex`. Or copy the skill folder (.agents/skills/verifying-changes in BuilderIO/agent-native) into .agents/skills/verifying-changes in your project. Codex loads it when a task matches its description.

Can I use Verifying 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 BuilderIO/agent-native --skill verifying-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/verifying-changes, .gemini/skills/verifying-changes, .github/skills/verifying-changes and .opencode/skills/verifying-changes in your project.

What does Verifying Changes need to run?

Going by SKILL.md and its folder, Verifying Changes needs the command-line tools its instructions call (pnpm and node).

Does Verifying Changes access the network?

SKILL.md contains no URLs. Any network use would come from the scripts or tools the agent runs. This is read from the text; nothing was executed.

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

No licence was found for Verifying Changes or its repository. Without one, default copyright applies: ask the author before reusing or redistributing it.

How many tokens does Verifying Changes use?

About 1.8k tokens (SKILL.md is roughly 7.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 Verifying Changes?

Skills that share tags, products or a category with Verifying Changes: Verify (asgeirtj/system_prompts_leaks, 69k stars), Verify Before Completion (Yeachan-Heo/oh-my-claudecode, 40k stars), Verify This (cursor/plugins, 10k stars) and Ruview Verify (ruvnet/RuView, 97k stars). The comparison table on this page puts their stars, adoption, token cost, safety result and licence side by side.

Who maintains Verifying Changes?

BuilderIO (a GitHub organization) maintains it in BuilderIO/agent-native, which has 7,103 GitHub stars. The repository holds 102 skills in this directory. The repository was last updated on October 9, 2026.

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