htlin222

Claude With Webhook — Git skill for Claude Code

Git community

Self-hosted GitHub webhook server that automates Claude Code planning & implementation from issues, integrating your local claude CLI subscription with GitHub workflows for zero-API-cost automation.

How to install Claude With Webhook

This entry records only its repository, not the path inside it, so there is no exact command to give. Open htlin222/claude-with-webhook and copy the folder into ~/.claude/skills/, or the file into ~/.claude/agents/.

What Claude With Webhook does

Self-hosted GitHub webhook server that automates Claude Code planning & implementation from issues, integrating your local claude CLI subscription with GitHub workflows for zero-API-cost automation.

Alternatives in Git

Cc Usage — by ryoppippi - Handy CLI tool for managing and analyzing Claude Code usage, based on analyzing local Claude Co 11.7k ★
Git MCP — GitHub Repo stars Free open-source remote MCP server for any GitHub project Git integration MCP 7.8k ★
Zcf — GitHub Repo stars Zero-Config Code Flow for Claude code & Codex Zero-config workflow 5.8k ★

README

Claude Code Webhook Server

[![Stars](https://img.shields.io/github/stars/htlin222/claude-with-webhook?style=flat)](https://github.com/htlin222/claude-with-webhook/stargazers) [![Last Commit](https://img.shields.io/github/last-commit/htlin222/claude-with-webhook)](https://github.com/htlin222/claude-with-webhook/commits/main) [![Go](https://img.shields.io/badge/Go-1.23+-00ADD8?logo=go&logoColor=white)](https://go.dev/) [![License: MIT](https://img.shields.io/badge/License-MIT-yellow.svg)](LICENSE) [![GitHub issues](https://img.shields.io/github/issues/htlin222/claude-with-webhook)](https://github.com/htlin222/claude-with-webhook/issues) [繁體中文](README.zhtw.md)

A Go server that automates Claude Code planning and implementation via GitHub issues. One server handles multiple repos, routed by URL path. When an allowed user opens an issue, Claude generates a plan. On approval, Claude implements the changes in a git worktree and opens a PR.

Scenario

A team is debating how to refactor the authentication module. Five people leave comments on the issue — one wants OAuth, another prefers JWT, someone raises concerns about backward compatibility, the PM clarifies the deadline, and a junior dev asks what "middleware" means.

Normally, the tech lead reads all of this, writes a summary, drafts a plan, codes the solution, writes tests, opens a PR, and asks for review. That's half a day gone.

With this project, the tech lead types one comment:

`@claude approve please gather everyone's opinions from this discussion, find the approach that satisfies the security concerns and the deadline, and implement it with tests`

Then goes to lunch.

By the time they're back, there's a PR waiting — code written, tests passing, every team member's concern addressed in the implementation. The tech lead reviews the diff, clicks merge, and moves on.

**The new workflow:** Humans discuss. Humans decide. The agent does the rest.

The only irreplaceable part is the conversation — the ideas, t