skills.rest
smith6jt-cop
smith6jt-copCOMMUNITY
Explore all skills by this author →
GitHub

repo-project-sync-workflow

Enforce main repository edits before syncing shared notebook modules to project folders.

3|Updated Dec 10, 2025
Search Tags:#version control#code management#project workflow#repo sync
One-click install
npx skills add https://github.com/smith6jt-cop/Skills_Registry --skill repo-project-sync-workflow
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: repo-project-sync-workflow
Source: https://github.com/smith6jt-cop/Skills_Registry/tree/main/plugins/kintsugi/repo-project-sync-workflow/skills/repo-project-sync-workflow
Command: npx skills add https://github.com/smith6jt-cop/Skills_Registry --skill repo-project-sync-workflow

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This Skill establishes the correct workflow for editing shared notebook modules, ensuring your changes persist across project updates and user sync operations.

Frequently Asked Questions about repo-project-sync-workflow

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

FAQPage Schema
How do I prevent my project folder changes from being overwritten during repository sync?▼

Prevent overwrites by making all edits in the main repository first, then syncing to project folders. This ensures the main repository remains the single source of truth and project changes are never lost during sync operations.

What's the correct workflow for editing shared notebook modules across multiple projects?▼

Edit shared modules like Kdecon, Kstitch, Kreg, and Kview2 exclusively in the main repository, then sync changes to project folders. This workflow prevents conflicting edits and ensures consistent module versions across all projects.

Why do I need to restart the kernel after syncing repository changes to project folders?▼

Kernel restarts may be required after syncing because updated notebook modules need to be reloaded into memory. Restarting ensures your project uses the latest code from the main repository without stale cached imports.

Can I edit code directly in project folders or must changes go through the main repository?▼

All edits must go through the main repository first. Project folders are overwritten on sync, so direct edits there will be lost. The main repository is the single source of truth for all shared code.

How does repository sync work in a multi-project setup?▼

Repository sync propagates changes from the main repository to all project folders, overwriting project-folder versions with main-repo versions. This enforces a centralized workflow where the main repository controls all shared module updates.

Related Skills

Explore More Software Engineering Skills→
michalstanieckomichalstaniecko

acf-fields

Centralize WordPress ACF field groups using Local JSON files for version control.

Community
Intermediate
JamesFincherJamesFincher

jupyter-live-kernel

Execute Python code against a persistent live Jupyter kernel.

Community
Intermediate
typeclawtypeclaw
53

typeclaw-monorepo

Organize reusable code modules into a monorepo structure within an agent folder.

Official
Basic
mostafasudomostafasudo
3

ship

Automate code deployment by merging branches, running tests, and creating pull requests.

Community
Intermediate