issue-fix
From the author
Fix a tracked security issue in a public `<upstream>` PR: sync the tracker, propose a plan, and on confirmation write the change, open the PR from the user's fork (on Subversion: share a private patch and commit once the team clears it), and update the tracker. Public content never reveals the CVE or the security nature of the change.
Install
npx skills add apache/magpie --skill issue-fix -a claude-code
Installs to .claude/skills/issue-fix/ · Each command fetches the skill straight from GitHub with the open skills CLI.
Byte-identical to the scanned commit, with the repository’s licence and a SOURCE.txt.
Want your agent to suggest skills while you type? See how to use skills from your IDE.
Safety checks on SKILL.md
- Contains hidden text (invisible characters, long comments or encoded blobs)Medium
- Ships scripts we have not reviewedLow
Why 73
aiqbench computes the trust score from public signals. It is not a security audit, so read a skill before you install it.
Similar skills
Closest to this one by what they do and when they are used.
- issue-import-from-prapache/magpieOpen a tracker for a security-relevant fix that already exists as a public `<upstream>` PR, with no `<security-list>` report. The tracker lands in `Assessed` with scope, PR-state and remediation fields filled from the PR; pairs with `security-cve-allocate`.Security★ 126
- issue-syncapache/magpieSynchronize a security issue in <tracker> with the state of its GitHub discussion, the <security-list> mailing thread, and any <upstream> PRs that fix it. The skill gathers all relevant signals and proposes label / milestone / assignee / field / draft-email updates — applying only what the user has explicitly confirmed. Suggests the next step in the handling process and prints the CVE allocation link when a CVE is needed.Security★ 126
- fix-workflowapache/magpieFor 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.Productivity★ 126
- issue-importapache/magpieImport new `<security-list>` reports into `<tracker>`: find threads not yet tracked, propose the imports (default: import unless rejected), create each tracker in `Needs triage`, and draft a receipt reply to the reporter. First step of the handling process.Security★ 126
- pr-review-fixTencentCloudBase/CloudBase-AI-ToolkitPeriodically analyze open pull requests for CI failures, code review feedback, and quality issues, then fix them in batch. Use this skill when the user asks to check PR status, triage CI failures, fix review comments, analyze open PRs, or run a scheduled PR health check across the repository.Engineering★ 1.1K
- newcomer-issue-explainerapache/magpieGiven an open good-first-issue on the configured `<upstream>` repo, explain it in beginner terms and sketch a concrete approach: which files to read first, what "done" looks like, and where to ask follow-up questions — without writing any code. First confirms the issue is open, non-security, and scope-clear, then drafts the explanation for maintainer review. Posts nothing without explicit maintainer confirmation.Security★ 126
Ratings & reviews
—
no reviews
Tried this skill? Rate it to help others. Sign in
Discussion
Join the discussion. Sign in