fix

Name: fix
Availability: InStock
Author: ivintik

Parse ISSUES.md and apply minimal fixes with non-regression guarantees.

Updated Feb 22, 2026

Search Tags:#fix #plugin #issues #ISSUES.md #code-review #dry-run #non-regression

Ready to run

npx skills add https://github.com/iVintik/claude-plugin-ops --skill fix-ivintik

💬 Prompt for ChatGPT / Claude Chat▼

Please help me install this Agent Skill.
Skill: fix
Source: https://github.com/iVintik/claude-plugin-ops/tree/main/skills/fix
Command: npx skills add https://github.com/iVintik/claude-plugin-ops --skill fix-ivintik

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

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

Core Features & Use Cases

Parse ISSUES.md to collect issues with IDs, titles, statuses, and resolutions.
Validate changes against a protected fix set, ensure non-regressions, and apply minimal patches.
Support selective fixing via --issue or fix-all-open, with a safe dry-run mode.

Quick Start

Run the fix skill on a plugin repository to fix open ISSUES.md entries with non-regression safety.

Frequently Asked Questions about fix

High-intent search queries and answers about installing and using this skill.

FAQPage Schema

How do I safely fix tracked issues in an ISSUES.md file without causing regressions?▼

Fixing tracked issues in an ISSUES.md file requires parsing entries, proposing minimal patches, and validating changes against a protected fix set to guarantee non-regression. This structured workflow ensures plugin issues are resolved safely without breaking existing functionality.

Can I run a dry-run to simulate ISSUES.md fixes before applying them?▼

Yes, you can simulate ISSUES.md fixes using a safe dry-run mode. This allows you to propose and verify changes for plugin issues before actually applying them, ensuring non-regression safety and minimal patch impact.

What is the best way to selectively fix open issues tracked in a plugin repository?▼

The best way to selectively fix open issues is by targeting specific entries with an issue flag or applying fixes to all open items. This approach parses ISSUES.md IDs and statuses to apply minimal, validated patches safely.

How does parsing an ISSUES.md file work for automated code review and issue resolution?▼

Parsing an ISSUES.md file works by collecting issues with IDs, titles, statuses, and resolutions. This structured data is then used to propose changes, verify non-regressions, and update the file as issues are safely fixed.

Does this issue fixing workflow require any specific dependencies or plugin components?▼

No specific dependencies or components are required to run this issue fixing workflow. It operates directly on plugin repositories to parse ISSUES.md entries, apply minimal patches, and verify non-regression safety.

When should I avoid using an automated tool to fix plugin issues?▼

You should avoid automated plugin issue fixing when changes cannot be validated against a protected fix set or when minimal patches are insufficient. Complex issues requiring broad refactoring fall outside this non-regression safety workflow.