OpenClaw GitHub Config Impact Analysis

Problem

When configuration lives in GitHub repositories—under config/, 配置文件/, or scattered YAML/properties files—engineers often have to rely on tribal knowledge to explain keys, estimate change impact, or compare environments. A local checkout may also be stale, so conclusions can be based on the wrong snapshot. This skill turns locating, syncing, and explaining configuration changes into an explicit workflow.

How It Works and Limits

• Project layout: parses owner/repo from the link and creates {workspace}/{repo}/ by default.
• Dated snapshots: each successful sync creates a YYYY-MM-DD directory, preserving history and writing .openclaw-config-state.json with commit_sha, remote_ref, and latest_version_dir.
• Freshness first: before answering, it compares the remote branch tip against local state; if mismatched, it re-downloads config files and paired *字段说明*.md notes before analysis.
• Parameter analysis: flattens YAML into dotted keys, aligns them with field documentation, then explains key meaning, environment differences, and risk.

Private repositories need a token. If the remote cannot be checked, the skill should say the snapshot may be stale. Secrets, passwords, and tokens should not be printed in full.