gpd-sync-state

Reconciles diverged STATE.md and state.json into a single source of truth.

Updated Mar 15, 2026
One-click install
npx skills add https://github.com/MichaelsEngineering/get-physics-done-test --skill gpd-sync-state-michaelsengineering
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: gpd-sync-state
Source: https://github.com/MichaelsEngineering/get-physics-done-test/tree/main/.agents/skills/gpd-sync-state
Command: npx skills add https://github.com/MichaelsEngineering/get-physics-done-test --skill gpd-sync-state-michaelsengineering

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Reconcile diverged STATE.md and state.json after manual edits or corruption, ensuring a single source of truth for project state.

Core Features & Use Cases

  • Keeps STATE.md and state.json in sync by merging human-readable state with machine-parsed state.
  • Supports conflict detection, recency analysis, and preservation of JSON-only fields.
  • Suitable for maintenance workflows in Codex-GPD projects and reproducible research pipelines.

Quick Start

Run the sync-state workflow to reconcile STATE.md and state.json and commit the results.

Frequently Asked Questions about gpd-sync-state

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

FAQPage Schema
How do I reconcile diverged STATE.md and state.json files in my project?

Reconcile STATE.md and state.json by running a sync-state workflow that compares both files, resolves conflicts using recency analysis, preserves JSON-only fields, and commits the merged results to restore a single source of truth.

What is state.json and STATE.md reconciliation used for in reproducible research pipelines?

State.json and STATE.md reconciliation restores a single source of truth for project state after manual human edits cause data divergence in reproducible research pipelines and Codex-GPD maintenance workflows.

Does state sync preserve machine-parsed JSON fields when merging with human-readable markdown?

Yes, state sync preserves JSON-only fields during reconciliation. It merges human-readable markdown state with machine-parsed state while ensuring specific JSON fields survive the recency-based resolution process.

What is the best way to fix state.json and STATE.md conflicts after manual edits?

The best way to fix state.json and STATE.md conflicts is to apply recency-based resolution, which compares diverged files, determines the most recent valid changes, and commits a reconciled state to eliminate discrepancies.

Why does my state.json file stop matching STATE.md after I edit it manually?

Your state.json stops matching STATE.md because manual human edits cause divergence. Running a reconciliation workflow detects this divergence and merges both files back into a single source of truth.