fixer-agent

Fix code defects and security vulnerabilities from QA audits with minimal patches.

Updated Feb 23, 2026
One-click install
npx skills add https://github.com/unnamedmistress/menuspy-marketing --skill fixer-agent
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: fixer-agent
Source: https://github.com/unnamedmistress/menuspy-marketing/tree/main/fixer-agent
Command: npx skills add https://github.com/unnamedmistress/menuspy-marketing --skill fixer-agent

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Fixes defects and security vulnerabilities discovered during QA audits by making minimal, targeted code changes that preserve existing behavior and reduce regression risk.

Core Features & Use Cases

  • Audit-driven remediation: Prioritizes P0–P3 findings and applies the smallest possible fix to resolve the issue.
  • Behavior-preserving patches: Avoids architectural rewrites and focuses on correcting incorrect or insecure implementations.
  • Regression prevention: Adds focused tests and documents before/after changes to prevent recurring issues.
  • Use Case: Receive a QA audit report showing an SQL injection and produce a minimal fix with a parameterized query, an added test, and a brief explanation.

Quick Start

Use fixer-agent to implement a minimal patch for the reported issue, add a regression test, and document what changed and why.

Frequently Asked Questions about fixer-agent

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

FAQPage Schema
How do I fix security vulnerabilities from an audit without breaking existing code behavior?

You can fix security vulnerabilities by applying minimal targeted patches that preserve behavior. This approach corrects insecure implementations with the smallest possible code edits, adds regression tests, and documents changes to reduce regression risk without requiring architectural rewrites.

How do I remediate P0 to P3 audit findings with minimal code edits?

Prioritize P0–P3 audit findings and apply the smallest possible fix to each defect. Locate affected files, make targeted edits to correct the insecure code, add focused regression tests, and document the before-and-after behavior changes.

What is the best way to patch an SQL injection finding from a code review?

The best way to patch an SQL injection finding is a minimal fix using a parameterized query. This behavior-preserving patch corrects the insecure implementation, adds a regression test to prevent recurrence, and includes a brief explanation of the change.

Can I use minimal targeted patches for repository-level bug fixes?

Yes, minimal targeted patches apply to repository-level bug fixes. The process locates affected files, makes the smallest necessary code edits to resolve the defect, adds regression tests, and documents the changes without performing architectural rewrites.

When should I avoid behavior-preserving patches for security remediation?

Avoid behavior-preserving patches when a security finding requires an architectural rewrite rather than a targeted code correction. This method is designed for minimal edits and regression prevention, so it will not resolve defects needing structural changes to the codebase.

Do I need regression tests when applying security patches to production code?

Yes, regression tests are required when applying security patches. Adding focused tests prevents recurring issues and verifies the targeted fix resolves the vulnerability without introducing new defects or altering existing application behavior.