Verify Change

Maintain resumable task records, select repository verification profiles, inspect revision-bound receipts, and carry work between coding agents. Use for substantial SDK or CLI work spanning sessions, evidence review, or carrying work between coding agents; use package-specific skills for implementation and ordinary small edits.

31,162 stars 4,960 forksSoftware Development

Install

skills CLI (Claude Code, Cursor, Codex and more)
npx skills add ComposioHQ/composio --skill verify-change
Manual install
git clone --depth 1 https://github.com/ComposioHQ/composio.git /tmp/composio
mkdir -p ~/.claude/skills
cp -r /tmp/composio/.agents/skills/verify-change ~/.claude/skills/verify-change

Personal skills live in ~/.claude/skills. Use .claude/skills in a project folder to share a skill with your team.

From the SKILL.md

# Verify Change

Write agent-tooling scripts and tests in TypeScript and execute them with Bun; do not add `.mjs` or Node entrypoints. Existing SDK languages and package-management commands keep their repository ownership.

Use [the verification map](references/verification-map.md) to select the existing
checks and preserve a task's goal, authority, next step and blockers across sessions.

1. For substantial work, initialize one task with the requested outcome and a
   matching profile. Keep the actual user request authoritative.
2. Inspect `status` when resuming, update `nextStep` and `blocker` in its local
   `task.json`, and refresh external issue, PR and CI state before acting.
3. Run the profile after implementation. Read the receipt and its boundary before
   reporting what passed. A passing profile establishes only its named checks.
4. Treat a recurring intervention as a candidate for an existing behavioral test,
   type or lint check. Prove the check rejects the original mistake. Preserve
   one-off judgment locally instead of expanding global instructions.

Do not create task records for trivial edits. Private task data and command output
stay under ignored `.artifacts/`; never attach them wholesale to a PR. This tool
records context and evidence, and does not grant commit, push, merge or release
authority.
Read the full skill on GitHub

Details

Skill name
verify-change
Path
.agents/skills/verify-change/SKILL.md
License
MIT
Repo updated
18 November 2026

FAQ

What does the Verify Change skill do?

Maintain resumable task records, select repository verification profiles, inspect revision-bound receipts, and carry work between coding agents. Use for substantial SDK or CLI work spanning sessions, evidence review, or carrying work between coding agents; use package-specific skills for implementation and ordinary small edits.

How do I install the Verify Change skill?

skills CLI (Claude Code, Cursor, Codex and more): npx skills add ComposioHQ/composio --skill verify-change. Skills go in ~/.claude/skills (personal) or .claude/skills (project), and Claude loads them automatically when a task matches the description.

Is Verify Change popular?

It lives in ComposioHQ/composio, which has 31,162 GitHub stars and 4,960 forks, and is included in 1 curated skill list.

Related skills

Bug Fixing

31k

ComposioHQ/composio

Fix defects in the Composio SDK repository with focused reproduction, root-cause analysis, regression tests, and narrow verification. Use when the user reports a bug, failing test, CI regression, runtime defect, or incorrect SDK behavior. Do not use for new feature design or broad refactors.

Software DevelopmentIn 1 list5k

CLI Command

31k

ComposioHQ/composio

Design, implement, or review Composio CLI commands under ts/packages/cli using Effect, effect/cli, services, output conventions, configuration and environment variables, and local vendor references. Use for CLI command UX, command wiring, service changes, or CLI source edits. Do not use for CLI E2E-only work; use cli-e2e there.

Software DevelopmentIn 1 list5k

CLI E2E

31k

ComposioHQ/composio

Write, modify, or debug Docker-based Composio CLI end-to-end tests under ts/e2e-tests/cli, including binary invocation, fixture isolation, output assertions, and package manifests. Use for CLI E2E test suites only; use cli-command for CLI source implementation.

Testing & QAIn 1 list5k

Develop Screenpipe Windows

22k

screenpipe/screenpipe

Develop and test Screenpipe Windows-native changes on a disposable Azure VM created from the prepared Screenpipe Windows dev image. Use for Windows compiler, process, service, local API, desktop, capture, installer, or permission behavior. Do not use for React-only work proved by the browser mock.

Software DevelopmentIn 1 list2.3k

Typescript SDK

31k

ComposioHQ/composio

Implement or modify TypeScript SDK behavior in @composio/core or shared TypeScript packages, including tools, toolkits, sessions, auth configs, connected accounts, modifiers, and generated SDK surfaces. Use for TS runtime/API work; pair with typescript-testing for verification and cross-sdk-parity when Python must match.

Software DevelopmentIn 1 list5k

Screenpipe API

22k

screenpipe/screenpipe

Query the user's local and synced-device Screenpipe data via the REST API at localhost:3030. Use for screen activity, meetings, apps, productivity, other-device or cross-device history, media export, retranscription, or connected services.

Software DevelopmentIn 1 list2.3k

Browse the most popular Claude skills, all software development skills, or write your own with the skills generator.