security

Automate security analysis of code changes with Trail of Bits tools.

12|4|Updated Mar 12, 2026
One-click install
npx skills add https://github.com/FC-FUZ/claude-code-governance --skill security-fc-fuz
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: security
Source: https://github.com/FC-FUZ/claude-code-governance/tree/main/skills/security
Command: npx skills add https://github.com/FC-FUZ/claude-code-governance --skill security-fc-fuz

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Unified security analysis powered by Trail of Bits and integrated workflows. One trigger provides full coverage for code changes.

Core Features & Use Cases

  • Differential-review: Security-focused code review with risk classification (Critical/High/Medium/Low)
  • audit-context-building: Deep architectural analysis using first-principles methodology
  • static-analysis: CodeQL, Semgrep, and SARIF integration
  • supply-chain-risk-auditor: Dependency exploitation and takeover risk assessment All sub-skills live at ~/.claude/plugins/marketplaces/skills/plugins/.

How to Use

Manual invocation examples show how to trigger the workflow and run the sub-skills.

Quick Start

Run the security skill on this code change to trigger automated Trail of Bits analysis and generate a security report.

Frequently Asked Questions about security

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

FAQPage Schema
How do I automate security analysis and vulnerability detection for code changes in a pull request?

Automated security analysis for code changes uses Trail of Bits tools to perform differential code review, classify risks from Critical to Low, and generate a unified security report. It coordinates static analysis and supply-chain audits through a single workflow trigger.

What is the best way to run a dependency audit and supply-chain risk assessment on my software project?

Supply-chain risk assessment evaluates dependency exploitation and takeover risks by integrating a dedicated supply-chain-risk-auditor into the centralized security workflow. It scans updated dependencies during code changes to identify and prioritize potential vulnerabilities.

Can I use CodeQL and Semgrep together for static analysis on my codebase?

Yes, static analysis integrates CodeQL, Semgrep, and SARIF formats to scan code changes. This combination runs as part of a unified security workflow alongside architectural analysis and differential review to provide comprehensive vulnerability coverage.

How does differential code review work for classifying security vulnerabilities?

Differential review performs security-focused code analysis on changes, classifying identified risks into Critical, High, Medium, and Low categories. It operates as a coordinated sub-skill within the broader Trail of Bits security workflow to prioritize findings.

Do I need to manually trigger each static analysis tool to review code dependencies?

No, a single trigger initiates the entire unified security workflow, coordinating differential-review, audit-context-building, static-analysis, and supply-chain-risk-auditor automatically. Rule 7 automation and governance checks manage the sub-skills centrally.

When do I need deep architectural analysis versus standard static analysis for vulnerability detection?

Deep architectural analysis applies first-principles methodology for audit-context-building when evaluating complex code changes, while standard static analysis targets specific vulnerability patterns. Both run automatically through the centralized security workflow during code reviews.