dryrun-auditor

Derive verification checklists from source files during dry-run audits.

Updated Aug 23, 2026
One-click install
npx skills add https://github.com/gapfDev/workflow --skill dryrun-auditor
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: dryrun-auditor
Source: https://github.com/gapfDev/workflow/tree/main/.claude/skills/dryrun-auditor
Command: npx skills add https://github.com/gapfDev/workflow --skill dryrun-auditor

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Auditors often rely on static, hardcoded checks that quickly become outdated. This Skill derives verification checklists dynamically from the current source files at runtime, enabling accurate, repeatable audits without modifying artifacts.

Core Features & Use Cases

  • Derives checks from source files to validate execution blocks without manual rule maintenance.
  • Enforces read-only verification of artifacts, guaranteeing no modifications during audits.
  • Use case: perform a dry-run audit on a repository to produce an audit report in temp/dryrun that maps checks to mem_bN references.

Quick Start

Run a dry-run audit that derives its verification checklist from the current source files without modifying artifacts.

Frequently Asked Questions about dryrun-auditor

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

FAQPage Schema
What is dynamic verification checklist derivation from source files?

Dynamic checklist derivation reads source files at runtime to generate verification criteria, replacing static hardcoded rules. It ensures audits match current codebase logic by deriving checks directly from source inputs rather than relying on manual rule maintenance.

How do I audit dry-run tests without modifying artifacts?

Perform a read-only dry-run audit that derives checks from source files to validate execution blocks. This enforces read-only verification of artifacts, guaranteeing no modifications during audits while generating an audit report mapping checks to mem_bN references.

Can I use derived checklists for repository execution block validation?

Yes, you can run a dry-run audit on a repository that dynamically derives its verification checklist from current source files. This validates execution blocks by reading agent rules and contracts to generate criteria without modifying the audited artifacts.

Why do static hardcoded audit checks become outdated?

Static hardcoded checks lack synchronization with codebase changes, causing verification gaps. Deriving verification checklists dynamically from current source files at runtime ensures accurate, repeatable audits that reflect the latest agent rules and contracts without manual updates.

Where does a read-only dry-run audit write its verification report?

A read-only dry-run audit writes its generated audit report to temp/dryrun outputs. This report maps the dynamically derived verification checks to mem_bN references, ensuring the original artifacts remain unmodified throughout the validation process.