Analyze Sigil scan findings and propose code fixes with verification steps.
npx skills add https://github.com/NOMARJ/sigil --skill fix-finding
Please help me install this Agent Skill. Skill: fix-finding Source: https://github.com/NOMARJ/sigil/tree/main/plugins/claude-code/skills/fix-finding Command: npx skills add https://github.com/NOMARJ/sigil --skill fix-finding
This Skill helps developers and security engineers turn Sigil scan findings into concrete, safe code changes by analysing the reported snippet, explaining the risk, and proposing an edit that preserves functionality while removing the security issue.
Provide a Sigil finding or file path and line number and ask for a risk explanation, a specific code edit, and verification steps.
High-intent search queries and answers about installing and using this skill.
Static analysis vulnerability remediation requires reading the reported snippet, understanding the surrounding code context, and applying a targeted edit that preserves functionality while removing the security issue. This includes explaining the attacker impact and providing steps to verify the fix.
Removing dangerous code patterns involves analyzing the specific finding, explaining the associated risk, and proposing a safer implementation that achieves the same functional intent without introducing exploitable vulnerabilities.
Remediating prompt injection and credential exposure findings requires file-level analysis of the reported code to propose explicit edit actions that secure data handling, alongside instructions to re-run security scans to confirm the vulnerability is resolved.
Context-aware code fixes for network exfiltration and obfuscation findings are generated by reading repository files to understand intent before proposing targeted edits that neutralize the exfiltration or deobfuscation risk.
Yes, verifying security code fixes requires re-running static analysis scans on the modified files to confirm the specific vulnerability, such as unsafe code patterns or inference security issues, has been fully remediated.
Fixing inference security vulnerabilities requires reading surrounding code because the remediation must preserve the original functionality while neutralizing the attack vector, which is impossible without understanding the file's broader context and intent.
jeremylongshoreScan codebases, dependencies, and configurations for security vulnerabilities and CVEs.
JeffallanIdentify security vulnerabilities in code, configuration, and infrastructure during audits.
lchenriqueIdentifies and prioritizes vulnerabilities in codebases by analyzing dependencies, secrets, code patterns, and configurations.
pycode4microReview code snippets, diffs, and pull requests for risks.
