quick-fix

Apply user-suggested edits to Markdown files under .claude directory.

1|1|Updated Oct 15, 2025
One-click install
npx skills add https://github.com/MilesChou/claude-marketplace --skill quick-fix
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: quick-fix
Source: https://github.com/MilesChou/claude-marketplace/tree/main/plugins/plugin-dev/skills/quick-fix
Command: npx skills add https://github.com/MilesChou/claude-marketplace --skill quick-fix

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solves? During testing of Claude commands, skills, or agents, users often provide immediate feedback. This Skill automates the process of quickly locating, modifying, and verifying the relevant Markdown files (.md) based on that feedback, streamlining the iterative development cycle and saving you manual editing time.

Core Features & Use Cases

  • Targeted File Identification: Automatically pinpoints the correct .md file (agent, command, or skill) being tested.
  • In-Place Editing: Uses Claude's Edit tool to apply user-suggested changes directly to the file.
  • Verification & Communication: Reads the modified file to confirm changes and explains them to the user, ensuring transparency.
  • Use Case: You're testing a new agent, and Claude suggests a clearer prompt. Activate quick-fix to instantly update the agent's .md file, confirm the change, and continue testing without manual file navigation.

Quick Start

User: I'm testing my 'my-agent' agent, and I think the prompt needs to be more specific. Agent: Understood. I can use the quick-fix skill to adjust the agent's .md file. What specific changes would you like to make to the prompt?

Frequently Asked Questions about quick-fix

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

FAQPage Schema
How do I automatically apply feedback to my Claude Skills during testing?

Quick-fix automatically locates and modifies the correct Markdown file for your Skill, command, or agent being tested. When you provide feedback during testing with a 'test' command, it applies your suggested changes directly to the `.md` file, reads the result back, and confirms the modification—eliminating manual file navigation and editing.

Can I use quick-fix to edit agent, command, and skill files in my plugins?

Yes. Quick-fix identifies and edits the appropriate Markdown files across all three types: agents at `plugins/{plugin-name}/agents/{agent-name}.md`, commands at `plugins/{plugin-name}/commands/{command-name}.md`, and skills at `plugins/{plugin-name}/skills/{skill-name}/SKILL.md`. It preserves YAML Front Matter and Markdown structure in each.

What happens to the YAML Front Matter when quick-fix edits my files?

Quick-fix preserves YAML Front Matter integrity during all edits. It applies changes only to the Markdown content while keeping the metadata header untouched, ensuring your file structure and configuration remain valid after modification.

How do I trigger quick-fix to modify my plugin files?

Start a test command for your plugin, skill, or agent using a command that begins with 'test'. Provide your feedback as a suggestion, and quick-fix automatically detects the target file, applies the edits using old_string and new_string patterns, and generates before/after reports.

Can quick-fix handle multiple edits to the same file at once?

Yes. Quick-fix supports single or multiple edits in one operation by matching old_string patterns and replacing them with new_string content. It validates outcomes after all changes to confirm success and consistency.

What's the fastest way to iterate on plugin documentation during development?

Use quick-fix during testing: provide feedback suggestions, and it instantly locates your `.md` file, applies changes in place, and verifies results. This compresses the feedback-edit-verify cycle into one step, keeping your iterative development flow unbroken.