propagate-to-public

Mirror shippable plugin files to a public repository with safety checks.

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

SYSTEM DOCUMENTATION & REQUIREMENTS

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

What problem does it solve?

This skill automates the complex, error-prone process of mirroring a development-grade repository to a public-facing distribution repository while ensuring sensitive development artifacts remain private.

Core Features & Use Cases

  • Scoped Mirroring: Synchronizes only the shippable plugin payload, documentation, and marketplace configuration while strictly protecting governance files like LICENSE and .github.
  • Automated Transformation: Automatically rewrites owner self-references and repository slugs from development-specific values to public Senzing-org standards.
  • Safety Guardrails: Prevents accidental data loss or repository corruption by enforcing path validation, origin verification, and excluding sensitive development-only directories.

Quick Start

Execute the propagate script to sync the current development tree to the designated public repository path.

Frequently Asked Questions about propagate-to-public

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

FAQPage Schema
How do I sync a development plugin repository to a public distribution repo safely?

Mirroring a development repository to a public repo is handled by selectively synchronizing shippable plugin payloads, documentation, and marketplace metadata while protecting governance files and excluding development-only directories.

What is the best way to automate repository ownership string replacement during deployment?

Automating repository ownership string replacement is achieved through automated transformation, which rewrites owner self-references and repository slugs from development-specific values to public standards during the synchronization process.

Does this repository sync tool require rsync and python3 to run?

Yes, rsync and python3 are required dependencies, along with bash, to execute the scripts that selectively mirror project files and perform automated string replacement.

How does the sync process protect governance files like LICENSE and .github directories?

Protecting governance files during sync is handled by strict safety guardrails that prevent the modification of protected files like LICENSE and .github while selectively mirroring only shippable plugin components to the public repository.

Can I use rsync to selectively mirror marketplace metadata without copying development-only artifacts?

Yes, you can selectively mirror marketplace metadata without copying development-only artifacts because the skill enforces scoped mirroring and origin verification to exclude sensitive directories during the rsync synchronization.