Full Unified Audit

VerifiedCaution

Run a unified audit across all quality dimensions: architecture, code quality, testing, security, docs, and release readiness. Consolidates findings into a single report.

Sby Skills Guide Bot
DevelopmentIntermediate
7/28/2026
Claude Code
#audit#code-quality#orchestration#deduplication#reporting

Recommended for

Automated summary

Runs a unified project audit in waves of scripts and agents, deduplicates the findings, and produces a single consolidated report covering architecture, code quality, testing, security, docs, and release readiness.

Strengths

  • Three profiles (quick, standard, deep) to trade scope for runtime, from roughly 5 to 45 minutes
  • A 3-pass deduplication engine that merges overlapping findings collected from multiple agents and scripts
  • One consolidated report with an overall health level, severity-ranked findings, and a prioritized action-item list
  • Appends findings to findings-log.jsonl so resolution can be tracked across consecutive runs
  • Honors a --skip list and project manifest overrides for extra agents and custom profiles

Limitations

  • Relies on an orchestrator agent, a profiles.json file, and helper scripts shipped with the repository but not included in the SKILL.md
  • The deep profile runs the full Gradle suite and can take around 45 minutes
  • The report is capped at 200 lines, so detailed findings get truncated
  • Its examples and conventions target a Kotlin/Android project (commonMain, .androidcommondoc)
When to use it

Use it before a release or during a periodic review when you need one prioritized picture of a project's architecture, code, security, and documentation health.

When not to use it

Avoid it for fixing one specific issue or checking a single dimension, and on projects missing the required orchestrator and profiles.json setup.

Security analysis

Caution
Quality score82/100

The skill orchestrates multiple audit agents and shell commands (e.g., Gradle coverage) for legitimate quality and security auditing. No destructive or exfiltrating instructions are present, and the structured protocols are benign. However, the use of Bash and Agent to execute potentially project-specific scripts carries a moderate level of inherent risk, warranting caution.

Findings
  • •Uses Bash and Agent to execute project-defined audit scripts, Gradle tasks, and agent workflows, which could run arbitrary code from the target repository if the repository is untrusted.
How this analysis is made

Examples

Full audit before a release
/full-audit --profile deep --output audit-report.md
Quick sanity check
/full-audit --profile quick --verbose
Standard audit on another repo, skipping coverage and sbom
/full-audit --project-root ../my-service --skip coverage,sbom

name: full-audit description: 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. intent: [audit, quality, architecture, security, docs, release, unified] allowed-tools:

  • Bash
  • Read
  • Grep
  • Glob
  • Agent
  • Write copilot: false

/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

| Profile | Waves | Gradle | Agents | Estimated Time | |---------|-------|--------|--------|----------------| | quick | 1-2 | No | No beta-readiness | ~5 min | | standard | 1-3 | Yes (coverage) | No beta-readiness | ~15 min | | deep | 1-4 | Yes (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)

From the file to a first result

The download contains exactly the content displayed on this page. This copy may differ from the latest version in the source repository.

View the source and supporting files

This download contains SKILL.md only. Any scripts, references, templates and dependencies are not included. Get the required files from the source, preserving their directory structure, before continuing.

1. Download the file

Download SKILL.md

From the root of a test project, save the file as .skill-downloads/full-unified-audit-ms47vp0t/SKILL.md, or use the command below. This folder is for inspecting the skill before installation.

Command for macOS/Linux or WSL: requires a POSIX shell and curl. On Windows without WSL, use the download button and create the folder manually.

mkdir -p '.skill-downloads/full-unified-audit-ms47vp0t' && curl --fail --show-error --location 'https://skills-guides.com/api/skills/full-unified-audit-ms47vp0t/download' --output '.skill-downloads/full-unified-audit-ms47vp0t/SKILL.md.part' && mv '.skill-downloads/full-unified-audit-ms47vp0t/SKILL.md.part' '.skill-downloads/full-unified-audit-ms47vp0t/SKILL.md'

2. Check prerequisites

Read SKILL.md before using it. If it references scripts or external services, inspect them and prepare the required access in your test environment.

No recognized prerequisites section in this file. This does not mean it is self-contained: libraries, tools and access requirements may be mentioned elsewhere in the content or source repository.

The platforms on this page are catalog indications. The paths below follow tool documentation; they do not prove this skill has been run in those tools. No minimum tool version is confirmed for this listing.

3. Load the skill

After inspection, copy the complete folder into your project using one of the commands below, then open a new tool session. The command stops if a folder with the same name already exists: compare the files before replacing it.

Claude Code
test -f '.skill-downloads/full-unified-audit-ms47vp0t/SKILL.md' && test -s '.skill-downloads/full-unified-audit-ms47vp0t/SKILL.md' && mkdir -p '.claude/skills' && test ! -e '.claude/skills/full-audit' && cp -R '.skill-downloads/full-unified-audit-ms47vp0t' '.claude/skills/full-audit'

OpenSkills

OpenSkills must already be installed. The local install/read procedure is checked with OpenSkills 1.5.0, which requires Node.js ≥ 20.6.0. Catalog slugs are not resolved automatically.

Official OpenSkills installation
openskills install './.skill-downloads/full-unified-audit-ms47vp0t'

openskills read 'full-unified-audit-ms47vp0t'

Reading should display the installed file content and its base directory. It does not run the skill or install its dependencies.

For an agent that reads AGENTS.md, then sync the index. This command changes AGENTS.md: review the diff before using it.

openskills sync

Manual method or another tool: attach SKILL.md to a conversation, or open it in an agent that can read files. Include any required supporting resources. No universal folder is recognized by every tool.

4. Try a first task

Use a short, synthetic input: an API endpoint, a small document or an interface brief. In a new conversation, attach the file or give the agent its path, then adapt this request:

Read .skill-downloads/full-unified-audit-ms47vp0t/SKILL.md and apply its instructions to this example: [describe a test input]. Identify any missing files, dependencies or access. Produce the result requested by the skill without inventing data or running unreviewed scripts.

Expected result: output matching the skill instructions, or a precise list of missing prerequisites. A read confirmation alone does not validate a first use. If an external resource is unavailable, that path remains untested.

Related skills