audit-loop

Automates iterative PR audits across docs, code, and security until zero issues remain.

2|Updated Feb 13, 2026
One-click install
npx skills add https://github.com/juslee/aios --skill audit-loop
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: audit-loop
Source: https://github.com/juslee/aios/tree/main/.claude/skills/audit-loop
Command: npx skills add https://github.com/juslee/aios --skill audit-loop

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Auditing code and docs across changes can be time-consuming and error-prone. This skill automates iterative audits, running doc, code, and security checks in rounds until zero issues remain.

Core Features & Use Cases

  • Auto-detects scope from changed files (docs-only vs full audit) and applies the appropriate audits
  • Orchestrates three audit types (doc audit, code review, security/bug review) in parallel where possible
  • Enforces a two-level convergence protocol: fix issues, commit results, and re-check until a clean state

Quick Start

Run the audit-loop on your branch to start automated, convergent audits across changed files.

Frequently Asked Questions about audit-loop

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

FAQPage Schema
How do I automate pull request audits for code, docs, and security?

Automate pull request audits by running doc, code, and security reviews in iterative rounds. The process detects changed files, applies the appropriate audits in parallel, commits fixes, and re-checks until zero issues remain.

What is an iterative code review process for converging on zero issues?

An iterative code review process runs multiple audit rounds, fixing issues and committing results after each pass. It enforces a two-level convergence protocol that re-checks changed files until the repository reaches a clean state with zero remaining issues.

How do I automatically detect whether a PR needs a docs-only or full audit?

Automatically detect audit scope by analyzing changed files in the repository. If only documentation files are modified, it triggers a docs-only audit; otherwise, it initiates a full audit covering code, docs, and security reviews.

Do I need an agent framework to run automated security reviews on changed files?

Yes, you need an agent framework to spawn subagents for parallel security reviews. The automated audit process also requires a repository with changed file detection and a commit routine to record fixes after each convergence round.

What is the best way to cross-check documentation against code changes in a repository?

Cross-check documentation against code changes by running a doc audit alongside code and security reviews in parallel. This ensures all modified files are verified iteratively, with fixes committed and re-checked until all documentation matches the code.

When should I avoid running automated iterative audits on my branch?

Avoid automated iterative audits if your environment lacks an agent framework to spawn subagents or a commit routine to record fixes. The process requires changed file detection and relies on committing fixes after each round to function correctly.