auditing-pre-release-security

Compare two git refs to audit security and supply-chain regressions.

Updated Apr 15, 2026
One-click install
npx skills add https://github.com/wanghaisheng/web3-scaffold-app-monorepo --skill auditing-pre-release-security-wanghaisheng
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: auditing-pre-release-security
Source: https://github.com/wanghaisheng/web3-scaffold-app-monorepo/tree/main/.claude/skills/auditing-pre-release-security
Command: npx skills add https://github.com/wanghaisheng/web3-scaffold-app-monorepo --skill auditing-pre-release-security-wanghaisheng

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Audits security and supply-chain risk between two git refs (BASE_REF and TARGET_REF) with Codex MCP cross-validation, helping teams spot regressions before release.

Core Features & Use Cases

  • Compare two git refs (tag/branch/commit) for security regressions across source, dependencies, and CI/build configurations.
  • Generate a Chinese Markdown security report with traceable evidence and Codex cross-validation.
  • Use for pre-release audits, release candidate validation, or supply-chain reviews.

Quick Start

Provide BASE_REF and TARGET_REF to initiate the audit and generate a Chinese security report.

Frequently Asked Questions about auditing-pre-release-security

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

FAQPage Schema
How do I audit security regressions between two git refs before a release?

Pre-release security audits compare two git refs to detect regressions in source, dependencies, and CI configurations. By applying this to release candidates, you generate a traceable Markdown report with Codex cross-validation to ensure supply-chain integrity.

What is supply-chain integrity validation for git release candidates?

Supply-chain integrity validation for release candidates checks diffs between git branches or tags to spot regressions. It analyzes changes in source code, dependencies, and build configurations, utilizing Codex cross-validation to enforce evidence tracing and deterministic outputs.

Does pre-release security auditing work with tags, branches, and commits?

Yes, pre-release security auditing works with any two git refs, including tags, branches, and commits. You provide a BASE_REF and TARGET_REF to compare configurations and source diffs, ensuring flexible validation across different release workflows.

Can I generate a Chinese security report comparing git branches?

Yes, you can generate a Chinese Markdown security report comparing git branches. The audit redacts secrets and provides evidence tracing for the detected diffs, ensuring deterministic outputs while enforcing Codex MCP cross-validation for supply-chain reviews.

How do I cross-check dependency diffs using Codex MCP?

Cross-check dependency diffs using Codex MCP by comparing your BASE_REF and TARGET_REF. The audit mechanism enforces cross-validation against the detected changes, providing traceable evidence for supply-chain regressions found in your pre-release workflows.