skills.rest
xxyj
xxyjCOMMUNITY
Explore all skills by this author →
GitHub

msx:drift

Compare archived specifications against implementation code to identify drift.

Updated Mar 16, 2026
Search Tags:#code analysis#drift detection#health reporting#spec-code drift#archived spec analysis
One-click install
npx skills add https://github.com/xxyj/xx-ai-cli --skill msx-drift
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: msx:drift
Source: https://github.com/xxyj/xx-ai-cli/tree/main/.cursor/skills/msx-12-drift
Command: npx skills add https://github.com/xxyj/xx-ai-cli --skill msx-drift

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes scripts (resource) components.

What problem does it solve?

The msx:drift Skill identifies potential deviations between archived specifications and their corresponding code, helping maintain code health and compliance.

Core Features & Use Cases

  • Spec-Code Analysis: Compares archived specs against current code for drift.
  • Health Reporting: Outputs a detailed health status report indicating drifted specs and their impact.
  • Use Case: When reviewing code changes after a feature update, msx:drift can quickly inform developers of any potential drift issues that might have arisen.

Quick Start

Run the msx:drift command to initiate a spec-code drift scan and receive a health report.

Frequently Asked Questions about msx:drift

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

FAQPage Schema
How do I detect spec-code drift between archived specifications and implementation code?▼

Spec-code drift detection compares archived specifications against current implementation code to identify deviations. This process assumes spec changes reflect intended code modifications and requires access to both spec and code repositories for accurate comparison.

What is spec-code drift analysis and when do I need to run it?▼

Spec-code drift analysis identifies potential deviations between archived specifications and their corresponding implementation code. You need to run it when reviewing code changes after a feature update to maintain code health and compliance.

How to generate a health report for drifted specifications after a feature update?▼

Generate a health report by initiating a spec-code drift scan to compare archived specs against current code. The output provides a detailed health status report indicating drifted specs and their impact on the codebase.

Do I need access to both spec and code repositories to check for spec-code drift?▼

Yes, checking for spec-code drift requires access to both spec and code repositories for comparison. The analysis operates on the assumption that archived spec changes reflect intended code modifications.

What's the best way to monitor code health and compliance using archived spec analysis?▼

Monitor code health by running archived spec analysis to compare archived specifications against corresponding code. This identifies potential spec-code drift and outputs a detailed health status report indicating compliance issues.

Related Skills

Explore More Software Engineering Skills→
wwloreywwlorey

audit-specs

Automates semantic audits of code specifications against library-wide codebases, outputting structured drift reports.

Community
Advanced
aroidoaroido

command-auto-implement

Automates feature implementation workflow from issue tracking to pull request merging.

Official
Advanced
kunalrawat425kunalrawat425

health

Aggregate type checks, linting, tests, and dead-code detection into a weighted 0-10 health score.

Community
Intermediate
brennancheungbrennancheung

commit-message

Analyze Git changes and generate Conventional Commits messages.

Community
Intermediate