patterns

Design event-driven GitHub agent workflows with loop prevention and orchestration patterns.

Updated Aug 27, 2026
One-click install
npx skills add https://github.com/xiaolai/awful-for-claude --skill patterns-xiaolai
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: patterns
Source: https://github.com/xiaolai/awful-for-claude/tree/main/skills/awful/patterns
Command: npx skills add https://github.com/xiaolai/awful-for-claude --skill patterns-xiaolai

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Establishes reliable, non-looping event-driven patterns to route GitHub agent actions and coordinate workflows.

Core Features & Use Cases

  • Trigger Patterns: Patterns like Labels as Routing Keys, repository_dispatch, workflow_run chaining, Comment Slash Commands, and Schedule-Based Triggers to connect events to actions.
  • Loop Prevention: Guards to prevent label ping-pong, event storms, and unbounded cascades with clear conventions and concurrency controls.
  • Orchestration Patterns: Fan-Out, Pipeline (Sequential), Gate (Human-in-the-Loop), and Periodic Sweep to compose multi-agent workflows.
  • Anti-Patterns & Safeguards: Common pitfalls and best practices to maintain safe, scalable automation.

Quick Start

Study the patterns and implement routing using labels, repository_dispatch, and scheduled triggers to avoid loops.

Frequently Asked Questions about patterns

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

FAQPage Schema
How do I prevent infinite loops in GitHub Actions workflows?

GitHub Actions workflow loops are prevented by applying loop prevention guards like clear conventions and concurrency controls. These guards stop label ping-pong, event storms, and unbounded cascades in event-driven routing.

What are the best event routing patterns for GitHub agent workflows?

The best event routing patterns for GitHub agent workflows include Labels as Routing Keys, repository_dispatch, workflow_run chaining, Comment Slash Commands, and Schedule-Based Triggers to safely connect events to actions.

How do I use labels as routing keys for GitHub Actions?

Using labels as routing keys for GitHub Actions involves defining trigger patterns that connect specific label events to agent actions. This enables reliable event-driven routing for scenarios like triage and code review workflows.

Can I chain multiple GitHub Actions workflows sequentially without causing event storms?

You can chain GitHub Actions workflows sequentially using Pipeline orchestration patterns and workflow_run chaining. Applying loop prevention strategies and concurrency controls ensures the sequential pipeline runs safely without causing event storms.

What is a human-in-the-loop gate pattern in GitHub workflows?

A human-in-the-loop gate pattern in GitHub workflows is an orchestration design that pauses automated event routing for manual approval. It establishes reliable coordination by requiring human intervention before proceeding with downstream agent actions.

Why does cross-workflow signaling cause label ping-pong and how do I stop it?

Cross-workflow signaling causes label ping-pong when workflows trigger events that re-trigger the original workflow. You stop it by implementing anti-pattern safeguards and loop prevention guards with strict concurrency controls.