agentmods.dev

resolve-fixed

resolve-fixed is a command for coding agents from juanmhidalgo/claude-plugins. It costs 34 tokens per session (918 once invoked), scanned A, original, MIT.

A command for closing GitHub review discussions after the related issues have been verified as fixed in REVIEW_FIXES.md.

In plain words
What is it for?
Use it to read completed fixes, resolve matching GitHub threads, and record the resolution details in the fixes file.
Why use it?
It prevents review threads from being closed before the corresponding fixes are checked and documented.

Command

Installs and runs on its own, but its text points at files inside its plugin — anything it tells you to read at a ${CLAUDE_PLUGIN_ROOT} path is only there once the plugin is installed. Installing the plugin gets both.

Part of the code-review plugin — 5 skills, 14 commands, 13 agents shipped together

not rated 8 10d ago A scan 34 tokens original MIT
View the source file juanmhidalgo/claude-plugins
Install

Getting it into your agent

One page per mod, every tool's command on it. A separate URL per tool would split the same page into five that compete with each other.

agentmods
npx agentmods add commands/juanmhidalgo/claude-plugins/resolve-fixed
Clone the repo
git clone --depth 1 https://github.com/juanmhidalgo/claude-plugins

Or install code-review, the plugin that ships this one along with the rest of its 5 skills, 14 commands, 13 agents.

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-fixed

README.md
[![agentmods](https://agentmods.dev/badge/commands/juanmhidalgo/claude-plugins/resolve-fixed.svg)](https://agentmods.dev/commands/juanmhidalgo/claude-plugins/resolve-fixed)
Your own site
<a href="https://agentmods.dev/commands/juanmhidalgo/claude-plugins/resolve-fixed"><img src="https://agentmods.dev/badge/commands/juanmhidalgo/claude-plugins/resolve-fixed.svg" alt="Measured on agentmods" height="20"></a>
Per session 34 Only the description is in the session, so the agent can decide to use it. The body loads when it is invoked.
When invoked 918 The whole file, excluding the scripts and references it only reads on demand.
Security scan A 0 findings. Scan, not verified.
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 $0.00034 $0.00918
Opus 5 $0.00017 $0.00459
Sonnet 5 $0.00007 $0.00184
Haiku 4.5 $0.00003 $0.00092

Measured 4d ago against content hash 1f26fc1be969, method: parsed. Prices are Anthropic first-party input rates as of 2026-08-30, from the pricing page.

Security

Grade A, and why

resolve-fixed 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 4d 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.

code-review/commands/resolve-fixed.md · 133 lines

How it starts

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

Context

  • Repository: !git remote get-url origin
  • Branch: !git branch --show-current
  • Date: !date +%Y-%m-%d
  • PR Number: $ARGUMENTS
  • Fixes file: REVIEW_FIXES.md (or run /code-review:fixes-plan to create one)

Instructions

Step 1: Validate Inputs

  1. Check PR number - Must be provided as argument
  2. Check fixes file exists - If not found, inform user to run /code-review:fixes-plan first

Step 2: Load and Parse Fixes File

Read the REVIEW_FIXES.md file and identify:

  • Issues marked as completed (- [x] **Completed**)
  • That have a GitHub ref_id (**GitHub:** \ref_id: review_comment:123456789``)

Extract for each completed issue with ref_id:

  • Issue number/title
  • The ref_id value

Step 3: Resolve Threads on GitHub

For each completed issue with a ref_id:

  1. Parse the ref_id to get the comment type and ID
  2. Run the resolve script: 
    ${CLAUDE_PLUGIN_ROOT}/scripts/pr-resolve-comment.sh OWNER REPO PR_NUMBER REF_ID resolve
  3. Track result - success or failure

Step 4: Update REVIEW_FIXES.md

For each successfully resolved issue:

  1. Add resolution note:

    **Notes:**
- ✅ Verified fixed on YYYY-MM-DD
- 🔗 GitHub thread resolved on YYYY-MM-DD

  2. Update Implementation Log:

    | YYYY-MM-DD | 3 | Resolved | @claude | GitHub thread resolved |

Step 5: Report Results

## GitHub Resolution Results

**PR:** #[number]
**Repository:** owner/repo

### Resolved
✅ Issue #3: N+1 Query - Thread resolved
✅ Issue #5: Missing validation - Thread resolved

### Skipped (no ref_id)
⏭️ Issue #1: Code style - No GitHub thread linked

### Failed
❌ Issue #7: Race condition - Could not resolve (thread not found)

### Not Fixed Yet
⏸️ Issue #2: Data migration - Still pending

---
**Summary:** 2 resolved, 1 skipped, 1 failed, 1 pending

Important

  • Only resolves completed issues - Issues must be marked [x] first
  • Requires ref_id - Issues without **GitHub:** line are skipped
  • Safe to run multiple times - Already resolved threads are skipped by GitHub
  • Run after push - Resolve threads after your fixes are pushed to the PR

Read the full file on GitHub · 133 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. 4d ago First seen · 133 lines · 34 tokens per session scan A 1f26fc1be969

Subscribe to this mod's changes

resolve-fixed is a command published in the GitHub repository juanmhidalgo/claude-plugins (8 stars, last pushed 10d ago), licensed MIT. It adds 34 tokens to every session and 918 once invoked, about $0.0002 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-31.

Code reviewGit and workflowclose-threadsgithub-commentspr-threadsresolve-threads
Related

Other commands, from other repositories

git

Git operations with intelligent commit messages and workflow optimization.

SuperClaude-Org/SuperClaude_Framework · 11 tokens

checklist

Generate a custom checklist for the current feature based on user requirements.

github/spec-kit · 13 tokens

clarify

Identify underspecified areas in the current feature spec by asking up to 5 highly targeted clarification questions and encoding answers back into the spec.

github/spec-kit · 27 tokens

specify

Create or update the feature specification from a natural language feature description.

github/spec-kit · 13 tokens

converge

Assess the current codebase against the feature's spec, plan, and tasks, then append any remaining unbuilt work as new tasks to tasks.md so implement can complete it.

github/spec-kit · 35 tokens

implement

Execute the implementation plan by processing and executing all tasks defined in tasks.md.

github/spec-kit · 14 tokens