compose-audit

Audit Jetpack Compose and Compose Multiplatform codebases for performance and correctness issues.

1|1|Updated May 23, 2026
One-click install
npx skills add https://github.com/santimattius/performance-compose-skills --skill compose-audit
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: compose-audit
Source: https://github.com/santimattius/performance-compose-skills/tree/main/skills/compose-audit
Command: npx skills add https://github.com/santimattius/performance-compose-skills --skill compose-audit

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes references (resource) and assets (resource) components.

What problem does it solve?

It identifies performance and correctness issues in Jetpack Compose and Compose Multiplatform codebases, then produces a severity-ranked audit that points directly to the canonical remediation skills.

Core Features & Use Cases

  • 3-phase, performance-first audit: prioritizes Composition restart risks, then classifies Layout/Drawing evidence into warning or suggestion tiers.
  • Discovery → scan → severity → routing workflow: detects project shape and Compose/CMP setup, runs pattern-based static scans, applies a severity rubric, and routes each finding to the correct downstream skill.
  • CMP-aware validation: applies platform/source-set rules for commonMain and version-gated lifecycle/navigation expectations, using context7 for documentation checks.
  • Actionable reporting contract: emits a structured report template including caps, evidence snippets, docs consulted, and a “Next Skills to Load” list.

Quick Start

Use compose-audit to review your project by asking: "audit my Compose project and route performance issues to the right fix skills."

Frequently Asked Questions about compose-audit

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

FAQPage Schema
How do I audit Jetpack Compose code for performance issues?

To audit Jetpack Compose code, run a context-aware static analysis scan that detects composition restart risks, classifies layout and drawing evidence by severity, and routes findings to downstream remediation skills.

How does static pattern scanning detect Compose composition restart risks?

Static pattern scanning detects composition restart risks by applying a severity rubric to code patterns, prioritizing unnecessary recompositions before evaluating layout and drawing phases for warnings or suggestions.

Can I run a Compose Multiplatform audit on commonMain source sets?

Yes, Compose Multiplatform audits apply platform-specific validation rules for commonMain source sets, checking version-gated lifecycle and navigation expectations using documentation context to ensure cross-platform correctness.

What is the best way to triage Compose performance findings by severity?

The best way to triage Compose performance findings is applying a severity rubric that classifies evidence into performance-first tiers, enforcing caps and evidence snippets before routing each finding to canonical remediation skills.

How do I route Compose code review findings to the correct fix skills?

Routing Compose code review findings uses canonical routing tables that map each detected performance issue across composition, layout, and drawing phases directly to a downstream remediation skill listed in the structured report.

What limitations exist when auditing Compose Multiplatform lifecycle expectations?

Auditing Compose Multiplatform lifecycle expectations is limited by version-gated constraints, requiring documentation checks and applying source-set rules for commonMain to validate platform-specific navigation and lifecycle behavior accurately.