magpie-audit-finding-fix

Generate code fixes for non-security audit findings and verify them by re-running the audit tool.

79|76|Updated Apr 28, 2026

Search Tags:#code quality #code maintenance #issue triage #automated fixing #audit tool

Ready to run

npx skills add https://github.com/apache/magpie --skill magpie-audit-finding-fix

💬 Prompt for ChatGPT / Claude Chat▼

Please help me install this Agent Skill.
Skill: magpie-audit-finding-fix
Source: https://github.com/apache/magpie/tree/main/skills/audit-finding-fix
Command: npx skills add https://github.com/apache/magpie --skill magpie-audit-finding-fix

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes scripts (resource) and references (resource) components.

What problem does it solve?

This Skill automates the process of drafting fixes for non-security findings from audit tools, streamlining the review and resolution process for maintainers.

Core Features & Use Cases

Audit-Finding Drafting: Generate code fixes for batch findings reported by various audit tools.
Verification: Confirms each fix by re-running the audit tool and ensures the findings are cleared.
Committing and Handing Back: Commits fixes to a single branch and provides a hand-back artefact for review.
No Autopilot: Skill does not automatically open pull requests and requires explicit user instruction to do so.
Use Case: After an audit of a codebase identifies non-security findings, this Skill can automatically draft fixes that need to be reviewed by a human maintainer before merging.

Quick Start

Run the magpie-audit-finding-fix skill to draft fixes for audit findings in the current working tree.

Frequently Asked Questions about magpie-audit-finding-fix

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

FAQPage Schema

How do I automate fixes for code quality issues found by audit tools?▼

To automate fixes for code quality issues, use this Skill to generate draft fixes for non-security findings from audit results, then re-run the audit tool to verify the findings are cleared before human review.

What is the best way to resolve non-security audit findings in a codebase?▼

Resolving non-security audit findings is best handled by drafting fixes in a single branch, verifying them by re-running the audit tool, and providing a hand-back artefact for maintainer review before merging.

Can I automatically open pull requests for automated code maintenance fixes?▼

No, you cannot automatically open pull requests for automated code maintenance fixes. The Skill operates without autopilot, committing fixes to a branch and requiring explicit user instruction to open a pull request.

Does this automated issue triage tool handle security vulnerabilities?▼

No, this automated issue triage tool does not handle security vulnerabilities. It is specifically designed to draft fixes for non-security findings, such as unused imports and incorrect type annotations.

How do I verify that automated fixing rules actually clear audit findings?▼

To verify automated fixing rules clear audit findings, the Skill re-runs the audit tool after generating code fixes to confirm each finding is resolved before committing the changes to a single branch.

What types of routine codebase issues can be fixed using an audit tool draft workflow?▼

Routine codebase issues suitable for an audit tool draft workflow include common non-security findings like unused imports and incorrect type annotations, which are batch fixed and verified by re-running the audit.