instruction-drift

Compare local instruction files against external documentation to generate drift reports.

94|31|Updated Feb 5, 2026
One-click install
npx skills add https://github.com/PureWeen/PolyPilot --skill instruction-drift
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: instruction-drift
Source: https://github.com/PureWeen/PolyPilot/tree/main/.claude/skills/instruction-drift
Command: npx skills add https://github.com/PureWeen/PolyPilot --skill instruction-drift

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes scripts (resource) and references (resource) and assets (resource) components.

What problem does it solve?

This Skill detects whether local instruction files and skills have diverged from their upstream documentation, preventing outdated guidance.

Core Features & Use Cases

  • Drift Detection: Compares local instruction files and manifests against external documentation sources to identify discrepancies.
  • Monitoring Upstream Changes: Tracks updates such as new releases, website content changes, and closed issues that may impact instructions.
  • Use Case: Before updating or editing an instruction file, run this Skill to verify that the guidance reflects the latest upstream documentation and release notes.

Quick Start

Run the instruction drift detection script to check all tracked sources and generate a comprehensive drift report for review.

Frequently Asked Questions about instruction-drift

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

FAQPage Schema
How do I detect documentation drift between local instruction files and external sources?

Documentation drift is detected by analyzing repository manifests, website content hashes, and issue states to identify discrepancies between local instructions and upstream sources. This process generates a comprehensive drift report for review.

What is the best way to maintain content consistency with upstream documentation?

Content consistency is maintained by monitoring upstream changes such as new releases, website content updates, and closed issues. Running a drift detection script compares local instruction files against these external sources to prevent outdated guidance.

When do I need to verify upstream documentation for instruction files?

Upstream verification is needed before updating or editing an instruction file. Running drift detection verifies that the guidance reflects the latest external documentation and release notes, ensuring accuracy in version control and compliance workflows.

How do I check repository manifests and website content hashes for instruction discrepancies?

You check for discrepancies by running the instruction drift detection script. It analyzes repository manifests and website content hashes to produce a comprehensive drift report detailing where local instructions have diverged from external sources.

Can I use drift detection for compliance workflows and version control?

Yes, drift detection applies directly to documentation management, version control, and compliance workflows. It tracks external updates like new releases and closed issues to ensure local instruction files remain aligned with external documentation.