magpie-security-issue-import-from-pr

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.

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.

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.

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.

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.