security-findings-link

Link duplicate security-review findings so consolidated reports merge them into one entry.

Updated Jul 13, 2026
One-click install
npx skills add https://github.com/torikhayes/aeai-dotnet-brownfield --skill security-findings-link-torikhayes
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: security-findings-link
Source: https://github.com/torikhayes/aeai-dotnet-brownfield/tree/main/.claude/skills/security-findings-link
Command: npx skills add https://github.com/torikhayes/aeai-dotnet-brownfield --skill security-findings-link-torikhayes

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve? During adversarial security reviews, multiple review capabilities often flag the same underlying vulnerability as separate findings, cluttering the consolidated report with duplicates. This Skill links two or more findings as the same issue so the report collapses them into a single entry. ## Core Features & Use Cases - Finding Deduplication: Link two or more finding IDs (e.g. code-0007 adv-0002) so they render as one consolidated entry with a "Detected by" line listing every contributing capability. - Human-Verified Linking: Before linking, the Skill reads each finding's description and evidence from findings.json and summarizes why they appear to be duplicates, keeping the merge decision reviewable. - Error Guidance: If an unknown finding ID is supplied, it identifies the invalid ID and suggests running /security-report to list valid IDs. - Use Case: A static-analysis pass and an adversarial review both flag the same SQL injection in a repository. Run the link command with both finding IDs so the final security report shows one issue instead of two unrelated findings. ## Quick Start Ask the assistant to link findings code-0007 and adv-0002 as the same underlying security issue.

Frequently Asked Questions about security-findings-link

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

FAQPage Schema
How do I merge duplicate security findings from different review tools?▼

Provide two or more finding IDs to the link command, for example code-0007 and adv-0002. The findings are recorded as the same underlying issue, and the next consolidated report renders them as a single entry listing every contributing capability.

How to link security findings with the security-findings-link command?▼

Pass at least two finding IDs as arguments. The Skill reads each finding's description and evidence from findings.json, summarizes why they look like duplicates for your confirmation, then runs the security-findings-store.sh script with the link action.

Can I link only one finding ID?▼

No, linking requires at least two finding IDs because linking a single finding is meaningless. If fewer than two IDs are provided, the Skill asks you to supply at least one more before proceeding.

What happens if I enter an unknown finding ID?▼

The store script returns an unknown finding id error, and the Skill tells you which ID was not found. It suggests running /security-report to see the list of valid finding IDs you can link.

Does linking findings delete the original findings?▼

No, linking preserves all original findings and their evidence. It records that they describe the same underlying issue so the consolidated report collapses them into one entry with a Detected by line listing each contributing capability.