Why should I edit the main repo instead of the project folder?

The main repository is the single source of truth. Project folders are downstream working copies; if you edit them directly, your changes will be overwritten the next time the user syncs from the main repo.

Which KINTSUGI modules are supported by this workflow?

This skill specifically supports Kdecon, Kstitch, Kreg, and Kview2 notebook modules, as well as the core KINTSUGI source files.

Can Claude automate the synchronization process?

Yes, the skill provides specific shell command patterns (cp) to move files from the main repository subdirectories to the corresponding project folder paths.

What happens if a fix doesn't seem to work after application?

This skill helps diagnose if the fix was applied to the main repo but not synced, or if the user needs to restart their Jupyter kernel to clear the import cache.

KINTSUGI Repository Sync Workflow

Name: KINTSUGI Repository Sync Workflow
Author: smith6jt-cop

bysmith6jt-cop

Productivity & Workflow

Enforces a single-source-of-truth workflow for editing and synchronizing KINTSUGI notebook modules across project folders.

About

The KINTSUGI Repository Sync Workflow skill is designed for developers managing complex, multi-project environments where shared notebook modules like Kdecon, Kstitch, and Kreg are used. It ensures that all code modifications happen in the main central repository first, preventing the common issue where direct edits in project folders are accidentally overwritten during synchronization. This skill helps Claude maintain environment integrity, provides correct sync commands, and reminds users to refresh Jupyter kernels after updates.

Key Features

Maps specific component paths for Kdecon, Kstitch, Kreg, and Kview2
Includes best-practice reminders for Jupyter kernel management
Identifies and resolves synchronization conflicts during development
Provides automated shell commands for syncing source to project folders
0 GitHub stars
Enforces 'Main Repo First' editing logic to prevent data loss

Use Cases

Ensuring bug fixes are propagated from source to active project folders
Updating shared codebase modules across multiple research environments
Preventing accidental overwrites during multi-root workspace development

About

Key Features

Maps specific component paths for Kdecon, Kstitch, Kreg, and Kview2
Includes best-practice reminders for Jupyter kernel management
Identifies and resolves synchronization conflicts during development
Provides automated shell commands for syncing source to project folders
0 GitHub stars
Enforces 'Main Repo First' editing logic to prevent data loss

Use Cases

Ensuring bug fixes are propagated from source to active project folders
Updating shared codebase modules across multiple research environments
Preventing accidental overwrites during multi-root workspace development