release

Create pull requests, deploy changes, update documentation, and close work items for FABER Phase 5 releases.

Updated Aug 23, 2026

Search Tags:#release #merge #pull-request

Ready to run

npx skills add https://github.com/fractary/claude-plugins --skill release-fractary

💬 Prompt for ChatGPT / Claude Chat▼

Please help me install this Agent Skill.
Skill: release
Source: https://github.com/fractary/claude-plugins/tree/main/plugins/faber/skills/release
Command: npx skills add https://github.com/fractary/claude-plugins --skill release-fractary

SYSTEM DOCUMENTATION & REQUIREMENTS

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

What problem does it solve?

Release coordinates finalization: creates PRs, links back to work items, and closes the work item upon successful deployment.

Core Features & Use Cases

Create and review PRs
Link to original work item and spec
Auto-merge checks under autonomy controls
Close work item and update session

Quick Start

Open a PR, merge if allowed, and mark the work item as closed when deployment succeeds.

Frequently Asked Questions about release

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

FAQPage Schema

How do I automate creating and merging pull requests for releases?▼

This Skill automates PR creation from feature branches, links them to work items, performs autonomy-gated auto-merge when allowed, and closes the associated work item upon successful deployment—eliminating manual coordination across PR review, merge, and work-item closure steps.

Can I link pull requests back to the original work item automatically?▼

Yes. The Skill creates PRs that reference the original work item and specification, ensuring traceability and maintaining context between deployment and tracked requirements throughout the release workflow.

How do I enforce autonomy controls on auto-merge during release?▼

Release includes autonomy gates that check permissions before auto-merging. Merge only proceeds when autonomy conditions are satisfied, preventing unauthorized deployments while automating compliant release paths.

What happens to the work item after deployment succeeds?▼

Upon successful deployment, the Skill automatically closes the work item and updates the session, completing the release cycle and signaling downstream stakeholders that the change is live.

Does this work with FABER Phase 5 workflows?▼

Yes. Release is designed for FABER Phase 5 workflows and integrates with workflow context including work_id, frame, architect, build, and evaluate components, returning standardized FABER responses.

What dependencies do I need to run release automation?▼

Release requires bash for scripting execution and jq for JSON data processing. These handle PR creation, merge validation, and work-item updates within the deployment pipeline.