Verify the whole changeset the way the User meets it: the suite, the Review gate, the Critical Paths, once every Task has landed. TRIGGER when the last Slice is staged, when an autonomous run reaches functional completion, or on "verify the changes". DO NOT TRIGGER with Tasks still open, where the Orchestrator judges each Task's returned Evidence instead.
Scanned 9/5/2026
Install to Claude Code
Skills Directorynpx -y skills add heyJordanParker/dotfiles --skill verify-changes --agent claude-codeInstalls into .claude/skills of the current project.
Are you the author of Verify Changes?
Add the live security badge to your README — it updates automatically with every re-scan.
[](https://www.skillsdirectory.com/skills/heyjordanparker-verify-changes)More formats (shields.io, HTML) on the badges page.
---
name: verify-changes
description: Verify the whole changeset the way the User meets it: the suite, the Review gate, the Critical Paths, once every Task has landed. TRIGGER when the last Slice is staged, when an autonomous run reaches functional completion, or on "verify the changes". DO NOT TRIGGER with Tasks still open, where the Orchestrator judges each Task's returned Evidence instead.
---
# Verify Changes
Runs once, over everything. Run it earlier and the Tasks still ahead rewrite what it proved.
## 1. Run the test suite
The suite passes. /prove governs what counts as a pass.
## 2. Run the Review gate
Run /review over the uncommitted changes.
## 3. Walk the Critical Paths
Run /user-testing over the User-facing behavior the changes touch.
IF the changes touch the User Interface:
### Ask /user-testing for browser testing
It traces code and nothing else until its caller asks.
## 4. Triage every finding with /triage
### Run /triage over every finding steps 1 through 3 returned
Its gate routes the confirmed findings to the Subagents that own the fixes.
Never: fixing a finding yourself while coordinating.
Is this your skill, or is something wrong with this listing? Request removal or report an issue. Author removals are honored within 72 hours.
No comments yet. Be the first to comment!
Ultra-compressed communication mode. Cuts token usage ~75% by speaking like caveman while keeping full technical accuracy. Supports intensity levels: lite, full (default), ultra, wenyan-lite, wenyan-full, wenyan-ultra. Use when user says "caveman mode", "talk like caveman", "use caveman", "less tokens", "be brief", or invokes /caveman. Also auto-triggers when token efficiency is requested.
Adversarial multi-agent planning skill. Self-orchestrates 5 hostile category members (unspecified-low, unspecified-high, deep, ultrabrain, artistry) via team-mode for ruthless cross-critique debate, distills only the defensible insights, then MANDATORILY hands the distilled insight bundle to the `plan` agent for executable plan formalization. Use when planning needs maximum rigor and surfacing of weak assumptions, blind spots, and over-engineering. Triggers: 'hyperplan', 'hpp', '/hyperplan', ...
Routes multi-tool workflows through MCP servers for large datasets and pipelines. Use when Bash tool overhead is limiting throughput on data-heavy tasks.
**Complete production-ready guide for Google Gemini embeddings API** This skill provides comprehensive coverage of the `gemini-embedding-001` model for generating text embeddings, including SDK usage, REST API patterns, batch processing, RAG integration with Cloudflare Vectorize, and advanced use cases like semantic search and document clustering. ---
Recovers prior coding-agent session context by running `catchup <agent> --since-compact`, which extracts a clean summary of a previous Codex, Claude Code, Antigravity, OpenCode, or Pi Agent session. Use when the user says "catch up", "what did the last session do", "get me up to speed", "I switched agents", or asks to recover/summarize a previous session before continuing. Do NOT use for the current conversation, git history, or any non-agent log.
