claude-infra-sync

Analyze repository files and documentation for inconsistencies and version mismatches.

Updated Aug 23, 2026
One-click install
npx skills add https://github.com/TimChild/PaperTrade --skill claude-infra-sync
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: claude-infra-sync
Source: https://github.com/TimChild/PaperTrade/tree/main/.claude/skills/claude-infra-sync
Command: npx skills add https://github.com/TimChild/PaperTrade --skill claude-infra-sync

SYSTEM DOCUMENTATION & REQUIREMENTS

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

What problem does it solve?

This Skill identifies discrepancies between Claude’s infrastructure files and the actual repository state, helping teams maintain synchronization and detect drift.

Core Features & Use Cases

  • Drift Detection: Checks for stale paths, broken links, outdated test counts, and version mismatches.
  • Repository Consistency: Verifies the alignment between documentation, agent and skill inventories, and code references.
  • Use Case: During project updates, run this Skill to ensure that all agent files, skills, and documentation are aligned, preventing deployment issues caused by drift.

Quick Start

Execute the sync check script in the .claude/skills/claude-infra-sync/ directory to generate a detailed drift report.

Frequently Asked Questions about claude-infra-sync

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

FAQPage Schema
How do I detect infrastructure drift in my repository?

Infrastructure drift is detected by analyzing repository files and documentation to identify inconsistencies, missing references, and version mismatches, ensuring your project components remain synchronized and accurate.

How do I validate directory references and dependency versions in my project?

You validate directory references and dependency versions by running a sync check script that compares your documentation against the actual repository state, identifying broken links and outdated test counts to maintain project integrity.

What is infrastructure drift and when should I check for it?

Infrastructure drift occurs when documentation and code references become misaligned from the actual repository state. You should check for it during project updates to prevent deployment issues caused by stale paths or outdated inventories.

Can I verify API endpoint consistency across project components?

Yes, you can verify API endpoint consistency. The Skill validates API endpoints alongside directory references and dependency versions to maintain integrity and ensure documentation accurately reflects the current infrastructure state.

Does this repository validation tool work without external dependencies?

Yes, this repository validation tool works without external dependencies. It operates directly on your repository files and documentation to perform drift detection and consistency checks natively.

What are the limitations of automated documentation checks for drift detection?

Automated documentation checks for drift detection are limited to analyzing repository files, directory references, dependency versions, and API endpoints explicitly present in your codebase, meaning they cannot validate external or undocumented infrastructure.