magpie-security-issue-import-from-pr

Import security issues from public pull requests into a tracker.

79|76|Updated Apr 28, 2026

Search Tags:#security #GitHub #issue management #PR #tracker

Ready to run

npx skills add https://github.com/apache/magpie --skill magpie-security-issue-import-from-pr

💬 Prompt for ChatGPT / Claude Chat▼

Please help me install this Agent Skill.
Skill: magpie-security-issue-import-from-pr
Source: https://github.com/apache/magpie/tree/main/skills/security-issue-import-from-pr
Command: npx skills add https://github.com/apache/magpie --skill magpie-security-issue-import-from-pr

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes scripts (resource) components.

What problem does it solve?

This Skill automates the process of importing security issues from public pull requests into a tracking system, reducing manual effort and streamlining the workflow for security teams.

Core Features & Use Cases

Automated Issue Import: Import security issues directly from public pull requests, avoiding the need for manual creation of tracker issues.
Scope Detection: Automatically detect the scope of the security issue based on file changes in the PR.
Milestone Proposal: Propose an appropriate milestone for the issue based on the detected scope.
Duplicate Tracker Guard: Prevent the creation of duplicate tracker issues for the same PR.
User Confirmation: Provide a detailed proposal for the tracker issue and require user confirmation before creation.

Quick Start

Use the magpie-security-issue-import-from-pr skill to import a security issue from a PR by providing the PR number and repository, e.g., magpie-security-issue-import-from-pr 65703 [repo:owner/name].

Frequently Asked Questions about magpie-security-issue-import-from-pr

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

FAQPage Schema

How do I import security issues from public pull requests into a tracker?▼

To import security issues from public pull requests into a tracker, this Skill extracts the issue details, detects the scope from file changes, and proposes a milestone before creating the tracker issue. It requires GitHub API access to both the PR and the tracker repository.

How does duplicate issue detection work when importing from a GitHub PR?▼

Duplicate issue detection works by checking the tracker for existing issues linked to the same public pull request. This guard prevents the creation of duplicate tracker issues, ensuring each security PR is only imported once.

Do I need GitHub API access to import security issues from a PR into my tracker?▼

Yes, you need GitHub API access to both the public pull request and the tracker repository to import security issues. This access allows the Skill to read PR file changes for scope detection and create the proposed issue in the tracker.

Can I automatically detect the scope and milestone of a security issue from a PR?▼

Yes, you can automatically detect the scope of a security issue based on file changes in the public pull request. The Skill then uses this detected scope to propose an appropriate milestone for the tracker issue.

Does the tracker issue creation process require user confirmation?▼

Yes, the tracker issue creation process requires user confirmation. The Skill generates a detailed proposal including the detected scope and proposed milestone, prompting you to confirm before actually creating the issue in the tracker.