skills.rest
chenwei791129
chenwei791129COMMUNITY
Explore all skills by this author →
GitHub

spectra-drift

Analyze drift between Spectra-managed change plans and repository state.

1|Updated Dec 7, 2025
Search Tags:#automation#refactoring#codebase#analysis#drift#spectra
One-click install
npx skills add https://github.com/chenwei791129/rancher-kubeconfig-updater --skill spectra-drift-chenwei791129
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: spectra-drift
Source: https://github.com/chenwei791129/rancher-kubeconfig-updater/tree/main/.claude/skills/spectra-drift
Command: npx skills add https://github.com/chenwei791129/rancher-kubeconfig-updater --skill spectra-drift-chenwei791129

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This Skill identifies discrepancies between your planned Spectra changes and the current state of the codebase, preventing integration conflicts and outdated implementation plans.

Core Features & Use Cases

  • Drift Analysis: Automatically detects broken design anchors, task collisions with external commits, and time-based dormancy.
  • Severity Assessment: Categorizes drift into light, medium, or heavy, providing actionable guidance on whether to proceed, refresh, or restart.
  • Use Case: Before applying a long-running feature branch, use this skill to ensure that recent refactors in the main codebase haven't invalidated your planned tasks or design references.

Quick Start

Run the spectra-drift skill to analyze the current drift status for the change named add-auth.

Frequently Asked Questions about spectra-drift

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

FAQPage Schema
How do I detect code drift between my planned changes and the current repository state?▼

Code drift analysis identifies structural and task-based inconsistencies between planned changes and the current repository state. It operates on active change sets to report broken design anchors and task collisions caused by external commits.

Why does my feature branch have task collisions with recent main branch commits?▼

Task collisions with recent main branch commits happen when external commits modify structures referenced by your active change sets. Drift analysis identifies these structural inconsistencies and provides actionable recommendations for plan reconciliation.

Do I need the spectra CLI to run programmatic drift analysis on my codebase?▼

Yes, you need the spectra CLI to execute programmatic drift analysis. It operates on active change sets to report broken design anchors and generate actionable recommendations for reconciling your implementation plan with the current repository state.

How do I assess the severity of codebase drift in my active change sets?▼

Assess codebase drift severity by categorizing inconsistencies into light, medium, or heavy classifications. This severity assessment provides actionable guidance on whether to proceed with the plan, refresh design anchors, or restart the implementation.

When should I run a drift analysis on my long-running feature branch?▼

Run drift analysis before applying a long-running feature branch to ensure recent refactors in the main codebase haven't invalidated planned tasks or design references. This prevents integration conflicts and identifies outdated implementation plans.

Related Skills

Explore More Software Engineering Skills→
cashwucashwu
24

spectra-drift

Detect codebase drift by comparing a Spectra change with the current state.

Community
Advanced
MomoChenisMeMomoChenisMe
1

speclink-drift

Detect and analyze drift in Speclink changes against the current codebase state.

Community
Intermediate
gekko68gekko68

bash-executor

Execute Bash commands with validation, dry-run previews, and timeout protection.

Community
Advanced
ZeliperZeliper

git-operations

Automates Git workflows with standardized [TASK-ID] commit messages and artifact exclusions.

Community
Basic