skills.rest
shuu5
shuu5COMMUNITY
Explore all skills by this author →
GitHub

twl:workflow-pr-cycle

Coordinate multi-stage pull request workflows across verify, fix, and merge stages.

Updated Apr 5, 2026
Search Tags:#automation#git#workflow#pipeline#ci#pull-request#pr-cycle
One-click install
npx skills add https://github.com/shuu5/twill --skill twl-workflow-pr-cycle
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: twl:workflow-pr-cycle
Source: https://github.com/shuu5/twill/tree/main/plugins/twl/skills/workflow-pr-cycle
Command: npx skills add https://github.com/shuu5/twill --skill twl-workflow-pr-cycle

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This workflow orchestrates a multi-step pull request process that was split into three separate parts to improve validation, fixes, and merging.

Core Features & Use Cases

  • Modular PR verification: Split verification, fix, and merge into distinct stages to isolate concerns and speed up feedback.
  • Stage-focused automation: Orchestrates steps across verification, fixes, and merging with clear guardrails.
  • Use Case: When teams require rigorous pre-merge checks, automated fixes, and controlled merges, this workflow coordinates the three stages.

Quick Start

Run /twl:workflow-pr-verify to start the PR verification workflow

Frequently Asked Questions about twl:workflow-pr-cycle

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

FAQPage Schema
How do I automate a pull request workflow with separate verify, fix, and merge stages?▼

You can automate a multi-step pull request workflow by splitting the PR cycle into distinct verification, fix, and merge stages. This approach isolates concerns, applies pre-merge checks, automates fixes, and coordinates controlled merges across teams.

Why should I split my PR pipeline into separate verification and merge workflows?▼

Splitting your PR pipeline into separate workflows isolates validation concerns and speeds up feedback. This modular PR validation allows stage-focused automation, ensuring rigorous pre-merge checks and controlled merges before final integration.

Can I use this workflow to apply automated fixes before a controlled merge?▼

Yes, this PR workflow orchestrates automated fixes as a distinct stage. It coordinates pre-merge checks, applies necessary fixes, and manages the controlled merge process across separate workflows to maintain codebase integrity.

Do I need YAML frontmatter metadata to run these staged PR workflows?▼

Yes, the staged PR workflows require YAML frontmatter-defined metadata, including name and description fields. This metadata is necessary to properly define and orchestrate the verification, fix, and merge stages.

What is the best way to start the PR verification workflow?▼

To start the PR verification workflow, you run the dedicated PR verification command. This initiates the first stage of the multi-step pull request process, coordinating subsequent pre-merge checks and controlled merge steps.

Does this PR cycle workflow support deprecation awareness during automated merges?▼

Yes, orchestrating these three staged workflows includes deprecation awareness. This ensures controlled merges account for outdated steps or dependencies, maintaining stability throughout the verify, fix, and merge pipeline.

Related Skills

Explore More Software Engineering Skills→
HKTITANHKTITAN
5

cursor-best-practices

Generate a YAML metadata block for a Cursor Skill unit.

Community
Advanced
GTC6244GTC6244

land-and-deploy

Merge PRs, wait for CI, deploy to production, and run canary health checks.

Community
Advanced
DGouronDGouron
41

ship

Automate Git shipping with verification gates, conventional commits, and PR creation.

Community
Advanced
florianhornerflorianhorner
4

land-and-deploy

Automate GitHub PR merge, CI gating, and canary deployment workflows.

Community
Advanced