sync-project

Reconcile configuration drift between local JSON project definitions and remote backend systems.

5|2|Updated Jun 14, 2026
One-click install
npx skills add https://github.com/dyzsasd/dev-loop --skill sync-project-dyzsasd
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: sync-project
Source: https://github.com/dyzsasd/dev-loop/tree/main/skills/sync-project
Command: npx skills add https://github.com/dyzsasd/dev-loop --skill sync-project-dyzsasd

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This skill resolves configuration drift between local workspace settings and remote project management backends like Linear or the dev-loop hub, preventing synchronization errors and stale project states.

Core Features & Use Cases

  • Drift Detection: Automatically identifies discrepancies in project names, archive status, and label sets between local config and the backend.
  • Safe Reconciliation: Provides a guided, operator-confirmed workflow to update local configs or backend settings without accidental overwrites.
  • Use Case: When a project is renamed in Linear, this skill detects the mismatch and prompts the user to update the local dev-loop.json file to match the new backend reality.

Quick Start

Invoke the sync-project skill to reconcile the current workspace project with its backend configuration.

Frequently Asked Questions about sync-project

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

FAQPage Schema
How do I fix configuration drift between local workspace settings and Linear?▼

To fix configuration drift between local workspace settings and Linear, you can use a reconciliation process that fetches backend state, compares it against local JSON configurations, and applies operator-confirmed updates to ensure synchronization.

What is project configuration reconciliation in a dev-loop?▼

Project configuration reconciliation in a dev-loop is the process of aligning local project definitions with remote backend project management systems to prevent synchronization errors and stale project states.

How do I synchronize local JSON configurations with a remote project management backend?▼

You synchronize local JSON configurations with a remote backend by fetching the backend state, detecting discrepancies in project names or label sets, and applying guided updates to align the local files.

Can I automatically detect label taxonomy mismatches between my local config and the backend?▼

Yes, you can automatically detect label taxonomy mismatches by comparing local JSON configurations against the backend state. The system identifies discrepancies and prompts for operator-confirmed updates to ensure synchronization.

Does synchronizing project configs with a backend require manual confirmation before overwriting?▼

Yes, synchronizing project configs with a backend requires manual confirmation. The process uses a guided, operator-confirmed workflow to update local configs or backend settings without accidental overwrites.

What happens when a project is renamed in Linear but my local dev-loop.json is outdated?▼

When a project is renamed in Linear but your local dev-loop.json is outdated, the reconciliation process detects the mismatch and prompts you to update the local file to match the new backend reality.