Stats
Actions
Tags
Help us improve
Share bugs, ideas, or general feedback.
npx claudepluginhub ivintik/private-claude-marketplace --plugin plugin-opsHow this skill is triggered — by the user, by Claude, or both
Slash command
/plugin-ops:fixThe summary Claude sees in its skill listing — used to decide when to auto-load this skill
---
Fixes GitHub issues using parallel analysis, hypothesis-based root cause analysis, similar issue detection, and prevention recommendations. Use for debugging errors, regressions, bugs, or triaging.
Fixes GitHub issues by number. Fetches details via gh CLI, classifies type/severity/complexity, tracks state in SQLite DB, and implements fixes autonomously.
Creates p5.js generative art with seeded randomness, noise fields, and interactive parameter exploration. Use for algorithmic art, flow fields, or particle systems.
Share bugs, ideas, or general feedback.
Fix tracked issues from ISSUES.md with non-regression guarantees.
Parse $ARGUMENTS:
--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").
Read knowledge/lifecycle-formats.md for the full protocol.
Read the ISSUES.md entry: description, context, severity, notes.
Read relevant files, identify root cause, determine what needs to change.
For each proposed change, check against protected set:
Minimal, focused changes. Edit tool for modifications, Write only for new files.
Re-read files for all resolved issues. If regression detected: revert the change, report conflict, do NOT mark current issue resolved.
Success: status → resolved, set date, write resolution.
Blocked: add note with date explaining blocker.
Prepend fix entry to REFLECTIONS.md (format from knowledge/lifecycle-formats.md).
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.