qrspi-sync-copilot

Name: qrspi-sync-copilot
Availability: InStock
Author: Lotea

Regenerate GitHub Copilot artifacts from Claude Code source mappings.

2|Updated Jun 6, 2026

Search Tags:#workflow #deterministic #OpenSpec #claude-code #mapping #copilot #artifact-sync

Ready to run

npx skills add https://github.com/lotea-be/qrspi --skill qrspi-sync-copilot

💬 Prompt for ChatGPT / Claude Chat▼

Please help me install this Agent Skill.
Skill: qrspi-sync-copilot
Source: https://github.com/lotea-be/qrspi/tree/main/.claude/skills/qrspi-sync-copilot
Command: npx skills add https://github.com/lotea-be/qrspi --skill qrspi-sync-copilot

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Regenerate the GitHub Copilot artifacts (copilot/) from the Claude Code source of truth (claude/), ensuring the generated outputs faithfully reflect the canonical mappings, frontmatter rules, and body mechanics.

Core Features & Use Cases

Deterministic regeneration: the sync runs via sync-copilot.mjs, performing rewriteAll text rewrites and per-output fixes to keep copilot/ in sync with claude/.
Wholesale refresh: it drops and recreates copilot/ to reflect current claude/ artifacts, preventing drift between sources of truth.
Fidelity management: it documents known fidelity gaps and consistent OpenSpec-driven transformations to minimize manual edits.

Quick Start

Run /qrspi-sync-copilot to regenerate the Copilot artifacts from Claude Code.

Frequently Asked Questions about qrspi-sync-copilot

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

FAQPage Schema

How do I sync Copilot artifacts from a Claude Code source of truth?▼

To sync Copilot artifacts, run a wholesale regeneration that drops and recreates the copilot/ directory from claude/ files. This applies deterministic rewrite rules and frontmatter mapping to align generated outputs with canonical sources.

Why do my generated Copilot artifacts drift from Claude Code mappings?▼

Generated Copilot artifacts drift when manual edits bypass canonical mappings. Wholesale regeneration drops and recreates copilot/ from the claude/ source of truth, applying deterministic rewrite rules to prevent source divergence.

What is deterministic artifact regeneration for Claude-driven workflows?▼

Deterministic artifact regeneration is a sync process that rewrites text and applies per-output fixes to faithfully reproduce Copilot artifacts. It ensures generated files reflect OpenSpec-driven transformations from the canonical Claude Code source.

Can I apply frontmatter mapping and path rewrites when regenerating Copilot files?▼

Yes, regenerating Copilot files applies frontmatter mapping and path rewrites automatically. The sync process uses deterministic rules to ensure generated outputs match the canonical Claude Code structure and metadata.

Does syncing Copilot artifacts require manual fixes after generation?▼

Syncing Copilot artifacts minimizes manual fixes by documenting known fidelity gaps and applying per-output fixes during generation. This OpenSpec-driven transformation ensures the wholesale refresh stays aligned with the Claude source.

What are the limitations of wholesale regeneration for copilot/ directories?▼

Wholesale regeneration drops and recreates the entire copilot/ directory, meaning any manual edits made directly to Copilot artifacts are overwritten. Known fidelity gaps are documented, but manual changes outside the claude/ source will not persist.