framework-patch

Coordinate framework releases across downstream repos and CI workflows.

Updated Aug 27, 2026

Search Tags:#changelog #release #notifications #governance #framework #tagging #downstream

Ready to run

npx skills add https://github.com/mattfuster/aisef-setup --skill framework-patch

💬 Prompt for ChatGPT / Claude Chat▼

Please help me install this Agent Skill.
Skill: framework-patch
Source: https://github.com/mattfuster/aisef-setup/tree/main/.claude/skills/framework-patch
Command: npx skills add https://github.com/mattfuster/aisef-setup --skill framework-patch

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

The Framework Patch agent manages outbound distribution of framework changes from the AISEF hub to downstream product repositories. It coordinates release tagging, changelog propagation, and dispatch notifications to ensure consistency and governance across all dependent repos.

Core Features & Use Cases

Release tagging governance with explicit changelog validation
Notifies downstream repos and triggers downstream sync workflows
Supports multi-repo coordination for major, minor, and patch updates

Quick Start

Initiate a framework release by saying 'Release framework v1.2.0'.

Frequently Asked Questions about framework-patch

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

FAQPage Schema

How do I coordinate framework releases across multiple downstream repositories?▼

Coordinating framework releases across downstream repositories requires synchronizing tag creation, changelog generation, and dispatch notifications. This skill manages that outbound distribution by enforcing semantic versioning and notifying dependent repos to trigger sync workflows.

Do I need an updated changelog before tagging a framework release?▼

Yes, an updated changelog is required before tagging a framework release. The process enforces changelog validation to ensure governance and consistency across all dependent downstream repositories during distribution.

How do framework release notifications trigger downstream CI workflows?▼

Framework release notifications trigger downstream CI workflows by reading the current framework state and downstream registry, then dispatching explicit notifications across multiple repos to initiate their sync processes.

Can I use semantic versioning for major, minor, and patch updates across downstream repos?▼

Yes, semantic versioning is supported for major, minor, and patch updates across downstream repos. The coordination process enforces these versioning standards during tag creation and downstream registry updates.

What is the best way to propagate changelog updates to downstream product repositories?▼

Propagating changelog updates to downstream product repositories is best handled by a coordination agent that validates the CHANGELOG, creates release tags, and dispatches notifications to ensure consistency across all dependent repos.