issue-inbox

Sync agent task progress and comments to GitHub issue threads.

3|2|Updated May 12, 2026

Search Tags:#automation #workflow #collaboration #github #agentic #issue-tracking

Ready to run

npx skills add https://github.com/kriscendobot/garden --skill issue-inbox

💬 Prompt for ChatGPT / Claude Chat▼

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

SYSTEM DOCUMENTATION & REQUIREMENTS

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

What problem does it solve?

This Skill solves the fragmentation between GitHub issue tracking and agentic task execution by ensuring that work performed by an agent remains tethered to the original issue thread.

Core Features & Use Cases

Threaded Communication: Automatically posts progress updates and completion summaries directly to the relevant GitHub issue.
Context Propagation: Ensures that issue metadata is carried through complex work chains, preventing loss of context during multi-step tasks.
Use Case: When a maintainer files a bug report, this skill allows the agent to perform the fix, verify the result, and report back on the issue thread without requiring the user to manually bridge the gap between the code and the conversation.

Quick Start

Instruct the agent to process the current job using the issue-inbox skill to ensure all work and follow-up comments are correctly synced to the originating GitHub issue.

Frequently Asked Questions about issue-inbox

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

FAQPage Schema

How do I post automated agent progress updates directly to a GitHub issue thread?▼

You can sync agentic task execution with GitHub issue threads by using this skill to automatically post progress updates and completion summaries directly to the relevant GitHub issue. It carries issue metadata through complex work chains to prevent context loss during multi-step tasks.

Can I use an automated workflow to fix a GitHub bug and report back without manually bridging the conversation?▼

Yes, when a maintainer files a bug report, this skill allows the agent to perform the fix, verify the result, and report back on the GitHub issue thread. It tethers work performed by an agent directly to the original issue tracking conversation.

Do I need the GitHub CLI to manage issue state and thread updates from agent workflows?▼

Yes, you need the GitHub CLI installed to perform authenticated thread updates and state management. This skill requires gh integration to synchronize agentic task execution with GitHub issue tracking and facilitate direct communication.

How does an agentic workflow defer GitHub issue closure to human submitters after fixing a bug?▼

This skill applies to automated maintenance workflows where agents must report progress and defer closure to human submitters. It ensures agents perform the fix and update the thread while keeping the final issue state management controlled by the human submitter.

What is the best way to maintain GitHub issue metadata across multi-step agent task chains?▼

The best way to maintain issue metadata across multi-step agent task chains is through context propagation. This skill ensures that issue metadata is carried through complex work chains, preventing the loss of context during automated maintenance workflows.