actions-mention-to-slack: Skill for Claude Code

.claude/skills/resolve-pr-threads/SKILL.md

resolve-pr-threads is a skill for Claude Code from abeyuya/actions-mention-to-slack. It costs 92 tokens per session (2,762 once invoked), scanned A, original, MIT.

A guide for closing old GitHub pull-request review threads after checking whether the requested changes were actually made. A pull request is a proposed code change that reviewers can comment on.

In plain words
What is it for?
Use it after a new review to resolve completed threads, with options to consider all reviewers, only one bot’s threads, or none.
Why use it?
It reduces the risk of hiding unresolved problems by requiring clear evidence before a thread is closed.

Skill for Claude Code

Written for Claude Code: installed under .claude/. Also seen: mentions Claude Code; mentions Codex.

This is abeyuya/actions-mention-to-slack's own configuration. It tells Claude Code how to work on actions-mention-to-slack itself, so it is not a mod to install elsewhere. Copy it as a starting point and replace the rules that are about this project. Everything actions-mention-to-slack configures →

Reuse

Borrowing it

Nothing to install: this file belongs to abeyuya/actions-mention-to-slack. Take a copy, put it at the same path in your own repository, and replace the rules that are about this project with yours.

Copy the file
curl -O https://raw.githubusercontent.com/abeyuya/actions-mention-to-slack/master/.claude/skills/resolve-pr-threads/SKILL.md
Clone the repo
git clone --depth 1 https://github.com/abeyuya/actions-mention-to-slack

Made for: Claude Code.

Wrote this? Show the measurements

A badge with what this costs and how it scanned, read live from this page, so it follows the numbers instead of freezing them. Markdown for a README, HTML for a documentation site or a project page.

agentmods badge for resolve-pr-threads

README.md
[![agentmods](https://agentmods.dev/badge/skills/abeyuya/actions-mention-to-slack/resolve-pr-threads/github.svg)](https://agentmods.dev/skills/abeyuya/actions-mention-to-slack/resolve-pr-threads)
Your own site
<a href="https://agentmods.dev/skills/abeyuya/actions-mention-to-slack/resolve-pr-threads"><img src="https://agentmods.dev/badge/skills/abeyuya/actions-mention-to-slack/resolve-pr-threads/github.svg" alt="Measured on agentmods" height="20"></a>

Or the 80×15 button, for a site that already has a row of RSS and ATOM ones. Only the verdict fits; the numbers stay here.

agentmods 80×15 button for resolve-pr-threads

Your own site · 80×15
<a href="https://agentmods.dev/skills/abeyuya/actions-mention-to-slack/resolve-pr-threads"><img src="https://agentmods.dev/badge/skills/abeyuya/actions-mention-to-slack/resolve-pr-threads.svg" alt="Reviewed on agentmods" width="80" height="20"></a>
Per session 92 Skills are progressive disclosure: only the name and description are preloaded; the body loads when the skill is used.
When invoked 2,762 The whole file, excluding the scripts and references it only reads on demand.
Security scan A 0 findings. A grade says what 26 rules found in the file — not that it is safe. Third-party audits
  • NVIDIA SkillSpector pass 7 Sept 2026
How audits are shown
Origin original No closer match found in the catalogue.
Token cost

What it costs to keep this loaded

Counted locally with the o200k_base tokenizer, which is exact for GPT models; Claude uses its own tokenizer and its counts differ. Treat this as one consistent yardstick across the catalogue rather than a bill. Prices are per million input tokens.

ModelPer sessionOnce invoked
Fable 5.1 $0.00092 $0.02762
Opus 5 $0.00046 $0.01381
Sonnet 5 $0.00018 $0.00552
Haiku 4.5 $0.00009 $0.00276

Measured 12d ago against content hash 09c03011809e, method: parsed. Prices are Anthropic first-party input rates as of 2026-09-11, from the pricing page.

Security

Grade A, and why

resolve-pr-threads scanned grade A with 0 findings against 26 rules in 11 categories — prompt injection, anti-refusal, data exfiltration, privilege escalation, supply chain, agent snooping, system-prompt leakage, SSRF and excessive agency — measured 12d ago.

A static scan of the body, not an audit. Every finding is printed with the line that produced it so you can judge whether it matters here. A mod is markdown that instructs an agent; that is exactly why what it instructs is worth reading.

Nothing flagged

None of the 26 patterns this scan looks for appear in this file: no shell pipes, no recursive deletes, no credential paths, no hidden text, no instruction-override or anti-refusal phrasing, no agent-config snooping. That is not a guarantee, it is the absence of the things that are checkable.

.claude/skills/resolve-pr-threads/SKILL.md · 173 lines

How it starts

The opening of the file, as written. The whole thing — 173 lines — stays where its author put it; the contents beside it link to each section on GitHub.

resolve-pr-threads skill

過去のレビュースレッドのうち修正済みのものを resolve する skill。 誤判定で未対応の指摘を畳むと見落としに直結するため、判定に迷う場合は常に「resolve しない」を選ぶこと。

入力

  • OWNER / REPO / PR_NUMBER: 対象 PR
  • THREAD_RESOLVE_SCOPE: resolve 範囲
    • all (デフォルト): すべての未 resolve スレッドを対象に、author 種別 (本レビュアー Bot / 他 Bot レビュアー / 人間レビュアー) を問わず resolve 候補にする。
    • own: 本アクション自身 (claude-code-action が用いる Bot) が author のスレッドのみ resolve 候補にする。判定は自身の過去コメントの author.login と一致するか否かで行う。判定が困難な場合は resolve しない。
    • none: 過去スレッドの resolve は一切行わない。本 skill 全体を skip する。
  • SELF_LOGIN (任意): THREAD_RESOLVE_SCOPE=own 時に「自身」を判定するための author.login。caller が判明していれば渡す。未指定の場合は次の優先順で推定する:
    1. 直近の review / comment から *[bot] author で実行中アクションと一致するもの。
    2. それで決まらなければ、PR 内で *[bot] 投稿件数最多の author。複数 Bot 同居時は別 Bot (github-copilot[bot] 等) との取り違えに注意。
    3. 一意に決まらなければ scope=own をまるごと skip し、Step 5 で「SELF_LOGIN 推定不能」と報告する。

共通の resolve 判定ルール

  • 既に isResolved: true のスレッドは触らない。
  • resolve するのは 指摘内容どおりの修正が現在の差分・ファイル内容から確認できる場合のみ
  • 以下のいずれかに該当する場合は resolve しない:
    • 指摘箇所が削除されただけで、別の場所に同じ問題が残っている可能性がある。
    • isOutdated: true だが、修正されたか単に行がずれただけかが判別できない。
    • 指摘が複数論点を含み、一部しか対応されていない。
    • そもそも修正されたかどうか判断に迷う。

手順

Step 0. THREAD_RESOLVE_SCOPE のチェック

THREAD_RESOLVE_SCOPE=none の場合は何もせず終了する。

Step 1. レビュースレッド一覧を取得する

id (Step 4 の resolveReviewThread mutation で必須) / isResolved / isOutdated / 各コメントの author.login / path / line / body を GraphQL で取得し、未 resolve スレッドすべてを判定対象とする。

reviewThreads(first: 100) は GitHub GraphQL API の 1 ページあたりの上限値。100 件を超える可能性がある場合はページネーションする。

gh api graphql \
  -F owner=<OWNER> \
  -F name=<REPO> \
  -F number=<PR_NUMBER> \
  -f query='
    query($owner: String!, $name: String!, $number: Int!, $after: String) {
      repository(owner: $owner, name: $name) {
        pullRequest(number: $number) {
          reviewThreads(first: 100, after: $after) {
            pageInfo { hasNextPage endCursor }
            nodes {
              id
              isResolved
              isOutdated
              comments(first: 100) {
                nodes {
                  author { login }
                  path
                  line
                  originalLine
                  body
                }
              }
            }
          }
        }
      }
    }'

Read the full file on GitHub · 173 lines

Changes

What this file has done since we first saw it

Hashed on every crawl. A supply-chain change to an agent config is a question of when, not whether, so the history is kept rather than the latest state alone.

  1. 12d ago First seen · 173 lines · 92 tokens per session scan A 09c03011809e

Subscribe to this mod's changes

resolve-pr-threads is a skill published in the GitHub repository abeyuya/actions-mention-to-slack (58 stars, last pushed today), licensed MIT. It adds 92 tokens to every session and 2,762 once invoked, about $0.0005 per session on Opus 5. A static security scan graded it A with 0 findings. No closer match exists in the catalogue, so it is treated as the original; first seen 2026-08-30.

Related

Other skills, from other repositories

robin

Use whenever an agent creates, updates, reviews, or completes a GitHub pull request. Detect whether Robin is installed in the repository; when it is, automatically drive the PR through a bounded review, verified-fix, reply, thread-resolution, re-review, authorized-merge, and cleanup loop without requiring the user to…

antongulin/robin · 92 tokens

bellwether

Bring the current PR to a mergeable state: CI green, all review comments resolved, no merge conflicts. Self-contained — watches CI, fixes issues, watches again until merge-ready. Use when the user wants to keep a PR green, auto-fix CI, resolve review comments, or says "get this merged".

roderik/bellwether · 68 tokens

pr-review

AI-assisted review of one or more GitHub Pull Requests. Offloads deterministic checks (lint, complexity, duplication, security, perf) to repo linters via self-contained scripts, then applies LLM judgment to what linters cannot catch and posts high-signal findings after a single human approval. Pass one or many PRs…

CiscoDevNet/essentials · 121 tokens

pr-address-comments

Read a remote GitHub PR's review comments, implement fixes on the PR branch, then reply to and resolve addressed threads (REST reply + GraphQL resolveReviewThread). Use for /pr-address-comments, a single PR URL or number, when not using the parallel batch skill pr-address-comments-all. Requires gh and a git checkout…

CiscoDevNet/essentials · 74 tokens

watch-pr

Watch a GitHub pull request for CI status, reviews, comments, merge conflicts, and terminal states using the gh-watch extension. Use when the user wants to monitor a PR, wait for CI, or track PR progress.

justincampbell/gh-watch · 48 tokens

manage-merge-queue

Prepare, review, enqueue, and land GitHub pull requests through a provider-neutral agent merge queue. Use when a PR becomes ready, configured review feedback must be addressed, the user says deploy, or queued changes need safe conflict-aware ordering.

Forward-Future/DeployBot · 54 tokens