sync-check

Detect mismatches between design documents under .claude/ and implemented code.

Updated Apr 27, 2026
One-click install
npx skills add https://github.com/shaul1991/shaul-plugin --skill sync-check-shaul1991
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: sync-check
Source: https://github.com/shaul1991/shaul-plugin/tree/main/claude-code-plugin/project-lifecycle/skills/sync-check
Command: npx skills add https://github.com/shaul1991/shaul-plugin --skill sync-check-shaul1991

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

The Sync Check skill systematically detects discrepancies between design documents stored under .claude/ and the actual codebase, preventing drift and maintaining a single source of truth.

Core Features & Use Cases

  • Detects mismatches between documentation and code (API specs, data models, and conventions) and suggests concrete updates.
  • Generates drift reports with severity levels and recommended remediation to guide teams.
  • Integrates into QA and CI workflows to enforce document-code alignment across sprints and releases.

Quick Start

Run the sync-check process to compare design documents with code and generate drift reports.

Frequently Asked Questions about sync-check

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

FAQPage Schema
How do I detect documentation drift between my design docs and codebase?

Documentation drift is detected by systematically comparing design documents stored under .claude/ against the actual codebase to identify mismatches in API specs, data models, and implementation conventions, then generating structured drift reports.

What is the best way to keep API specs and data models in sync with evolving code?

Keeping API specs and data models in sync requires automatic drift detection that compares design documents against implemented code, generates severity-level reports, and provides concrete update recommendations to maintain a single source of truth.

Can I integrate drift detection into my CI workflow to enforce document-code alignment?

Drift detection integrates into QA and CI workflows to enforce document-code alignment across sprints and releases by automatically comparing .claude/ design documents with the codebase and generating artifact reports for remediation.

How do I generate a drift report for mismatches between implementation conventions and documentation?

Generating a drift report involves running a sync-check process that compares design documents with implemented code, producing structured reports with severity levels and recommended remediation steps to guide document-code alignment.

What types of documentation mismatches can drift detection identify in evolving architectures?

Drift detection identifies mismatches across evolving architectures, data models, UI specs, API specs, and implementation conventions by comparing .claude/ design documents against the actual codebase to prevent discrepancies.

Does sync-check work for projects with evolving data models and UI specs?

Sync-check works for projects with evolving architectures, data models, and UI specs by detecting discrepancies between .claude/ design documents and the implemented codebase, providing automatic drift detection and artifact generation.