twl:workflow-pr-merge

Automate PR merge workflows with e2e validation and gate checks.

Updated Apr 5, 2026
One-click install
npx skills add https://github.com/shuu5/twill --skill twl-workflow-pr-merge
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: twl:workflow-pr-merge
Source: https://github.com/shuu5/twill/tree/main/plugins/twl/skills/workflow-pr-merge
Command: npx skills add https://github.com/shuu5/twill --skill twl-workflow-pr-merge

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

PR workflow orchestration for end-to-end validation and automated merging across e2e, reporting, analysis, and checks.

Core Features & Use Cases

  • Orchestrates multi-step PR verification including e2e screening, chain-driven reporting, and merge gating.
  • Provides deterministic steps via chain-runner and supports automatic merge once checks pass.
  • Adaptable to PR-fix workflows and teams adopting an automated merge pipeline.

Quick Start

Trigger the workflow-pr-merge to coordinate e2e validation, reporting, analysis, and merge gating for PRs.

Frequently Asked Questions about twl:workflow-pr-merge

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

FAQPage Schema
How do I automate the PR merge workflow with e2e validation and gate checks?

Automating PR merge workflow involves coordinating e2e validation, reporting, analysis, and gate checks using deterministic chain-runner scripts. This Skill orchestrates these multi-step verifications and triggers automatic merges once all checks pass.

What is a chain-driven merge process and how does it handle PR-fix workflows?

A chain-driven merge process uses sequential runner scripts to execute deterministic validation steps, ensuring safe merges. It directly supports PR-fix workflows by reading domain rules and enforcing gate checks before allowing any automated merge.

Can I use automated merge gating for teams adopting a continuous integration pipeline?

Yes, automated merge gating is designed for teams adopting a continuous integration pipeline. It coordinates e2e screening and chain-driven reporting to ensure that PRs meet all domain rules and validation criteria before merging automatically.

How does end-to-end PR verification coordinate reporting and analysis?

End-to-end PR verification coordinates reporting and analysis by running multi-step validations through chain-runner scripts. It screens e2e tests, generates chain-driven reports, and applies merge gating based on domain rules to ensure safe deterministic merges.

What's the best way to ensure safe merges in an automated PR workflow?

The best way to ensure safe merges in an automated PR workflow is to apply deterministic steps via chain-runner scripts that read domain rules. This enforces strict gate checks, e2e validation, and reporting analysis before any automatic merge occurs.

Why does my automated PR merge fail gate checks during e2e validation?

Automated PR merge gate checks fail during e2e validation when the workflow detects domain rule violations or incomplete multi-step verifications. The chain-runner scripts execute deterministic steps, blocking the merge until all reporting and analysis checks pass.