sync-back

Copy modified local ChipAgent project files back to the source repository.

2|Updated Mar 16, 2026
One-click install
npx skills add https://github.com/xsw632/ChipAgent --skill sync-back
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: sync-back
Source: https://github.com/xsw632/ChipAgent/tree/main/skills/sync-back
Command: npx skills add https://github.com/xsw632/ChipAgent --skill sync-back

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

When working on a local ChipAgent test project, manually tracking and copying modified skills, agents, scripts, and configuration files back to the main ChipAgent source repository is tedious, time-consuming, and prone to human error.

Core Features & Use Cases

  • Automated Change Detection: Scans all mapped directories between the local project and source repo to identify changed, new, and missing files, automatically excluding irrelevant directories like node_modules and build artifacts.
  • Clear Change Summary: Presents a structured table of all differences with change summaries so you can exactly see what has been modified before syncing.
  • Selective Sync Control: Lets you choose exactly which changes to copy back to the source repo, avoiding accidental overwrites of unrelated files.
  • Use Case: For example, if you have updated a custom skill and adjusted a test script in your local ChipAgent-Test project, this skill will show you those exact changes and let you sync only the ones you want back to the main ChipAgent repo.

Quick Start

Use the sync-back skill to review and copy your modified local ChipAgent project files back to the main ChipAgent source repository.

Frequently Asked Questions about sync-back

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

FAQPage Schema
How do I sync modified files from a local ChipAgent test project back to the source repository?

To sync modified files from a local ChipAgent test project back to the source repository, you can use an automated file synchronization tool that diffs mapped directories, summarizes changes, and selectively copies updated skills, agents, scripts, and configurations while excluding node_modules and build artifacts.

What is the best way to track local hardware development changes before merging to the main codebase?

Tracking local hardware development changes before merging to the main codebase is best handled by automated cross-directory diffing, which scans for changed, new, and missing files between your isolated local environment and the upstream source repository to generate a clear change summary.

How can I avoid accidentally overwriting unrelated files when copying hardware project configurations?

To avoid accidentally overwriting unrelated files when copying hardware project configurations, use selective sync control to review a structured table of all differences and choose exactly which modified files to copy back to the source repo.

Does automated code synchronization exclude build artifacts and node_modules directories?

Automated code synchronization does exclude irrelevant directories like node_modules and build artifacts during the scanning process, ensuring that only meaningful changes to skills, agents, scripts, and project configurations are flagged for syncing.

Can I selectively choose which updated scripts and agents to copy back to the ChipAgent repo?

Yes, you can selectively choose which updated scripts and agents to copy back to the ChipAgent repo, because the synchronization process presents a structured table of all differences with change summaries to let you decide exactly what to merge.