retrofit-from-public

Synchronize file updates from a public Git repository into a local environment with inverse transformations.

Updated Jul 13, 2026
One-click install
npx skills add https://github.com/docktermj/senzing-bootcamp-claude-plugin --skill retrofit-from-public
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: retrofit-from-public
Source: https://github.com/docktermj/senzing-bootcamp-claude-plugin/tree/main/.claude/skills/retrofit-from-public
Command: npx skills add https://github.com/docktermj/senzing-bootcamp-claude-plugin --skill retrofit-from-public

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill requires rsync, python3, and includes scripts (resource) components.

What problem does it solve?

This tool solves the synchronization gap between a public-facing repository and a private development environment, ensuring that community-driven fixes, spelling corrections, and direct edits are not lost.

Core Features & Use Cases

  • Inverse Transformation: Automatically reverses owner-specific rewrites (e.g., Senzing to docktermj) to maintain local development identity.
  • Safe Synchronization: Performs add/update operations without ever deleting local development files, providing a report of discrepancies for manual review.
  • Use Case: A maintainer receives a pull request on the public repository that fixes a typo in the documentation; this tool pulls that change into the development repo while ensuring the local environment remains correctly configured.

Quick Start

Run the retrofit script from the root of your development repository to pull and transform the latest changes from the public repository.

Frequently Asked Questions about retrofit-from-public

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

FAQPage Schema
How do I sync changes from a public Git repository to my local development environment?

To sync changes from a public Git repository, run the retrofit script from your development repository root. It selectively merges file updates using rsync while applying inverse identity transformations to maintain your local development configuration.

What is the best way to keep a dual-repo workflow updated without losing local development files?

Keeping a dual-repo workflow updated requires safe, non-destructive synchronization. This tool performs add and update operations without deleting local development files, generating a discrepancy report for manual review instead of removing untracked local content.

Do I need rsync installed to sync public repository changes back to development?

Yes, you need rsync and a local Git installation to perform safe file synchronization. These dependencies are required to execute the script that pulls public repository updates into your development environment.

How does inverse identity transformation work when merging public repository files?

Inverse identity transformation automatically reverses owner-specific rewrites, such as changing Senzing back to docktermj. This mechanism ensures that community-driven fixes and edits are pulled into the development repo while preserving local identity.

Can I use this script to automatically delete local files that are missing from the public repository?

No, the synchronization process is strictly non-destructive and will never delete local development files. It only performs add and update operations, providing a structural difference report so you can manually review discrepancies.

Why does my public repository sync not overwrite owner-specific configurations in development?

Your public repository sync preserves local configurations because the tool applies inverse identity transformations during file synchronization. It reverses public-facing owner rewrites to ensure your local development identity remains correctly configured.