security-permissions-review

Name: security-permissions-review
Availability: InStock
Author: FuseBase

Scan git diffs for security vulnerabilities in authentication, permissions, and secrets.

6|Updated May 29, 2026

Search Tags:#security review #code security #vulnerability detection #approval gate #secret scanning #permission check #auth validation

Ready to run

npx skills add https://github.com/fusebase-dev/fusebase-flow --skill security-permissions-review

💬 Prompt for ChatGPT / Claude Chat▼

Please help me install this Agent Skill.
Skill: security-permissions-review
Source: https://github.com/fusebase-dev/fusebase-flow/tree/main/flow-skills/security-permissions-review
Command: npx skills add https://github.com/fusebase-dev/fusebase-flow --skill security-permissions-review

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This skill addresses the high risk of undetected security vulnerabilities in code changes that touch sensitive surfaces like authentication, permissions, secrets management, and production data handling, which can lead to data breaches, unauthorized access, or compliance violations if not caught before deployment.

Core Features & Use Cases

Sensitive Surface Scanning: Automatically flags changes to auth middleware, permission checks, environment files, deploy configs, and customer-facing data flows.
Approval Gate Enforcement: Identifies operations that require formal approval per project policy and surfaces missing approval artifacts to block unauthorized deploys.
Use Case: When a developer updates a login flow or adds a new endpoint that handles customer data, this skill catches missing auth checks, potential secret leaks, and required approval steps before code is pushed to production.

Quick Start

Use the security-permissions-review skill to scan the current git diff for security risks, missing approval artifacts, and auth gaps.

Frequently Asked Questions about security-permissions-review

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

FAQPage Schema

How do I scan code changes for security vulnerabilities before deploying?▼

To scan code changes for security vulnerabilities before deploying, use a pre-deploy review process that checks git diffs modifying authentication, permissions, secrets, and production data surfaces. This prevents unauthorized access and data exposure by enforcing least-privilege checks.

How does secret redaction work in environment files and deploy configurations?▼

Secret redaction in environment files and deploy configurations works by scanning code diffs for sensitive data and automatically masking or removing exposed secrets. This prevents potential secret leaks from reaching production environments during deployment.

What is an approval gate in code security reviews?▼

An approval gate in code security reviews is an enforcement mechanism that identifies operations requiring formal authorization and surfaces missing approval artifacts. This blocks unauthorized deploys by validating that all required permissions are verified before code changes are pushed.

How do I check for missing auth validation in new endpoints?▼

To check for missing auth validation in new endpoints, scan the git diff for changes to auth middleware and database write operations. The review flags missing authentication checks and permission gaps to prevent unauthorized access to customer data flows.

Can I use a security review skill for database write operations and customer-facing data flows?▼

Yes, you can use a security review skill for database write operations and customer-facing data flows. It automatically flags changes to outbound customer-facing messages and database operations, catching missing permission checks and potential data exposure risks.

When do I need a least-privilege permission check for production data handling?▼

You need a least-privilege permission check for production data handling when code changes touch sensitive surfaces like auth middleware, environment files, and database operations. This prevents compliance violations and data breaches by ensuring access is appropriately restricted.