# Amia Github Thread Management

> Use when managing PR review threads. Reply does NOT auto-resolve threads. Trigger with /manage-threads. Loaded by ai-maestro-integrator-agent-main-agent.

- Skill: `emasoft-ai-maestro-integrator-agent/amia-github-thread-management` (Agent Skill, multi-file: 12 files)
- Install (CLI): `npx skillmds@latest add emasoft-ai-maestro-integrator-agent/amia-github-thread-management`
- Raw SKILL.md: https://api.skillmd.com/api/skills/emasoft-ai-maestro-integrator-agent/amia-github-thread-management/raw
- Safety review: pending
- Works with: Claude Code, Claude.ai, OpenAI Codex
- Category: AI & ML
- License: MIT
- Author: Emasoft (https://skillmd.com/u/emasoft-ai-maestro-integrator-agent)
- Updated: 2026-09-10
- Page: https://skillmd.com/skills/emasoft-ai-maestro-integrator-agent/amia-github-thread-management

---


# GitHub Thread Management Skill

## Overview

Manage GitHub PR review threads: list, reply, resolve, and batch-resolve. Replying to a thread does NOT auto-resolve it -- resolution requires a separate GraphQL mutation.

## Prerequisites

- GitHub CLI (`gh`) installed and authenticated
- Python 3.8+ for automation scripts
- Repository collaborator access (required for resolving)
- GraphQL API access

## Instructions

1. **List unresolved threads**: Run `amia_get_review_threads.py --unresolved-only`
2. **Decide action per thread**: Reply only (needs clarification), resolve only (code speaks for itself), or reply+resolve (explain and close)
3. **Execute**: Run the appropriate script with required parameters
4. **Verify**: Check JSON output `success` field
5. **Track**: Re-run listing to confirm all threads addressed

### Checklist

Copy this checklist and track your progress:

- [ ] List unresolved threads with `amia_get_review_threads.py --unresolved-only`
- [ ] Determine action per thread (reply / resolve / both)
- [ ] For implemented changes: resolve (optionally with reply via `--and-resolve`)
- [ ] For clarification needed: reply only (keep open)
- [ ] For batch operations: use `amia_resolve_threads_batch.py`
- [ ] Verify each operation via JSON output
- [ ] Re-run listing to confirm completion
- [ ] Check for unreplied comments with `amia_get_unaddressed_comments.py`

## Output

| Field | Type | Description |
|-------|------|-------------|
| `success` | boolean | Whether the operation completed |
| `threadId` | string | GraphQL node ID (PRRT_xxx format) |
| `isResolved` | boolean | Resolution state after operation |
| `commentId` | string | (Reply ops) Created comment node ID |
| `results` | array | (Batch ops) Per-thread results |
| `error` | string | (On failure) Error message |

> **Output discipline:** All scripts support `--output-file <path>`. With flag: JSON to file, summary to stderr. Without: JSON to stdout.

## Error Handling

Exit 1: bad params. Exit 2-4: API errors. See detailed guide in Resources.

## Resources

Full reference: [detailed-guide](references/detailed-guide.md):
  - Decision Tree for Thread Operations
  - Key Concepts
    - Thread vs Comment
    - Thread States
    - The Reply-Resolve Separation
  - Common Workflows
    - Workflow 1: Address All Unresolved Threads
    - Workflow 2: Reply and Resolve in One Command
    - Workflow 3: Batch Resolve After Large Refactor
    - Workflow 4: Find What Still Needs Attention
  - Script Usage Details
    - amia_get_review_threads.py
    - amia_resolve_thread.py
    - amia_resolve_threads_batch.py
    - amia_reply_to_thread.py
    - amia_get_unaddressed_comments.py
  - Exit Codes
  - Error Handling
    - "Thread not found" Error
    - Resolution Appears to Fail Silently
    - Cannot Resolve Thread - Permission Denied
    - Reply Added But Thread Still Unresolved
    - GraphQL Rate Limiting
  - Available Scripts (Quick Reference)

## Examples

### Example: Reply and Resolve

```bash
# List unresolved threads
python3 scripts/amia_get_review_threads.py --owner myorg --repo myrepo --pr 123 --unresolved-only

# Reply and resolve in one command
python3 scripts/amia_reply_to_thread.py \
  --thread-id PRRT_xyz \
  --body "Fixed by refactoring validation logic" \
  --and-resolve
# Output: {"success": true, "commentId": "...", "resolved": true}
```