gh-address-comments-extras

Harden GitHub PR review thread fetching and scanner suppression workflows against encoding and metadata errors.

1|Updated Dec 13, 2025
One-click install
npx skills add https://github.com/ZK-Theory/TDL --skill gh-address-comments-extras-zk-theory
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: gh-address-comments-extras
Source: https://github.com/ZK-Theory/TDL/tree/main/.agents/skills/gh-address-comments-extras
Command: npx skills add https://github.com/ZK-Theory/TDL --skill gh-address-comments-extras-zk-theory

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve? GitHub PR review workflows break in two subtle ways: Python thread-fetch scripts mis-decode GitHub API JSON under Windows locale encodings, and scanner findings (Codacy, Semgrep, CodeQL) get suppressed without exact rule IDs, leaving findings unresolved or incorrectly closed. This Skill adds evidence gates that catch both failure modes before they corrupt a review cycle. ## Core Features & Use Cases - Windows UTF-8 Gate: Forces UTF-8 mode (e.g., PYTHONUTF8=1) and strict decoding for Python-based thread fetchers so non-ASCII review text never silently truncates the thread inventory. - Scanner Suppression Gate: Requires mapping every check-run annotation to an exact scanner rule ID, tool, path, and line before prescribing any suppression, and demands a fresh remote analysis to prove the finding closed. - Pre-Delivery Verification: Re-checks each accepted fix against the original behavioral claim, effective tool configuration, evidence epoch, and exact reviewed head, with idempotency checks so only one review is posted. - Use Case: While addressing PR review comments on a Windows machine, a fetch script decodes GitHub JSON with the local code page and drops comments containing non-ASCII text; this Skill forces UTF-8 decoding and flags the incomplete inventory before you reply to a partial thread. ## Quick Start Ask the assistant to use gh-address-comments-extras when fetching PR review threads on Windows or before adding a suppression for a Codacy, Semgrep, or CodeQL finding.

Frequently Asked Questions about gh-address-comments-extras

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

FAQPage Schema
How do I fix GitHub API JSON decoding errors on Windows in Python?

Force UTF-8 mode for the process, for example by setting PYTHONUTF8=1, and use helpers that pass encoding=utf-8 with errors=strict to subprocess text reads. Validate the fetch path with non-ASCII review text to confirm decoding works.

How do I find the exact rule ID for a Codacy, Semgrep, or CodeQL finding?

Fetch the current check-run annotations or scanner export and record the tool, exact rule ID, message, path, and line. If the ID is absent, resolve it through the scanner API or upstream rule source using the exact message rather than inferring from a similarly named rule.

When is it safe to add a suppression for a scanner finding?

Only after mapping the finding to an exact rule ID at the current HEAD and running a fresh remote analysis that proves the suppression matched and the finding closed. If exact metadata is unavailable, use a documented line-scoped suppression only when the scanner supports it and record the uncertainty.

Why does my PR review thread fetch miss some comments?

Locale-based decoding on Windows can silently drop or corrupt non-ASCII review text, producing an incomplete thread inventory. Treat any locale-decoding failure as incomplete and never fall back to a partial flat-comment view without saying so.

How do I avoid posting duplicate PR reviews after a timeout?

Do not retry blindly after a timeout or uncertain response. Query by the exact head and review identifier, or use an equivalent idempotency mechanism, to determine whether the review already exists, then record the confirmed result and post only once.