clawhip

Route Git, GitHub, tmux, and workspace events to Discord channels via a daemon gateway.

926|170|Updated Mar 8, 2026
One-click install
npx skills add https://github.com/Yeachan-Heo/clawhip --skill clawhip
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: clawhip
Source: https://github.com/Yeachan-Heo/clawhip/tree/main
Command: npx skills add https://github.com/Yeachan-Heo/clawhip --skill clawhip

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

clawhip provides a daemon-first gateway to route events to Discord channels, enabling automated notifications with operator oversight and data provenance.

Core Features & Use Cases

  • Multi-delivery routing: dispatch a single event to multiple destinations with independent formats and mentions.
  • Typed event model and modular sources: Git, GitHub, tmux, and workspace monitors feed the daemon, enabling scalable event processing.
  • Provider-native hook readiness: supports provider-native hooks for Codex/Claude, enabling seamless local and remote integrations.

Quick Start

Start clawhip by cloning the repo, building or installing the binary, scaffolding a minimal config, starting the daemon, and following the live verification runbook.

Frequently Asked Questions about clawhip

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

FAQPage Schema
How do I route GitHub and tmux events to Discord notifications?

To route GitHub and tmux events to Discord notifications, you can use a daemon-first gateway that processes typed events from modular sources and dispatches them to configurable sinks. This enables automated notifications with operator oversight.

What is multi-delivery routing for Discord channel notifications?

Multi-delivery routing for Discord notifications dispatches a single event to multiple destinations simultaneously, allowing each destination to use independent formats and mentions tailored to the specific channel's needs.

Can I send a single Git event to multiple Discord channels with different formats?

Yes, you can send a single Git event to multiple Discord channels with different formats. The daemon-first gateway supports multi-delivery routing, dispatching one event to multiple destinations with independent formats and mentions.

How do I set up a daemon to automate Discord notifications for repository events?

To set up a daemon for automating Discord notifications, clone the repository, build or install the binary, scaffold a minimal configuration file, start the daemon, and follow the live verification runbook to ensure events route correctly.

Does clawhip support provider-native hooks for Codex and Claude integrations?

Yes, clawhip supports provider-native hooks for Codex and Claude, enabling seamless local and remote integrations. This allows the daemon to receive and process events directly from these providers.

What are the limitations of using a daemon-first gateway for Discord notifications?

Using a daemon-first gateway for Discord notifications requires maintaining a continuously running daemon process and configuring typed event sources for Git, GitHub, tmux, and workspace monitors, which adds infrastructure overhead compared to simple webhook scripts.