release-patterns

Automate PR creation, CI validation, and release coordination in rebase-first workflows.

395|84|Updated Oct 5, 2025
One-click install
npx skills add https://github.com/bybren-llc/wtfb-safe-agentic-workflow --skill release-patterns
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: release-patterns
Source: https://github.com/bybren-llc/wtfb-safe-agentic-workflow/tree/main/.claude/skills/release-patterns
Command: npx skills add https://github.com/bybren-llc/wtfb-safe-agentic-workflow --skill release-patterns

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

PR creation, CI/CD validation, and release coordination following rebase-first workflow.

Core Features & Use Cases

  • PR Creation: with ticket reference
  • Merge Strategy: rebase-only
  • CI Validation: run locally
  • Pre-Merge QAS gate: mandatory

Quick Start

Create a PR for {TICKET_PREFIX}-XXX with full context; run CI validation.

Frequently Asked Questions about release-patterns

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

FAQPage Schema
How do I enforce CI validation before merging pull requests?

CI validation runs locally before push and is mandatory before merge. The Skill automates CI/CD checks during PR workflows, ensuring all validation passes before code reaches the main branch in a rebase-first workflow.

What's the best way to enforce rebase merge strategy across my team?

Rebase-only merge strategy is enforced at PR creation and merge time. The Skill applies this automatically, preventing non-rebase merges and maintaining a linear commit history for clean releases.

How do I require ticket references in pull requests?

Mandatory ticket references are enforced during PR creation. The Skill validates that each PR includes the required ticket prefix, ensuring traceability between code changes and tracked work items.

Can I use standardized PR templates with automated validation?

Yes. The Skill provides standardized PR templates and applies them automatically during PR creation, ensuring consistency across your release workflow and reducing manual formatting overhead.

Do I need a QAS gate before releasing code?

A QAS gate is mandatory before merge. The Skill enforces pre-merge quality assurance review, preventing code from reaching production without explicit quality sign-off.

What happens if CI validation fails during a pull request?

Failed CI validation blocks the merge. The Skill halts the release process until all CI checks pass, ensuring only validated code proceeds through your rebase-first workflow.