template-drift

Compare local .adlc/templates/ files against canonical toolkit templates and output a per-file drift summary.

159|41|Updated Mar 18, 2026
One-click install
npx skills add https://github.com/atelier-fashion/adlc-toolkit --skill template-drift
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: template-drift
Source: https://github.com/atelier-fashion/adlc-toolkit/tree/main/template-drift
Command: npx skills add https://github.com/atelier-fashion/adlc-toolkit --skill template-drift

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This skill detects drift between a project's local .adlc/templates/ copies and the canonical templates shipped with the toolkit, clarifying which changes are intentional vs. accidental.

Core Features & Use Cases

  • Enumerate templates present in the local project and toolkit to identify missing or extra files.
  • Diff templates to quantify changes and produce a per-file drift summary.
  • Classify drift as intentional vs accidental and provide actionable recommendations.
  • Generate a detailed drift report and optional reconciliation steps for project teams.

Quick Start

Run /template-drift to compare local .adlc/templates/ with toolkit templates and review the per-file drift report.

Frequently Asked Questions about template-drift

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

FAQPage Schema
How do I detect template drift between my project and the toolkit?

Template drift is detected by comparing your project's local .adlc/templates/ copies against the canonical toolkit templates. Running the check enumerates missing or extra files, diffs content changes, and outputs a per-file drift summary with actionable recommendations.

What is template drift and how does it affect my repository?

Template drift occurs when local project template copies diverge from canonical toolkit templates, creating ambiguity between intentional customizations and accidental changes. Identifying this drift clarifies which modifications are deliberate and which need reconciliation to maintain project consistency.

Can I check template drift for a single specific template file?

Yes, you can scope the template drift check to a single template by passing an argument. This limits the enumeration and diff comparison to that specific template, providing a focused per-file drift summary instead of scanning the entire repository.

What do I need to run a local template diff against the toolkit?

Running a template diff requires local .adlc/templates/ copies present in the project and a reachable toolkit templates path. Without these prerequisites, the comparison cannot enumerate files or quantify the changes between the project and the canonical templates.

How do I reconcile accidental changes found in my project templates?

To reconcile accidental changes, review the generated per-file drift summary which classifies drift as intentional or accidental. Use the provided optional reconciliation steps to align local .adlc/templates/ copies back to the canonical toolkit templates where needed.