Skill

Plugin Issue Fix

---

Install

Run in your terminal

npx claudepluginhub ivintik/private-claude-marketplace --plugin plugin-ops

Tool Access

This skill uses the workspace's default tool permissions.

Skill Content

Similar Skills

cache-components

Guides Next.js Cache Components and Partial Prerendering (PPR) with cacheComponents enabled. Implements 'use cache', cacheLife(), cacheTag(), revalidateTag(), static/dynamic optimization, and cache debugging.

cache-components

138.6k

claude-opus-4-5-migration

2 files

Migrates code, prompts, and API calls from Claude Sonnet 4.0/4.5 or Opus 4.1 to Opus 4.5, updating model strings on Anthropic, AWS, GCP, Azure platforms.

claude-opus-4-5-migration

83.2k

evaluation-methodology

1 file

Details PluginEval's skill quality evaluation: 3 layers (static, LLM judge), 10 dimensions, rubrics, formulas, anti-patterns, badges. Use to interpret scores, improve triggering, calibrate thresholds.

plugin-eval

32.9k

Stats

Stars0

Forks0

Last CommitMar 8, 2026

Actions

View Source View Plugin View on GitHub View README

Plugin Issue Fix

Fix tracked issues from ISSUES.md with non-regression guarantees.

Parse Arguments

Parse $ARGUMENTS:

First positional (optional): Path to plugin directory. Default: current working directory.
--issue ISSUE-NNN: Fix a specific issue.
--all-open: Fix all open issues (severity order: critical → major → minor → enhancement).
--dry-run: Analyze and propose fixes without applying.

If neither --issue nor --all-open, list open issues and ask which to fix.

Cache guard: ~/.claude/plugins/cache/ is READ-ONLY. Resolve to the real git repo via atlas: atlas_search_projects(query="plugin-name").

Non-Regression Protocol (mandatory)

Read knowledge/lifecycle-formats.md for the full protocol.

Read ISSUES.md — collect all resolved issues with ID, title, resolution, files
This "protected set" must remain intact after fixes

For Each Issue

1. Understand

Read the ISSUES.md entry: description, context, severity, notes.

2. Investigate

Read relevant files, identify root cause, determine what needs to change.

3. Plan

For each proposed change, check against protected set:

Touches resolved fix → SKIP, explain conflict
Same file but different section → proceed with caution
No overlap → proceed

4. Apply (unless --dry-run)

Minimal, focused changes. Edit tool for modifications, Write only for new files.

5. Verify

Re-read files for all resolved issues. If regression detected: revert the change, report conflict, do NOT mark current issue resolved.

6. Update ISSUES.md

Success: status → resolved, set date, write resolution. Blocked: add note with date explaining blocker.

Post-Fix

Prepend fix entry to REFLECTIONS.md (format from knowledge/lifecycle-formats.md).

Output

Fix results for {plugin-name} v{version}

ISSUE-{NNN} ({severity}): {title}
  Status: resolved | blocked | skipped
  {resolution or reason}

Non-regression: {N} resolved issues verified — {all intact | M regressions}

For multi-file fixes: break into steps, verify non-regression after each step, revert on regression, update status to in-progress with partial progress notes.