at-mention-surveillance

Monitor GitHub comment bodies for @-mentions and create jobs.

3|2|Updated May 12, 2026

Search Tags:#automation #workflow #collaboration #monitoring #github #surveillance

Ready to run

npx skills add https://github.com/kriscendobot/garden --skill at-mention-surveillance

💬 Prompt for ChatGPT / Claude Chat▼

Please help me install this Agent Skill.
Skill: at-mention-surveillance
Source: https://github.com/kriscendobot/garden/tree/main/skills/at-mention-surveillance
Command: npx skills add https://github.com/kriscendobot/garden --skill at-mention-surveillance

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill requires gh, jq, and includes scripts (resource) components.

What problem does it solve?

This skill solves the problem of missed routing signals in GitHub comments, ensuring that critical requests directed at the bot or maintainer are never overlooked due to being buried in comment bodies.

Core Features & Use Cases

Content-Level Monitoring: Scans comment bodies for specific @-mentions, capturing intent that event-level triggers miss.
Automated Job Dispatch: Automatically converts identified mentions into actionable fix or design jobs for the gardener pool.
Safety-First Acknowledgement: Uses reactji-acknowledgment to signal receipt of requests before processing, preventing silent failure modes.

Quick Start

Enable the at-mention-surveillance skill to monitor the repository for routing signals and automatically post jobs for the gardener pool.

Frequently Asked Questions about at-mention-surveillance

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

FAQPage Schema

How do I monitor GitHub comments for @-mentions to trigger automated tasks?▼

Monitoring GitHub comments for @-mentions involves polling GitHub API endpoints for new issue and pull request bodies to identify routing intent. This skill scans comment bodies, captures specific mentions, and automatically dispatches actionable maintenance or design jobs.

What's the best way to automate job dispatch from GitHub issue comment bodies?▼

Automating job dispatch from GitHub issue comments requires scanning comment bodies for specific @-mention patterns. Once identified, these mentions are automatically converted into actionable fix or design jobs for the gardener pool to process.

Do I need GitHub CLI and jq to scan pull request comments for maintainer mentions?▼

You need the GitHub CLI and jq to process comment data and maintain state for idempotent job creation. These dependencies are required to poll API endpoints and parse the comment bodies for specific @-mention patterns.

Why use content-level monitoring instead of event-level triggers for GitHub @-mentions?▼

Content-level monitoring captures routing intent from contributors that event-level triggers miss. By scanning comment bodies directly for specific @-mentions, it ensures critical requests buried in comments are never overlooked.

How does this skill prevent silent failure modes when processing GitHub mentions?▼

To prevent silent failure modes, this skill uses reactji-acknowledgment to signal receipt of requests before processing. This safety-first approach ensures contributors know their @-mentions have been received and queued for automated job dispatch.

Can I use this approach to track routing signals across multiple GitHub repositories?▼

Tracking routing signals across repositories requires polling GitHub API endpoints for new comments and review bodies. This skill operates by maintaining state for idempotent job creation, ensuring duplicated mentions do not trigger redundant maintenance tasks.