fxa-security-review

Audit code diffs against OWASP categories and leakage patterns.

683|238|Updated Jun 3, 2015
One-click install
npx skills add https://github.com/mozilla/fxa --skill fxa-security-review
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: fxa-security-review
Source: https://github.com/mozilla/fxa/tree/main/.claude/skills/fxa-security-review
Command: npx skills add https://github.com/mozilla/fxa --skill fxa-security-review

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Identify and mitigate security risks in code changes by auditing diffs for vulnerabilities before merge.

Core Features & Use Cases

  • Diff-focused security auditing: reviews the currently changed code for OWASP categories and data exposure.
  • Threat detection across authentication, authorization, and data paths, including secrets leakage, insecure crypto, and misconfigurations.
  • Actionable remediation guidance to reduce risk before deployment, suitable for security-sensitive PRs.

Quick Start

Review the current diff (git diff main...HEAD) and produce a prioritized security remediation plan.

Frequently Asked Questions about fxa-security-review

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

FAQPage Schema
How do I audit code diffs for security vulnerabilities before merging?▼

Auditing code diffs for security vulnerabilities involves reviewing changes against OWASP categories and leakage patterns to surface risks like secrets, insecure crypto, and misconfigurations, producing a prioritized remediation plan.

What is threat modeling for code changes and when do I need it?▼

Threat modeling for code changes is the process of identifying and documenting security risks in authentication, authorization, and data handling paths, needed when changes touch security-sensitive areas across web, mobile, or backend services.

Can I detect secrets leakage and insecure crypto in a git diff?▼

Yes, secrets leakage and insecure crypto can be detected in a git diff by auditing the changed code for data exposure patterns and OWASP categories, along with configuration and build artifacts.

Does diff-focused security review work for backend and mobile services?▼

Diff-focused security review works across web, mobile, and backend services by auditing changes touching authentication, authorization, data handling, and security-sensitive paths for misconfigurations and logging gaps.

What's the best way to review a pull request for OWASP risks?▼

The best way to review a pull request for OWASP risks is auditing the code diff against vulnerability categories and leakage patterns, then producing a prioritized security remediation plan before deployment.