FU

Automated, multi-dimensional audit suite that orchestrates agents to produce a consolidated quality report.

Install

mkdir -p .claude/skills/full-audit && curl -L -o skill.zip "https://agentskills.codes/api/skills/download/11342" && unzip -o skill.zip -d .claude/skills/full-audit && rm skill.zip

Installs to .claude/skills/full-audit

Activation

This is the description your AI agent reads to decide when to run this skill — the better it matches your request, the more reliably it fires.

Run a unified audit across all quality dimensions — architecture, code quality, testing, security, docs, and release readiness. Consolidates findings from multiple agents and scripts into a single deduplicated report.
217 charsno explicit “when” trigger
Intermediate

Key capabilities

  • Run multi-wave audits
  • Deduplicate findings
  • Generate consolidated reports
  • Track resolution status

How it works

It orchestrates parallel audit waves and uses a 3-pass deduplication engine to merge findings into a single report.

Inputs & outputs

You give it
Project root path
You get back
Consolidated audit report

When to use full-audit

  • Pre-release health check
  • Technical debt assessment
  • Security and documentation audit
  • Architectural review

About this skill

/full-audit

Unified project audit that orchestrates scripts and agents in waves, deduplicates findings, and produces a consolidated report.

Usage

/full-audit                        # standard profile (default)
/full-audit --profile quick        # fast, no Gradle
/full-audit --profile deep         # everything including beta-readiness
/full-audit --verbose              # detailed inline findings
/full-audit --output report.md     # save report to file
/full-audit --project-root PATH    # target project (default: cwd)
/full-audit --skip coverage,sbom   # skip specific checks

Profiles

ProfileWavesGradleAgentsEstimated Time
quick1-2NoNo beta-readiness~5 min
standard1-3Yes (coverage)No beta-readiness~15 min
deep1-4Yes (full)All~45 min

Procedure

Step 1: Resolve Configuration

  1. Parse arguments: --profile (default: standard), --verbose, --output, --project-root, --skip
  2. Read skills/full-audit/profiles.json for wave definitions
  3. If $PROJECT_ROOT/l0-manifest.json exists, check for full_audit overrides:
    • extra_agents: additional agents to include
    • custom_profiles: profile overrides
    • skip_checks: checks to always skip

Step 2: Execute Waves

Delegate to the full-audit-orchestrator agent, passing:

  • Profile name and wave configuration
  • Project root path
  • Skip list
  • Verbose flag

The orchestrator will:

  1. Execute each wave's checks in parallel where possible
  2. Collect findings using the <!-- FINDINGS_START --> / <!-- FINDINGS_END --> protocol from agents
  3. Run the 3-pass deduplication engine on all collected findings
  4. Track resolution against previous findings-log.jsonl entries

Step 3: Produce Report

The orchestrator produces the consolidated report in this format:

================================================================
                    FULL AUDIT REPORT
         {Project} -- {Date} -- Profile: {profile}
================================================================

HEALTH: {CRITICAL|WARNING|HEALTHY} ({N} findings: X CRIT, Y HIGH...)

 CRITICAL  [security]       OAuth tokens in SQLite plaintext
 CRITICAL  [architecture]   java.time.* in commonMain (4 files)
 HIGH      [code-quality]   CancellationException swallowed (3 repos)
 MEDIUM    [documentation]  3 pattern docs with stale versions
 ...

Checks: {N}/{M} | Duration: {T} | Deduped: {D} findings merged

ACTION ITEMS (priority order):
1. [CRITICAL] Encrypt token storage -- Art. 32 compliance
2. [CRITICAL] Replace java.time with kotlinx-datetime
3. [HIGH]     Add rethrow in catch blocks -- /auto-cover can help
================================================================

Step 4: Persist & Output

  1. Append findings to .androidcommondoc/findings-log.jsonl using the findings-append helper
  2. Append a full_audit event to .androidcommondoc/audit-log.jsonl using audit-append helper
  3. If --output specified, write report to file
  4. Display report to user

Constraints

  • NEVER re-run Gradle if --profile quick is selected
  • NEVER run beta-readiness-agent unless --profile deep
  • Respect --skip list -- silently skip named checks
  • All agents must emit findings using the structured protocol
  • The report must be <=200 lines (truncate detail section if needed, keep action items)

When not to use it

  • Single-file linting

Prerequisites

Gradle (for standard/deep profiles)

Limitations

  • Report limited to 200 lines

How it compares

It consolidates disparate quality checks into one unified report rather than running isolated tools.

Compared to similar skills

full-audit side by side with the closest alternatives in the catalog.

SkillInstallsUpdatedSafetyDifficulty
full-audit (this skill)03moNo flagsIntermediate
code-review-checklist327dNo flagsBeginner
pr-review01moNo flagsAdvanced
reviewing-code218moNo flagsIntermediate

Try saying

Example prompts that trigger this skill in your AI assistant.

Search skills

Search the agent skills registry