magpie-audit-finding-fix

Solid

For a batch of findings from a non-security audit tool (`<audit-tool>` — ruff / flake8 / mypy / pylint / CodeQL / Apache Verum / Apache Caer / equivalent; full list in the body) against `<upstream>`, draft the smallest fix for each finding. Re-runs the tool after each batch to confirm the findings are cleared. Produces a commit and a hand-back artefact; never opens a PR on autopilot or merges.

AI & Automation 91 stars 89 forks Updated today Apache-2.0

Install

View on GitHub

Quality Score: 84/100

Stars 20%
65
Recency 20%
100
Frontmatter 20%
70
Documentation 15%
100
Issue Health 10%
50
License 10%
100
Description 5%
100

Skill Content

<!-- SPDX-License-Identifier: Apache-2.0 https://www.apache.org/licenses/LICENSE-2.0 --> <!-- Placeholder convention (see ../../AGENTS.md#placeholder-convention-used-in-skill-files): <project-config> → adopter's project-config directory <upstream> → adopter's public source repo <default-branch> → upstream's default branch (master vs main) <runtime> → recipe for invoking the project's runtime <audit-tool> → the audit tool producing findings (ruff, flake8, mypy, pylint, Apache Verum, Apache Caer, CodeQL, or any non-security equivalent) Substitute these with concrete values from the adopting project's <project-config>/ before running any command below. --> # audit-finding-fix This skill drafts fixes for non-security audit-tool findings in `<upstream>`. It accepts a batch of findings from `<audit-tool>` — lint violations, type errors, dead-code warnings, doc-coverage gaps — and for each finding applies the **smallest** change that makes the tool no longer report it. The skill re-runs `<audit-tool>` after each fix to confirm the finding is cleared. The entire batch is committed on a single branch and handed back for human review. The skill **stops before opening a PR**. This skill is the generic-Agentic Drafting companion to [`issue-fix-workflow`](../issue-fix-workflow/SKILL.md) (which handles issue-tracker bugs and feature requests) and [`security-issue-fix`](../se...

Details

Author
apache
Repository
apache/magpie
Created
4 months ago
Last Updated
today
Language
Python
License
Apache-2.0

Bundled in these plugins

Similar Skills

Semantically similar based on skill content — not just same category

AI & Automation Solid

magpie-issue-fix-workflow

For a single triaged `<issue-tracker>` issue confirmed as a bug or feature, draft a fix against `<upstream>` on `<default-branch>`. Produces the failing test, the smallest production change, the targeted+module test runs, and the commit. The PR is NOT opened on autopilot; the human committer reviews, signs, and pushes. Hand-back artefact summarises branch, commits, test results, and scope.

91 Updated today
apache
AI & Automation Listed

craft-fix

The Craftsman standard for driving fixes against an existing `craft-audit` workspace — "fix the findings", "fix SEC-003", "work through the audit", "start the climb". An ACTION skill, not a domain: it picks findings off the master tracker's climb sequence, re-verifies each is still real, gets the user's approval, and executes a batched fix with a regression test — it never re-audits or re-ranks. Fires with no finding ID named ("start the climb" means the top 5 open items) and on handoffs like "regression test for finding X" or "work on TEST-004". REQUIRES an existing `.craftsman/` workspace at the project root. Without one, a scoped fix request goes to the relevant domain craft skill and a whole-project assessment goes to `craft-audit` first.

1 Updated 4 days ago
atifgul99
AI & Automation Listed

craft-fix

The Craftsman standard for driving fixes against an existing `craft-audit` workspace — "fix the findings", "fix SEC-003", "work through the audit", "start the climb". An ACTION skill, not a domain: it picks findings off the master tracker's climb sequence, re-verifies each is still real, gets the user's approval, and executes a batched fix with a regression test — it never re-audits or re-ranks. Fires with no finding ID named ("start the climb" means the top 5 open items) and on handoffs like "regression test for finding X" or "work on TEST-004". REQUIRES an existing `.craftsman/` workspace at the project root. Without one, a scoped fix request goes to the relevant domain craft skill and a whole-project assessment goes to `craft-audit` first.

1 Updated 4 days ago
gul-labs