gh-address-comments

Redirect PR comment workflows to gh-fix-ci for fetch, triage, and apply-fixes.

Updated Nov 30, 2025
One-click install
npx skills add https://github.com/poisontr33s/chthonic-archive --skill gh-address-comments-poisontr33s
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: gh-address-comments
Source: https://github.com/poisontr33s/chthonic-archive/tree/main/.codex/skills/gh-address-comments
Command: npx skills add https://github.com/poisontr33s/chthonic-archive --skill gh-address-comments-poisontr33s

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes scripts (resource) components.

What problem does it solve?

Historically, PR comment workflow management for gh-address-comments is now centralized in gh-fix-ci, consolidating fetch, triage, and fixes.

Core Features & Use Cases

  • Centralizes PR comment, review, and thread handling under gh-fix-ci for CI and review workflows.
  • Applies to GitHub repositories migrating PR comment workflows to gh-fix-ci, enabling consistent auth verification and PR resolution.
  • Use case: teams migrating GH PR comment automation to gh-fix-ci to streamline reviews.

Quick Start

Follow the gh-fix-ci setup to begin managing PR comments and reviews for your repositories.

Frequently Asked Questions about gh-address-comments

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

FAQPage Schema
How do I manage GitHub PR comments now that the workflow is consolidated?▼

GitHub PR comment management is now centralized in gh-fix-ci, which consolidates fetching, triaging, and applying fixes into a single workflow. You must follow the gh-fix-ci setup to manage PR comments, reviews, and threads for your repositories.

What do I need to automate pull request review workflows across repositories?▼

Automating pull request review workflows requires the GitHub CLI (gh), access to the gh-fix-ci workflow, and access to the PR's repository metadata. This setup enables consistent authentication verification and cross-repo PR resolution for fetching comments and threads.

Why has PR comment handling been redirected for CI and review automation?▼

PR comment handling has been redirected to centralize fetch, triage, and apply-fixes operations under gh-fix-ci. This migration facilitates cross-repo consistency, centralized authentication, and streamlined CI review workflows for teams managing GitHub repositories.

Does gh-address-comments work independently for fetching and triaging PR comments?▼

No, gh-address-comments does not work independently; it wraps fetch, triage, and apply-fixes operations by redirecting them to gh-fix-ci. It applies to GitHub repositories whose PR-comment tooling has been migrated to the gh-fix-ci workflow.

How to start applying fixes to GitHub pull request threads?▼

To start applying fixes to GitHub pull request threads, follow the gh-fix-ci setup to begin managing PR comments and reviews. This centralizes the handling of PR threads and enables consistent authentication verification across your repositories.

Can I use this workflow for migrating PR comment automation across multiple repositories?▼

Yes, this workflow is designed for teams migrating GitHub PR comment automation to gh-fix-ci to streamline reviews. It enables cross-repo consistency by centralizing the handling of PR comments, reviews, and threads under a single workflow.