opsec-pr-gate

Detect anonymity and security risks in pre-merge code changes.

Updated Jun 22, 2026

Search Tags:#code analysis #security #opsec #pre-merge review #anonymity

Ready to run

npx skills add https://github.com/skylarsabo/code-ops --skill opsec-pr-gate

💬 Prompt for ChatGPT / Claude Chat▼

Please help me install this Agent Skill.
Skill: opsec-pr-gate
Source: https://github.com/skylarsabo/code-ops/tree/main/plugins/privacy-opsec-suite/skills/opsec-pr-gate
Command: npx skills add https://github.com/skylarsabo/code-ops --skill opsec-pr-gate

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes scripts (resource) components.

What problem does it solve?

This Skill provides a pre-merge gate to block any changes that would weaken anonymity or introduce security risks, ensuring that changes adhere to OpSec best practices.

Core Features & Use Cases

Pre-Merge Gate: Blocks changes adding egress, logging, identifiers, fingerprint surface, correlation, or weakened anonymity defaults.
Review and Verdict: Provides a prioritized review and verdict on the changes against OpSec standards.
Use Case: Ideal for maintaining anonymity and security in projects that require high levels of privacy protection.

Quick Start

Invoke the opsec-pr-gate skill on your PR or branch with the command: /privacy-opsec-suite:opsec-pr-gate

Frequently Asked Questions about opsec-pr-gate

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

FAQPage Schema

How do I block anonymity regressions in a pre-merge code review?▼

You can block anonymity regressions by running a pre-merge gate that analyzes code changes against predefined OpSec standards to detect and prevent merged risks like new egress points or identifiers.

What specific OpSec risks should a pre-merge security analysis detect?▼

A pre-merge security analysis should detect changes that add egress, logging, identifiers, fingerprint surface, correlation vectors, or weakened anonymity defaults to maintain strict privacy protection.

Can I use automated code analysis to enforce OpSec guidelines on a pull request?▼

Yes, you can use automated code analysis to enforce OpSec guidelines by invoking an OpSec review gate on your pull request or branch to generate a prioritized verdict on security risks.

Does pre-merge OpSec review work for software development environments requiring high privacy?▼

Pre-merge OpSec review works for software development environments requiring high privacy by comparing code changes against strict anonymity standards before allowing any merge to proceed.

What is the best way to prevent logging and fingerprint surface from entering a codebase?▼

The best way to prevent logging and fingerprint surface from entering a codebase is to implement an automated pre-merge gate that blocks changes introducing these security and anonymity risks.

Why does my code review fail to catch weakened anonymity defaults before merging?▼

Your code review may fail to catch weakened anonymity defaults because it lacks an automated OpSec gate to compare changes against predefined privacy standards and block risky merges.