adapt

Synchronize installed agents, rules, and skills with project state after stack drift.

Updated Apr 27, 2026
One-click install
npx skills add https://github.com/vTRKA/supervibe --skill adapt-vtrka
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: adapt
Source: https://github.com/vTRKA/supervibe/tree/main/skills/adapt
Command: npx skills add https://github.com/vTRKA/supervibe --skill adapt-vtrka

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Prevents AI coding agents and skills from becoming outdated when your project stack changes, such as renamed files, new modules, or major dependency upgrades, by generating an evidence-based adaptation plan before any writes.

Core Features & Use Cases

  • Dry-run, diff-gated adaptation: Reads project state and change evidence to propose exact agent/rule/skill updates without immediately mutating durable artifacts.
  • Stale reference repair: Detects deleted or renamed files referenced by installed artifacts and updates or flags those references using grep/diff evidence.
  • Lifecycle-driven, verification-first execution: Persists adapt lifecycle state and requires explicit approval before applying changes, then reruns verification to confirm a clean state.

Quick Start

Ask your AI tool to run the adaptation dry-run by saying: "Please run /supervibe-adapt and propose the safest updates based on my current project stack changes."

Frequently Asked Questions about adapt

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I synchronize AI agents with project stack changes after dependency upgrades?

Synchronize AI agents with project stack changes by generating an evidence-based adaptation plan that reads project state diffs and proposes exact agent, rule, and skill updates without immediately mutating durable artifacts.

What is the best way to fix stale file references in AI coding rules after renaming or removing modules?

Fix stale file references in AI coding rules by detecting deleted or renamed files using grep and diff evidence, then proposing updates or flags for those outdated references before applying any changes.

How does dry-run verification work for updating installed skills during maintenance sessions?

Dry-run verification for updating installed skills works by reading change evidence to propose safe updates, requiring explicit user approval before any writes, and rerunning verification to confirm a clean state.

Can I update agent context automatically without user approval when stack drift occurs?

Updating agent context when stack drift occurs always requires explicit user approval before applying any writes, ensuring that diff-based source-of-truth reads and evidence-backed planning gate all modifications to managed artifacts.

When do I need to refresh agent context to match current runtime and managed artifacts?

Refresh agent context to match current runtime and managed artifacts during maintenance sessions triggered by explicit adapt requests or plugin updates where new modules, renamed files, or major dependency changes have caused stack drift.