magpie-issue-fix-workflow

Draft code fixes with automated tests for confirmed issue tracker items.

79|76|Updated Apr 28, 2026
One-click install
npx skills add https://github.com/apache/magpie --skill magpie-issue-fix-workflow
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: magpie-issue-fix-workflow
Source: https://github.com/apache/magpie/tree/main/skills/issue-fix-workflow
Command: npx skills add https://github.com/apache/magpie --skill magpie-issue-fix-workflow

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill requires git, apache-magpie, and includes scripts (resource) and references (resource) components.

What problem does it solve?

This Skill automates the drafting of code fixes for issues in issue trackers, streamlining the process from identifying an issue to drafting a fix.

Core Features & Use Cases

  • Automated Fix Drafting: Drafts code fixes for confirmed bugs or feature requests.
  • Regression Testing: Produces failing tests, production changes, and targeted test runs.
  • Human Review: Stops before opening a PR, requiring human review and decision.
  • Use Case: For a confirmed bug in a project, use this Skill to automatically draft a fix, including the failing test and necessary production change.

Quick Start

Use the fix <KEY> command to draft a fix for an issue.

Frequently Asked Questions about magpie-issue-fix-workflow

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

FAQPage Schema
How do I automate drafting code fixes for bugs in an issue tracker?

Automating code fixes for confirmed issue tracker bugs requires a Skill that drafts production changes and regression tests. This tool generates the necessary code fixes but stops before PR creation, requiring human review to proceed.

Can I generate regression tests automatically when fixing a confirmed bug?

Generating regression tests automatically for a confirmed bug is supported by drafting failing tests alongside production code changes. The workflow creates targeted test runs to validate the code fix before you manually review and approve it.

Do I need Git and Apache Magpie to automate bug fixing workflows?

Automating bug fixing workflows requires Git and the Apache Magpie framework as dependencies. You must have both tools configured in your environment to execute the automated fix drafting and regression testing processes.

What is the best way to draft failing tests and production changes for a confirmed issue?

Drafting failing tests and production changes for a confirmed issue is best handled by an automated fix workflow that generates both elements. It produces targeted test runs and code modifications, stopping for human review before opening a pull request.

Does the automated fix workflow open a pull request automatically after generating code changes?

Automated fix workflows do not open pull requests automatically after generating code changes. The process explicitly stops before PR creation, requiring human review and a manual decision to proceed with the drafted code fix.

Why does the code generation process require human review before proceeding?

Code generation requires human review to ensure the drafted production changes and regression tests are safe and accurate. The workflow intentionally stops before PR creation so developers can validate the automated bug fix before integration.