skills.rest
kanno321-create
kanno321-createCOMMUNITY
Explore all skills by this author →
GitHub

drift-detection

Scan agent instructions for drift and update CONFLICT_MAP.md.

Updated Aug 23, 2026
Search Tags:#monitoring#drift-detection#drift#conflict#agent-loop#pattern-scan#conflict-map
One-click install
npx skills add https://github.com/kanno321-create/shorts_studio --skill drift-detection-kanno321-create
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: drift-detection
Source: https://github.com/kanno321-create/shorts_studio/tree/main/.claude/skills/drift-detection
Command: npx skills add https://github.com/kanno321-create/shorts_studio --skill drift-detection-kanno321-create

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Drift between legacy and current studio instructions can cause conflicting directives and looping behavior. This skill scans for such inconsistencies across the agent ecosystem and updates the CONFLICT_MAP.md to reflect the current state, helping keep workflows stable.

Core Features & Use Cases

  • Pattern-based scanning across studio instructions to identify stale or conflicting directives.
  • Automatically update .planning/codebase/CONFLICT_MAP.md to prevent recurring misbehavior.
  • Triggered on demand or on a scheduled cadence to maintain alignment between agents and guidelines.

Quick Start

Trigger drift detection to scan for outdated vs current directives and refresh CONFLICT_MAP.md.

Frequently Asked Questions about drift-detection

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

FAQPage Schema
How do I detect instruction drift in agent loops?▼

Instruction drift in agent loops is detected by running a pattern-based scan against .claude/drift_patterns.json to identify conflicting directives and update .planning/codebase/CONFLICT_MAP.md.

Why does my agent exhibit looping behavior and conflicting directives?▼

Agent looping behavior and conflicting directives usually occur when drift exists between legacy and current studio instructions, causing misalignment across the agent ecosystem that requires a pattern scan to resolve.

How do I update CONFLICT_MAP.md during a periodic studio audit?▼

To update CONFLICT_MAP.md during a periodic studio audit, trigger drift detection on a scheduled cadence to scan for outdated directives and automatically refresh the conflict map.

Can I integrate drift detection into a larger orchestration workflow?▼

Yes, drift detection supports periodic execution with optional integration into a larger orchestration workflow to maintain alignment between agents and guidelines during ongoing studio development.

What is the best way to maintain alignment between agents and guidelines?▼

The best way to maintain alignment between agents and guidelines is to run scheduled drift detection scans that identify stale directives across the studio and record current inconsistencies in CONFLICT_MAP.md.

Related Skills

Explore More Software Engineering Skills→
phillippelevidadphillippelevidad

pattern-governance

Discover recurring code patterns and generate ADRs with agent directives.

Community
Advanced
gmickelgmickel
674

flow-next-audit

Audit .flow/memory entries against the current codebase for stale guidance.

Community
Advanced
filipexyzfilipexyz
6

heartbeat-manager

Manage periodic execution cycles for AI agents using configuration files.

Community
Intermediate
PeiwvyPeiwvy

neat-freak

Reconcile agent memory and project documentation with the current codebase state.

Community
Advanced