Use this skill when changing a machine-readable contract — a JSON Schema, an API spec, or a config schema — and bumping its version: tightening a constraint, adding/removing/renaming a field, introducing a breaking change, raising an API version, or writing the changelog entry for a schema change. Trigger on \"change the schema\", \"tighten this constraint\", \"bump the schema version\", \"breaking change to the API\", \"new API version\", \"changelog entry for a schema change\". Runs six pha...
Scanned 9/2/2026
Install to Claude Code
Skills Directorynpx -y skills add Kanevry/session-orchestrator --skill contract-version-bump --agent claude-codeInstalls into .claude/skills of the current project.
Are you the author of Contract Version Bump?
Add the live security badge to your README — it updates automatically with every re-scan.
[](https://www.skillsdirectory.com/skills/kanevry-contract-version-bump)More formats (shields.io, HTML) on the badges page.
---
name: contract-version-bump
description: "Use this skill when changing a machine-readable contract — a JSON Schema, an API spec, or a config schema — and bumping its version: tightening a constraint, adding/removing/renaming a field, introducing a breaking change, raising an API version, or writing the changelog entry for a schema change. Trigger on \"change the schema\", \"tighten this constraint\", \"bump the schema version\", \"breaking change to the API\", \"new API version\", \"changelog entry for a schema change\". Runs six phases — classify against the contract's OWN versioning rule (not generic semver instinct), find every version literal and vendored copy, check consumer compatibility for new keywords, apply consistently, write the changelog entry, and report downstream drift — codifying three non-obvious traps hit in a real case (GitLab issue #17, `aiat-enablement` repo, 2026-07-25)."
---
# contract-version-bump
Canonical skill: `skills/contract-version-bump/SKILL.md`
Read that file and follow it exactly. Resolve relative links against `skills/contract-version-bump/`, not this wrapper.
Cursor has no Skill tool. Treat "invoke the contract-version-bump skill" as: Read `skills/contract-version-bump/SKILL.md`.
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!
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', ...
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.
**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. ---
Use when a repo needs CodeGraph plus ast-grep for Codex MCP setup, exploration, impact analysis, structural search, or safe refactor planning.
Interview, source-challenge, verify, save, and ADR-gate fuzzy coding requests into Codex-ready implementation specs. Use when a feature, bugfix, refactor, migration, repo-wide change, or architecture task needs user-verified requirements, source-backed decisions, durable architecture decisions, acceptance criteria, validation commands, rollout notes, saved spec/ADR files, and a Codex execution prompt. Do not use when already fully specified or when the user wants direct implementation now.
