Sponsor Suno AI Music arrow_forward
Slash Command

Resolve Threads

Batch-resolve unresolved PR/MR review threads via GraphQL API (GitHub/GitLab)

Type
Slash Command
GitHub stars
339
License
MIT
Repo last updated
Sep 24, 2026

What Resolve Threads is

Resolve Threads is a slash command published in the athola/claude-night-market repository on GitHub, which has about 339 stars. The repository describes itself as: “23 Claude Code plugins: TDD enforcement hooks, git/PR workflows, spec-driven development, code review, project lifecycle, fix-from-error, maintenance automation, context optimization, research, and multi-LLM delegation. 186 skills, 128 commands, 54 agents.”

A slash command is a reusable prompt saved as a markdown file and run by typing its name after a slash. In Claude Code, custom commands have been merged into skills: a file in .claude/commands/ and a skill folder in .claude/skills/ both create the same kind of command, and existing command files keep working.

Resolve Threads gives you a repeatable way to run the same instructions without retyping them, optionally with arguments.

How to install Resolve Threads

Claude Code

  1. Download resolve-threads.md from the repository.
  2. Save it to ~/.claude/commands/ (all projects) or .claude/commands/ (one project). As a skill, you can instead save it as ~/.claude/skills/<name>/SKILL.md.
  3. Run it by typing / followed by its name.

Claude Cowork

  1. Turn the command into a skill: create a folder with the file saved as SKILL.md and zip it.
  2. In Customize → Skills, click +, then upload the ZIP.
  3. Run it from any task with / and the skill name.

New to extending Cowork? Our plugins guide and Customize guide explain how skills, plugins, and connectors fit together.

Inside the source file

An excerpt from plugins/sanctum/commands/resolve-threads.md, shared under the repository's MIT license. Read the full file on GitHub.

Quickly resolve all unresolved review threads on a PR after fixes have been addressed.

When To Use

  • Runs automatically at the end of /fix-pr (Phase 7)
  • After manually addressing PR review comments outside /fix-pr
  • To clean up resolved conversations before merge
  • As a standalone verification command

When NOT To Use

  • Simple changes that don't need the full workflow
  • Work already completed through another sanctum command

Workflow

Step 1: Identify Target PR

# GitHub - if no PR specified, use current branch
gh pr view --json number,url -q '.number'

# GitLab
glab mr view --json iid -q '.iid'

Step 2: Fetch Unresolved Threads

# Replace OWNER, REPO, PR_NUMBER with actual values
gh api graphql -f query='
query {
  repository(owner: "OWNER", name: "REPO") {
    pullRequest(number: PR_NUMBER) {
      reviewThreads(first: 100) {
        nodes {
          id
          isResolved
          path
          line
          comments(first: 1) {
            nodes { body }
          }
        }
      }
    }
  }
…

Step 3: Resolve Each Thread

For each unresolved thread:

gh api graphql -f query='
mutation {
  resolveReviewThread(input: {threadId: "PRRT_xxx"}) {
    thread { isResolved }
  }
}'

Step 4: Verify Resolution

# Should return 0
gh api graphql -f query='...' \
  --jq '[.data.repository.pullRequest.reviewThreads.nodes[] | select(.isResolved == false)] | length'

Output

### Thread Resolution Summary

| Status | Count |
|--------|-------|
| Resolved | 15 |
| Already resolved | 3 |
| Failed | 0 |

All 18 review threads are now resolved.

Notes

  • Requires GitHub CLI with GraphQL access
  • Does NOT reply to threads - use /fix-pr for reply + resolve
  • Safe to run multiple times (idempotent)

See Also

  • /fix-pr - Full workflow for addressing PR comments (reply + resolve)
  • /pr-review - Review a PR and post findings as GitHub comments

Before you install

  • Read the whole file first. Skills, commands, and subagents are instructions Claude will follow, so make sure they match what you want.
  • Check which tools, scripts, or MCP servers it uses. Local servers and scripts run with your permissions.
  • Try it in a test project or a copy of your files before pointing it at real work.
  • Pin the version you tested, and review changes before updating.
  • Watch for instructions that fetch web content or run shell commands; those are where prompt injection risks start. See our prompt injection guide.

FAQ

What is Resolve Threads?

Resolve Threads is a slash command for Claude Code and Claude Cowork from the athola/claude-night-market repository on GitHub. Batch-resolve unresolved PR/MR review threads via GraphQL API (GitHub/GitLab)

How do I install Resolve Threads in Claude Code?

Download resolve-threads.md from the repository. Save it to ~/.claude/commands/ (all projects) or .claude/commands/ (one project). As a skill, you can instead save it as ~/.claude/skills/<name>/SKILL.md. Run it by typing / followed by its name.

Can I use Resolve Threads in Claude Cowork?

Turn the command into a skill: create a folder with the file saved as SKILL.md and zip it. In Customize → Skills, click +, then upload the ZIP. Run it from any task with / and the skill name.

Is Resolve Threads safe to install?

It is a third-party community resource, not reviewed by Anthropic or this site. Read the source file first, check which tools and connectors it uses, and install only from sources you trust.

Similar resources

Browse all skills, subagents, and plugins →

Listing data comes from the public GitHub repository and was last checked in September 2026. Excerpts are © their authors and shared under MIT. This directory is independent and not affiliated with Anthropic or the resource's authors.