skills.rest
CharlieGreenman
CharlieGreenmanCOMMUNITY
Explore all skills by this author →
GitHub

gpd-sync-state

Merge diverged STATE.md and state.json while preserving JSON-only fields.

1|Updated Mar 29, 2026
Search Tags:#workflow#validation#state-management#merge-conflicts#state-sync#state-json#state-md
One-click install
npx skills add https://github.com/CharlieGreenman/roomtemp-superconductor-gpd --skill gpd-sync-state
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: gpd-sync-state
Source: https://github.com/CharlieGreenman/roomtemp-superconductor-gpd/tree/main/.agents/skills/gpd-sync-state
Command: npx skills add https://github.com/CharlieGreenman/roomtemp-superconductor-gpd --skill gpd-sync-state

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Reconcile diverged STATE.md and state.json after manual edits or corruption, ensuring both representations reflect the same project state.

Core Features & Use Cases

  • Detect and reconcile divergences between the human-readable STATE.md and machine-friendly state.json.
  • Preserve JSON-only fields (e.g., convention_lock, intermediate_results, approximations, propagated_uncertainties) while updating core fields.
  • Support automatic or interactive resolution via the official workflow and recency analysis.

Quick Start

Run the sync-state workflow to reconcile STATE.md and state.json, optionally specifying --prefer md or --prefer json to choose the truth source.

Frequently Asked Questions about gpd-sync-state

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

FAQPage Schema
How do I sync STATE.md with state.json after manual edits?▼

To sync STATE.md with state.json, run the sync-state workflow which detects divergences, applies recency analysis, and merges human-readable state with machine state while preserving JSON-only fields.

What happens to JSON-only fields when reconciling state files?▼

When reconciling state files, JSON-only fields like convention_lock, intermediate_results, approximations, and propagated_uncertainties are preserved while core state fields are aligned between both representations.

When do I need state synchronization for my workflow?▼

State synchronization is needed when manual edits, corruption, or partial updates create inconsistencies between your human-readable STATE.md and machine-friendly state.json project representations.

Can I choose which file to prefer during state.json and STATE.md conflict resolution?▼

Yes, during conflict resolution you can specify --prefer md or --prefer json to choose the truth source when merging diverged state files via the official workflow.

What's the best way to fix state.json and STATE.md merge conflicts?▼

The best way to fix merge conflicts is running the sync-state workflow, which handles detection, recency analysis, conflict presentation, and validation before committing reconciled files.

Related Skills

Explore More Software Engineering Skills→
MichaelsEngineeringMichaelsEngineering

gpd-sync-state

Reconcile diverged STATE.md and state.json files after manual edits or corruption.

Community
Advanced
cursor-jscursor-js

git-commit

Analyze code diffs and generate Conventional Commits messages.

Official
Intermediate
chronista-clubchronista-club
2

Sycamore - Rust Reactive WebUI Framework

Automate GitHub PRs, issues, and merge-conflict handling via the GitHub CLI.

Official
Advanced
CharGrnmnCharGrnmn
1

gpd-sync-state

Reconcile STATE.md and state.json project state files.

Community
Advanced