magpie-security-issue-deduplicate

To merge duplicate security issues while preserving reporter credits, run the command 'dedupe #NNN #MMM', specifying the issue to keep and the duplicate to merge. All reporter credits, mailing-list threads, and attack vector descriptions from both issues are retained.

Yes, CVE JSON attachments are regenerated automatically after merging duplicate bug tracking issues. This ensures both finders are credited in the resulting JSON file, requiring a CVE tool adapter for the regeneration process.

Yes, GitHub API access is required to merge duplicate security issues. The skill operates on bug tracking systems using issue tracking tools and needs API access to interact with the issues being merged.

The best way to detect and merge two tracking issues describing the same vulnerability is using the 'dedupe #NNN #MMM' command. This automatically merges the duplicate issue into the primary one while preserving all details and descriptions from both.

Merging duplicate security issues preserves all details and descriptions to ensure no attack vector information or mailing-list threads are lost during the deduplication process. This maintains a complete historical record of the vulnerability report across both original issues.

The skill applies to bug tracking systems using issue tracking tools and requires both a CVE tool adapter and GitHub API access. It is designed to merge issues within the same tracking environment rather than across separate platforms.