github-controller

Route GitHub events to issue-solve, pr-review, pr-fix, or no-op skills.

132|13|Updated Dec 18, 2025
One-click install
npx skills add https://github.com/holon-run/holon --skill github-controller
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: github-controller
Source: https://github.com/holon-run/holon/tree/main/skills/github-controller
Command: npx skills add https://github.com/holon-run/holon --skill github-controller

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This skill acts as the decision layer for a persistent controller session in Holon, continuously deciding whether to run issue solves, PR reviews, PR fixes, or no-ops, and dispatching to the appropriate GitHub-related skills.

Core Features & Use Cases

  • Long-running controller loop that consumes newline-delimited events from HOLON_CONTROLLER_EVENT_CHANNEL and maintains a session state.
  • Decision routing to one of: issue-solve, pr-review, pr-fix, or no-op, with exactly one executed skill per event when applicable.
  • Persistent memory and session metadata stored at the designated HOLON_CONTROLLER_SESSION_STATE_PATH and /holon/state/controller-memory.md.
  • Idempotent handling and guarded execution to prevent duplicate processing across restarts.

Quick Start

Launch Holon in proactive controller mode and feed events to HOLON_CONTROLLER_EVENT_CHANNEL.

Frequently Asked Questions about github-controller

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

FAQPage Schema
What is event-driven GitHub automation and how does a controller route events?

Event-driven GitHub automation uses a controller to process incoming events and route them to specific actions. The controller evaluates each event to decide whether to trigger an issue-solve, pr-review, pr-fix, or no-op, executing exactly one corresponding skill per event.

How do I automate PR reviews and issue fixes using a stateful GitHub controller?

To automate PR reviews and issue fixes, you run a persistent controller loop that consumes newline-delimited events from the HOLON_CONTROLLER_EVENT_CHANNEL. The controller maintains session state and dispatches each event to the appropriate pr-review, pr-fix, or issue-solve skill.

Do I need a running Holon environment to use proactive GitHub automation?

Yes, proactive GitHub automation requires a running Holon environment. You must also configure the HOLON_CONTROLLER_EVENT_CHANNEL and have durable session and memory persistence to maintain the controller loop and prevent duplicate processing.

How does a stateful controller handle idempotent execution across restarts?

A stateful controller handles idempotent execution across restarts by storing persistent metadata and session state at designated paths like HOLON_CONTROLLER_SESSION_STATE_PATH and /holon/state/controller-memory.md. This guarded execution ensures no duplicate processing occurs when the session resumes.

When should I use a persistent decision layer for GitHub event routing?

You should use a persistent decision layer for GitHub event routing when you need continuous, stateful evaluation of incoming events. It is necessary for long-running automation loops that require maintaining a cursor and dispatching to different skills like issue-solve or pr-fix without duplicates.