Composio powers 1000+ toolkits, tool search, context management, authentication, and a sandboxed workbench to help you build AI agents that turn intent into action.

next
md 26 lines 1.67 KB
Rendered Raw
1 ---
2 name: verify-change
3 description: 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.
4 ---
5
6 # Verify Change
7
8 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.
9
10 Use [the verification map](references/verification-map.md) to select the existing
11 checks and preserve a task's goal, authority, next step and blockers across sessions.
12
13 1. For substantial work, initialize one task with the requested outcome and a
14 matching profile. Keep the actual user request authoritative.
15 2. Inspect `status` when resuming, update `nextStep` and `blocker` in its local
16 `task.json`, and refresh external issue, PR and CI state before acting.
17 3. Run the profile after implementation. Read the receipt and its boundary before
18 reporting what passed. A passing profile establishes only its named checks.
19 4. Treat a recurring intervention as a candidate for an existing behavioral test,
20 type or lint check. Prove the check rejects the original mistake. Preserve
21 one-off judgment locally instead of expanding global instructions.
22
23 Do not create task records for trivial edits. Private task data and command output
24 stay under ignored `.artifacts/`; never attach them wholesale to a PR. This tool
25 records context and evidence, and does not grant commit, push, merge or release
26 authority.