s3-audit

Audit code changes against strategy and execution with tiered verdicts.

Updated Feb 4, 2026
One-click install
npx skills add https://github.com/rlaksana/.sharing --skill s3-audit
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: s3-audit
Source: https://github.com/rlaksana/.sharing/tree/main/s3-audit
Command: npx skills add https://github.com/rlaksana/.sharing --skill s3-audit

SYSTEM DOCUMENTATION & REQUIREMENTS

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

What problem does it solve?

This Skill acts as a critical quality gate, automatically verifying that code changes meet predefined standards for security, compliance, and correctness before they are archived, preventing the introduction of critical issues and technical debt.

Core Features & Use Cases

  • Automated Quality Checks: Enforces a comprehensive set of rules (R1-R10) covering everything from dependency pinning to license compliance and prompt residue.
  • Tiered Response System: Automatically BLOCKS critical failures (like missing verification evidence), ESCALATES significant scope drift, and WARNS on advisory issues.
  • Use Case: Before merging a new feature, run s3-audit on the associated DRR ID. The Skill will analyze the changes against the original strategy and execution, flagging any deviations, missing tests, or security risks, and providing a clear verdict on whether the change can proceed.

Quick Start

Run the s3-audit skill to audit the DRR with ID 'drr-12345'.

Frequently Asked Questions about s3-audit

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

FAQPage Schema
How do I automate code compliance and security audits before merging changes?

Automated code compliance audits enforce quality gates by validating pinned references, assumption ledgers, and execution integrity against a defined strategy. This prevents technical debt by generating tiered verdicts to block critical failures.

What is a quality gate for verifying scope adherence and constraint drift in CI/CD?

A quality gate for CI/CD verifies scope adherence and constraint drift by analyzing code changes against original execution strategies. It generates BLOCK, ESCALATE, or APPROVED verdicts based on predefined compliance and security rules.

How do I check for license contamination and supply chain risks in code changes?

Checking for license contamination and supply chain risks involves auditing code changes against defined rules. The audit validates dependencies and generates warnings or blocks to ensure license compliance before archiving.

Can I use an automated code audit to detect prompt residue and context boundary violations?

Yes, an automated code audit detects prompt residue and context boundary violations by validating changes against a defined strategy. It enforces correctness by flagging these issues and generating appropriate compliance warnings.

What is the best way to enforce verification evidence requirements in a software pipeline?

The best way to enforce verification evidence is using an automated audit that blocks critical failures when evidence is missing. This quality gate validates execution integrity and compliance before changes proceed.

When should an automated code audit escalate scope drift instead of blocking it?

An automated code audit escalates scope drift when the deviation is significant but not a critical failure. It generates an ESCALATE verdict to review the constraint drift, whereas missing verification evidence triggers an immediate BLOCK.