security-audit

Compare two Git references to identify security regressions in code, dependencies, and CI/CD.

3|2|Updated Feb 11, 2026
One-click install
npx skills add https://github.com/Paxeer-Network/Sidiora-Perpetual-Protocol --skill security-audit-paxeer-network
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: security-audit
Source: https://github.com/Paxeer-Network/Sidiora-Perpetual-Protocol/tree/main/.windsurf/skills/security-audit
Command: npx skills add https://github.com/Paxeer-Network/Sidiora-Perpetual-Protocol --skill security-audit-paxeer-network

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes scripts (resource) and references (resource) components.

What problem does it solve?

This Skill automates the pre-release security review of code and dependency changes between any two Git references, identifying potential regressions and risks.

Core Features & Use Cases

  • Source Code Auditing: Compares code diffs for security vulnerabilities.
  • Dependency Analysis: Audits changes in direct and transitive dependencies, checking lockfile determinism.
  • CI/CD Risk Assessment: Reviews CI/CD workflows for potential security misconfigurations.
  • Use Case: Before merging a release candidate branch into main, use this skill to compare the latest tag with the release candidate branch to ensure no new security flaws were introduced.

Quick Start

Run a security audit comparing the git tag v1.0.0 to the branch main.

Frequently Asked Questions about security-audit

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

FAQPage Schema
How do I audit code and dependency changes between two Git references before a release?

To audit code and dependency changes, compare two Git references like tags or branches to identify security regressions in source code, dependency deltas, and CI/CD configurations, outputting a detailed Markdown report.

What is a pre-release security audit for Git branches and commit SHAs?

A pre-release security audit compares two Git references to identify potential security regressions and risks in source code diffs, dependency changes, and CI/CD workflows before merging a release candidate branch into main.

How do I check lockfile determinism and transitive dependency changes in a release candidate?

Checking lockfile determinism and transitive dependency changes involves analyzing dependency deltas between Git references to audit new package behaviors and identify potential security vulnerabilities introduced by updated packages.

Does this security audit tool review CI/CD workflows for misconfigurations?

Yes, the security audit reviews CI/CD workflows for potential security misconfigurations by analyzing the configuration diffs between two Git references to catch newly introduced risks in the pipeline.

Can I compare a Git tag against a branch to ensure no new security flaws were introduced?

Yes, you can compare a Git tag against a branch to ensure no new security flaws were introduced by analyzing the source code diffs, dependency changes, and CI/CD configurations between those two Git references.

What format does the pre-release security audit report output?

The pre-release security audit outputs a detailed Markdown report containing the analysis of code diffs, dependency deltas, lockfile determinism, and new package behaviors found between the compared Git references.