distribute

Synchronize JengaAgent scripts, hooks, and configuration files across consumer project directories.

Updated Aug 27, 2026
One-click install
npx skills add https://github.com/samwelmunga/JengaAgent --skill distribute-samwelmunga
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: distribute
Source: https://github.com/samwelmunga/JengaAgent/tree/main/.agents/skills/distribute
Command: npx skills add https://github.com/samwelmunga/JengaAgent --skill distribute-samwelmunga

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes scripts (resource) components.

What problem does it solve?

This skill eliminates the manual overhead of keeping multiple JengaAgent-powered projects synchronized, ensuring all consumer projects share the same version of agents, hooks, and scripts.

Core Features & Use Cases

  • Version-Aware Releases: Automatically manages major, minor, and patch versioning across your entire project portfolio.
  • Dry-Run Previews: Safely preview all file changes and distribution actions before applying them to your projects.
  • Use Case: When you update a core workflow script in your master repository, use this skill to instantly propagate those changes to every registered consumer project while maintaining version integrity.

Quick Start

Use the distribute skill to push the latest minor version updates to all registered consumer projects after performing a dry run.

Frequently Asked Questions about distribute

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

FAQPage Schema
How do I synchronize workflow scripts across multiple projects?

Synchronizing workflow scripts across multiple projects involves pushing updated configuration files, hooks, and scripts from a master repository to registered consumer directories while maintaining version-controlled git commits for tracking.

What is the best way to automate versioning for deployment across project directories?

Automating versioning for deployment across project directories requires a synchronization mechanism that manages major, minor, and patch version updates, ensuring all consumer projects share the same workflow version.

Can I preview file changes before synchronizing updates to consumer projects?

Yes, you can preview file changes before synchronizing updates to consumer projects by executing a dry run, which safely displays all distribution actions and file modifications before they are actually applied.

Do I need shell execution access to distribute workflow components across directories?

Yes, you need shell execution access to distribute workflow components, because the synchronization process performs file system operations and git commits to manage version-controlled releases.

How does version-controlled distribution work for DevOps automation hooks?

Version-controlled distribution for DevOps automation hooks works by propagating master repository updates to every registered consumer project directory, automatically tracking changes through git commits to maintain version integrity.