check-mirrored-artifacts

Verify byte-identical cross-repo file copies and re-run generators to detect stale generated artifacts.

5|1|Updated Aug 18, 2023
One-click install
npx skills add https://github.com/thpoll83/PolyKybdHost --skill check-mirrored-artifacts-thpoll83
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: check-mirrored-artifacts
Source: https://github.com/thpoll83/PolyKybdHost/tree/main/.claude/skills/check-mirrored-artifacts
Command: npx skills add https://github.com/thpoll83/PolyKybdHost --skill check-mirrored-artifacts-thpoll83

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes scripts (resource) components.

What problem does it solve? Files mirrored across multiple repositories and artifacts produced by generators drift silently: copies diverge with no build or test to flag it, and generated files keep looking current even after their generator's input path stops resolving. This Skill detects both failure modes before they cause wrong language decoding, mislabelled editor tabs, or stale release artifacts. ## Core Features & Use Cases - Mirror drift detection: Runs check_mirrors.sh to compare eleven file pairs across the qmk_firmware, PolyKybdHost, and polykybd-ctnd repos, printing ok/DRIFTED/MISSING per pair and exiting non-zero on any drift. - Generated artifact validation: Re-runs each generator (generate_fonts.py --check, preview_doctor.py, cog) and confirms the output still matches the committed artifact and that input paths still resolve. - Guided re-sync: When drift is found, directs you to pick the canonical side deliberately, copy with cp, re-run the check, and record the copy direction in the commit. - Use Case: Before a PolyKybd release, run the mirror check to confirm the frozen ISO language table, font manifests, and the nine mirrored skills are byte-identical across all three repos, then re-run the font generator to prove the committed artifacts are not stale. ## Quick Start Ask the assistant to run the check-mirrored-artifacts skill to verify all mirrored files and generated artifacts are in sync across the PolyKybd repos.

Frequently Asked Questions about check-mirrored-artifacts

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

FAQPage Schema
How do I check if mirrored files have drifted across repositories?

Run bash .claude/skills/check-mirrored-artifacts/check_mirrors.sh. It compares eleven file pairs across the qmk_firmware, PolyKybdHost, and polykybd-ctnd repos with cmp, prints ok or DRIFTED per pair, and exits non-zero if anything drifted or is missing.

How do I detect stale generated files in a repository?

Re-run each artifact's generator rather than comparing files, since a generated artifact has no counterpart to diff. For example run python3 fonts/generate_fonts.py --check and confirm the generator's input path still resolves, because a renamed input fails silently.

What files does the PolyKybd mirror check compare?

It compares the frozen iso_lang_country.py table across three repos, the noto-fonts.yaml catalogue, fontpack_render_settings.json, lang_flags.json, and the SKILL.md files of nine mirrored skills shared between the qmk and host repositories.

What should I do when the mirror check reports drift?

Pick the correct side deliberately rather than by timestamp: the qmk copy is canonical for the ISO table, while mirrored skills should be merged by reading both. Copy with cp, re-run the check, and state the copy direction in the commit message.

Why can cmp not detect a stale generated artifact?

A generated artifact has no counterpart to compare against, so byte comparison is meaningless. The only valid check is whether its generator still runs and resolves its input path, since a generator whose input was renamed silently writes nothing new.