port-drift-detector

Detect cross-repository drift between paired code implementations using Git history and markdown ledgers.

Updated Aug 27, 2026
One-click install
npx skills add https://github.com/marvelousempire/ai-skills-library --skill port-drift-detector
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: port-drift-detector
Source: https://github.com/marvelousempire/ai-skills-library/tree/main/skills/project/brokerage-prototype/port-drift-detector
Command: npx skills add https://github.com/marvelousempire/ai-skills-library --skill port-drift-detector

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes scripts (resource) components.

What problem does it solve?

This Skill detects drift between paired repository implementations and automatically reports the status, eliminating manual checks and potential synchronization issues.

Core Features & Use Cases

  • Cross-Repo Drift Detection: Monitors paired repositories for inconsistencies and changes not documented in a markdown ledger.
  • Automated Reporting: Generates weekly reports with drift status updates without manual intervention.
  • Use Case: When managing a prototype and its canonical implementation in different repositories, use this Skill to ensure synchronization and receive weekly drift status updates.

Quick Start

Run the 'port-drift-detector' command to start drift detection between the 'brokerage-prototype' and the 'canonical' repository.

Frequently Asked Questions about port-drift-detector

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

FAQPage Schema
How do I detect cross-repo drift between paired code implementations?▼

Cross-repo drift detection is automated by analyzing Git history and markdown ledger data to identify undocumented inconsistencies between paired repositories. This eliminates manual checks and highlights synchronization issues in your codebase.

What is the best way to automate synchronization checks between a prototype and canonical repository?▼

Automated synchronization checks compare repository implementations against a markdown ledger to detect unreported drift. Running the port-drift-detector command monitors these paired repositories and generates status updates without manual intervention.

Can I generate automated weekly reports for Git repository drift?▼

Weekly reports for Git repository drift are generated automatically by the Skill. It monitors cross-repo inconsistencies and produces status updates, ensuring continuous synchronization validation for your development workflow.

Do I need a markdown ledger to track code drift across repositories?▼

A markdown ledger is required to track documented changes across repositories. The drift detection process compares actual Git history against this ledger data to flag any unreported inconsistencies between paired implementations.

How does markdown ledger data work with Git history for drift detection?▼

Git history and markdown ledger data work together by comparing committed code changes against documented updates. Any implementation mismatch found in the Git history that lacks a corresponding ledger entry is flagged as repository drift.