code-sync-advisor

Detect code drift and enforce pattern conformance before code review.

1|Updated Mar 4, 2026
One-click install
npx skills add https://github.com/Prathmesh2000/cursor_agent-orchestrator --skill code-sync-advisor
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: code-sync-advisor
Source: https://github.com/Prathmesh2000/cursor_agent-orchestrator/tree/main/agent-system/skills/code-sync-advisor
Command: npx skills add https://github.com/Prathmesh2000/cursor_agent-orchestrator --skill code-sync-advisor

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Identify code drift and enforce pattern conformance to keep a codebase consistent as it evolves.

Core Features & Use Cases

  • Structural Sync: verify file and folder placement, and naming conventions.
  • Pattern Sync: compare new or modified code against Pattern Cards for controllers, services, and models.
  • Import/Dependency Sync: ensure import paths and dependencies align with existing conventions.
  • Naming Sync: enforce camelCase, PascalCase, and consistent export patterns.
  • API/Module Contract Sync: validate API contracts and error/response patterns against project standards.
  • Use Case: When adding a new OrderService.ts, the skill checks placement, naming, and adherence to the project pattern.
  • Quick checks at PR-time: flag drift before code review to reduce review cycles.

Quick Start

Run the Sync Check before submitting a PR to verify structural and pattern conformance.

Frequently Asked Questions about code-sync-advisor

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

FAQPage Schema
How do I detect code drift before submitting a pull request?

Code drift is detected by running a sync check against a Codebase Map and Pattern Cards before code review, verifying that new or modified code conforms to existing structural, pattern, and import conventions.

What is pattern conformance checking for controllers, services, and models?

Pattern conformance checking validates new or modified code against predefined Pattern Cards to ensure structural placement, naming conventions, and style consistency across controllers, services, and models within a repository.

How do I enforce naming conventions and import sync across a codebase?

Naming and import sync are enforced by checking new code against existing repository conventions, validating camelCase and PascalCase usage, export patterns, and ensuring import paths align with project standards.

Can I validate API contracts and error response patterns against project standards?

Yes, API and module contract sync validates new API contracts and error or response patterns against existing project standards to ensure consistency before code review cycles begin.

Does code drift detection work for adding new service files like OrderService?

Yes, adding a new file like OrderService triggers checks for correct folder placement, naming conventions, and adherence to the project's service pattern to prevent codebase drift.

What is the best way to reduce code review cycles caused by inconsistent code patterns?

Running a structural and pattern sync check before submitting a PR flags code drift early, reducing review cycles by ensuring naming, imports, and file placement conform to established conventions beforehand.