wz:self-audit

Run a worktree-isolated self-audit loop that validates, fixes, and merges on green.

3|1|Updated Mar 16, 2026
One-click install
npx skills add https://github.com/MohamedAbdallah-14/Wazir --skill wz-self-audit
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: wz:self-audit
Source: https://github.com/MohamedAbdallah-14/Wazir/tree/main/skills/self-audit
Command: npx skills add https://github.com/MohamedAbdallah-14/Wazir --skill wz-self-audit

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

The self-audit loop provides a safe, automated way to validate, audit, fix, verify, and merge changes only when all checks pass, preventing regressions in critical codebases.

Core Features & Use Cases

  • End-to-end, worktree-isolated audits that do not touch the main working tree until green.
  • Structured phase execution with safety rails to protect protected paths.
  • Generates a learnings log and audit history for ongoing improvements and compliance.

Quick Start

Invoke the self-audit to run an isolated audit cycle and merge only when all checks pass.

Frequently Asked Questions about wz:self-audit

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

FAQPage Schema
How do I automate code auditing in a Git worktree without touching my main branch?

Automated code auditing in a Git worktree isolates quality checks and fixes in a separate working tree, ensuring the main branch remains untouched until all validations pass and merge conditions are green. It enforces phased execution to prevent regressions.

What is a worktree-isolated self-audit loop for code quality?

A worktree-isolated self-audit loop is a structured process that validates, audits, fixes, verifies, and merges code changes only when all checks pass. It runs safely in an isolated Git worktree to perform end-to-end quality checks without risking the main working tree.

How does a state database track audit history and learnings for software compliance?

A state database logs audit findings and learnings during the self-audit cycle to generate an ongoing audit history. This structured logging supports continuous code quality improvements and provides compliance tracking for critical codebases.

Can I apply automated fixes to protected paths during a Git audit?

Automated fixes target general code quality issues, but safety rails explicitly protect critical paths from modification during the audit. The structured phase execution ensures protected paths remain secure while applying fixes where possible.

What's the best way to prevent regressions when merging automated code fixes?

The best way to prevent regressions is enforcing a merge-only-on-green policy within a worktree-isolated audit. This approach verifies all fixes and runs end-to-end quality checks before merging, ensuring no unvalidated changes reach the main branch.