Sync Config with Upstream Sample for Openclaw

Safely refreshes reference comments and URLs from an upstream sample without changing the user's live configuration.

j3ffyang
v1.0.0
Sep 17, 2026
0
122
0

Install & Download

1. ClawHub CLI

The fastest way to install a skill directly from the registry.

npx clawhub@latest install sync-config-with-sample

2. Manual Installation

Copy the skill folder to one of these locations

Global
~/.openclaw/skills/
Workspace
<project>/skills/

Priority: Workspace > Local > Bundled

3. Prompt Installation

Copy this prompt to OpenClaw to install it automatically.

Help me install sync-config-with-sample using Clawhub. If Clawhub is not installed, install it first (npm i -g clawhub).

Prefer to download?

Get the raw skill files in a ZIP archive.

What is Sync Config with Upstream Sample?

This Openclaw Skills workflow synchronizes a production configuration file with the latest upstream sample while preserving every user-controlled value, binding, active block, and feature. It treats the sample as an immutable baseline and removes reference noise from diffs by copying only inert comments, section references, and documentation URLs.

The skill uses a disciplined diff-and-classify process to separate reference changes from genuine configuration differences. Ambiguous hunks are investigated against upstream commits, documentation, and the installed software version before any edit is made, making it useful for safely maintaining files such as Hyprland configurations.

Sync Config with Upstream Sample Use Cases

  • Refresh a device-specific production config against a newly downloaded, date-stamped upstream sample.
  • Remove outdated wiki URLs or explanatory comment differences from configuration diffs.
  • Preserve custom values, keybinds, active startup blocks, environment settings, and added features.
  • Determine whether a suspicious change is an upstream rename, deprecation, typo fix, or real user configuration.
  • Prepare a clean reviewable diff before upgrading the underlying application.
  • Maintain archived live configuration files such as hyprland.lua.gpd beside upstream samples such as hyprland.lua.260917.

How Sync Config with Upstream Sample Works

  1. Identify the production file, typically a device-suffixed file such as *.gpd, and the newest dated upstream sample.
  2. Declare both protected sets: never modify the sample, and never alter actual configuration in the production file.
  3. Run a file diff to expose every difference between the production config and the sample.
  4. Classify each diff hunk as Reference, Config, or Ambiguous.
  5. Copy reference-only comments, headers, wording, and URLs verbatim from the sample into the production file.
  6. Leave configuration hunks untouched and record them as the intended surviving differences.
  7. Investigate ambiguous lines using the sample, upstream GitHub commits, pull requests, issues, documentation, and the installed package version.
  8. Ask for a decision before changing any ambiguous configuration-like hunk.
  9. Apply exact, unique edits that do not overlap executable configuration code.
  10. Re-run diff and verify that the sample is unchanged, user configuration survived, and only legitimate configuration differences remain.

Sync Config with Upstream Sample Setup

No package installation is required. Prepare the two files locally and ensure standard diff tooling is available. Optional version checks require the relevant application's CLI and package manager.

  1. Place the live or archived production config and the freshly downloaded upstream sample in the same working directory.
  2. Confirm the production file uses the device suffix and the sample uses a clear date-based suffix.
  3. Ensure the upstream sample is a clean download; never edit it in place.
  4. Review the installed application's version when an ambiguous rename or compatibility question arises.
diff hyprland.lua.<device> hyprland.lua.<date>

hyprctl version

pacman -Q <pkg>

Use the available editing mechanism only for exact reference-line replacements. Before completion, preserve or commit a backup of the production file so the final diff can be reviewed safely.

Sync Config with Upstream Sample Data Schema & Taxonomy

The skill organizes configuration data around two immutable roles:

File or data element Role Handling
*.gpd or device-suffixed file Production configuration Preserve values, binds, active blocks, environment settings, and custom features
Dated *.2609xx file Upstream reference sample Read-only; never modify in place
Diff hunks Change units Classify as Reference, Config, or Ambiguous
Reference comments Inert metadata Copy exact wording, whitespace, URLs, and section headers from the sample
Configuration code Operational data Leave untouched and report as a surviving diff
Ambiguous entries Unresolved compatibility data Investigate upstream history and installed-version support before editing

The metadata taxonomy is intentionally conservative: Reference changes are applied, Config changes are retained, and Ambiguous changes require evidence and user approval. The generated artifact is the updated production file plus a final diff and a survival list documenting all real configuration differences.

Sync Config with Upstream Sample Advanced Features

  • Immutable sample protection prevents accidental edits to the re-downloadable upstream baseline.
  • Exact unique-string editing preserves whitespace and minimizes unintended changes.
  • Three-way hunk classification separates documentation noise from executable configuration.
  • Ground-truth investigation checks upstream GitHub PRs, commits, issues, wiki pages, and installed versions.
  • Compatibility-aware recommendations account for renamed or deprecated settings and version-specific support.
  • User approval gates ambiguous edits instead of silently applying potentially breaking changes.
  • Final verification confirms sample integrity, configuration survival, and removal of reference or URL noise.
  • The workflow scales across device-specific files and recurring upstream sample refreshes as part of Openclaw Skills automation.

SKILL.md


Loading

Related Openclaw Skills

METADATA

Github Stars: 0
forks: 0

Featured*