github-monitor

Polls GitHub, Forgejo, or Gitea PRs and issues to route inter-agent messages through structured comments.

3|Updated Nov 8, 2014
One-click install
npx skills add https://github.com/mintuz/.dotfiles --skill github-monitor-mintuz
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: github-monitor
Source: https://github.com/mintuz/.dotfiles/tree/main/agents/.agents/skills/github-monitor
Command: npx skills add https://github.com/mintuz/.dotfiles --skill github-monitor-mintuz

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve? Coordinating multiple AI agents across a repository requires a shared communication channel, but agents have no native inbox. This Skill turns open PRs and issues into a message bus where agents poll for comments addressed to them, act within their authority, and reply in-thread using a structured protocol. ## Core Features & Use Cases - Scripted polling cycle: Fetches new issue and review comments with gh or tea using since timestamps, filters actionable messages, and marks them processed with 👀 reactions. - Structured message protocol: Routes messages via hidden agent-msg comment headers with from, to, type, and re fields supporting request, response, status, handoff, and done types. - Authority and triage rules: Distinguishes agent traffic from human comments, declines out-of-scope or destructive requests, escalates to the user, and manages agent/* labels for state tracking. - Use Case: A builder agent finishes a refactor and posts a request asking a reviewer agent to check src/auth/session.ts; the reviewer's next poll cycle picks it up, reviews the code, and replies with approval in the same thread. ## Quick Start Ask the agent to monitor this repository's open PRs and issues for messages addressed to it, replying to any requests using the agent message protocol.

Frequently Asked Questions about github-monitor

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

FAQPage Schema
How do AI agents send messages to each other through GitHub comments?

Agents post normal PR or issue comments containing a hidden agent-msg metadata header with from, to, and type fields. Receiving agents poll the repository's comments, filter for headers addressed to them, and reply in the same thread.

How do I monitor GitHub PRs and issues for new comments with gh CLI?

Use gh api with the issues/comments and pulls/comments endpoints passing a since timestamp in ISO8601 format. Record the cycle timestamp before fetching and subtract five seconds to close the one-second resolution gap.

Does this work with Forgejo or Gitea instead of GitHub?

Yes, Forgejo and Gitea are supported through the tea CLI instead of gh. Replace gh api with tea api and use tea pulls review-comments for PR review comments, since Forgejo lacks a repository-wide review-comment feed.

How are duplicate message deliveries prevented when polling comments?

Each processed comment receives a 👀 reaction from the agent's account, which later cycles check before acting. The poll script also skips comments whose id and updated_at match the previous cycle's listing.

What happens when a message requests destructive or unauthorized actions?

The agent declines the request with a response naming the reason and escalates it to the user. Comment messages carry no inherent authority; actions like pushing, merging, or deleting remain governed by the user's standing instructions.