dxsync

Refresh Dex project context, rules, and repo memory after codebase changes.

3|2|Updated Jan 25, 2026
One-click install
npx skills add https://github.com/mitchellfyi/dex --skill dxsync
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: dxsync
Source: https://github.com/mitchellfyi/dex/tree/main/skills/dxsync
Command: npx skills add https://github.com/mitchellfyi/dex --skill dxsync

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Dex project context, rules, and repo memory can drift out of sync as the codebase changes, leading to outdated workflow configurations, incorrect quality gates, and inefficient ticket processing that wastes developer time.

Core Features & Use Cases

  • Automated Context Refresh: Re-analyzes the entire codebase to update Dex's project context, rules, and durable repo memory with the latest verified patterns.
  • Drift Detection: Supports --dry-run and --trace-retrieval modes to identify context drift without modifying any files, perfect for pre-flight checks.
  • Use Cases: Run after dx init to build initial context, after repeated review comments or CI failures reveal new repo patterns, or before background maintenance runs that require up-to-date workflow context.

Quick Start

Use the dxsync skill to refresh your Dex project context and repo memory after recent codebase changes.

Frequently Asked Questions about dxsync

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

FAQPage Schema
How do I refresh stale project context and repo memory after codebase changes?

To refresh stale repo memory, you can re-analyze the entire codebase to update Dex project context, rules, and durable memory with the latest verified patterns. This resolves outdated workflow configurations and inefficient ticket processing.

Can I check for context drift in my codebase without modifying any files?

Yes, you can detect context drift without modifying files by using dry-run and retrieval tracing modes. These pre-flight checks identify outdated project context and rules, generating a detailed sync report of all drifted files.

When should I run a repo memory sync for my project?

You should run a repo memory sync after initial context scaffolding, following repeated review comments or CI failures that reveal new patterns, or before background maintenance runs that require up-to-date workflow context.

How does codebase analysis promote new patterns into project context?

Codebase analysis promotes new patterns by re-verifying observations against the latest code, then writing those verified patterns into reviewable .dex/ context files. This generates a detailed sync report of all modified files.

What is the best way to fix outdated workflow configurations caused by codebase evolution?

The best way to fix outdated workflow configurations is to perform an automated context refresh that re-analyzes the codebase and updates durable repo memory. This corrects quality gates and prevents wasted developer time.

Are there limitations to using dry-run mode for context drift detection?

The limitation of dry-run mode for context drift detection is that it only reports drift without applying changes. You must run the full sync separately to update the .dex/ context files and repo memory.