push-update

Promote generic improvements from an instance to a template with versioning.

Updated Aug 23, 2026
One-click install
npx skills add https://github.com/Jennyfirrr/workspace-template --skill push-update-jennyfirrr
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: push-update
Source: https://github.com/Jennyfirrr/workspace-template/tree/main/claude-skills/push-update
Command: npx skills add https://github.com/Jennyfirrr/workspace-template --skill push-update-jennyfirrr

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Promote a generic improvement discovered in this workspace up to the template and version it so every project can pull it. The UP flow ensures the change is carried into the template only when it provides a reusable core, leaving project-specific content local. It coordinates spotting reusable patterns, canonicalizing artifacts, and wiring changes to the template's structure.

Core Features & Use Cases

  • Genericize an improvement: strip project specifics and prepare a template-ready artifact.
  • Version and promote: append a changelog entry and bump the template VERSION so updates are pullable by downstream instances.
  • Safe, reusable deployment: enforce the boundary between generic core and local project content to maintain template integrity.

Quick Start

Identify a reusable improvement and run the /push-update sequence to publish it to the template and advance its version.

Frequently Asked Questions about push-update

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

FAQPage Schema
How do I promote a workflow improvement from a project instance back to a template?▼

To promote an instance improvement, the push-update process strips project-specific content, genericizes the artifact, and updates the template version log so all downstream instances can pull the reusable core.

What is template versioning for standardized processes and when do I need it?▼

Template versioning is the mechanism of bumping a VERSION and appending a changelog entry when a reusable core improvement is promoted upstream. You need it when a generic artifact benefits all downstream project instances.

How do I genericize project-specific artifacts before pushing an upstream update?▼

You genericize project-specific artifacts by enforcing the boundary between local content and the generic core, stripping project specifics, and wiring changes to the template's structure before promoting the upstream update.

How do I ensure local project content remains separate during template versioning?▼

Template versioning ensures project-specific content remains local by enforcing a strict boundary, promoting only true generic artifacts upstream while leaving local project configurations untouched in the instance.

What is the best way to standardize workflow automation changes across multiple projects?▼

The best way to standardize workflow automation changes is to identify a reusable improvement, canonicalize it, and promote it to the template so all instances can pull updates while maintaining local project boundaries.

What happens if I promote project-specific content instead of a generic artifact to the template?▼

Promoting project-specific content instead of a generic artifact breaks template integrity. The process enforces a boundary to ensure only true generic artifacts are versioned and promoted upstream, leaving local content untouched.