platform-sweep

Audit web platform health across UX, code, security, dependencies, and performance.

Updated Aug 23, 2026
One-click install
npx skills add https://github.com/escotilha/claude-public --skill platform-sweep
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: platform-sweep
Source: https://github.com/escotilha/claude-public/tree/main/skills/platform-sweep
Command: npx skills add https://github.com/escotilha/claude-public --skill platform-sweep

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Platform Sweep helps teams reduce technical risk by finding and prioritizing issues across UX, code quality, security, dependencies, and performance, then applying fixes safely after approval.

Core Features & Use Cases

  • Parallel multi-track audits: Runs dedicated agents for UX/page issues, code cleanup signals, security review, dependency health, and performance analysis.
  • Consolidated, severity-ranked reporting: Normalizes findings into a single prioritized report that’s easier to plan and execute.
  • Guardrailed auto-fixes with worktrees: Creates isolated git worktrees per fix group, applies changes in parallel, and verifies before merging.

Quick Start

Run Platform Sweep on your current project with URL auto-detection and full auditing: execute /platform-sweep and approve the fix plan when prompted.

Frequently Asked Questions about platform-sweep

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

FAQPage Schema
How do I run a comprehensive platform health audit before a release?

A platform health audit runs parallel agents across UX, code cleanup, security, dependencies, and performance, consolidating findings into a severity-ranked report. It targets pre-release stability checks and periodic technical health routines for web platforms.

Can I automatically remediate security and dependency issues without breaking production?

Yes, automated remediation applies fixes via isolated git worktrees and runs verification before merging. Destructive changes are gated behind explicit user approval, ensuring production safety during security and dependency updates.

What is the best way to prioritize technical debt across multiple engineering domains?

Run a parallel multi-track audit that normalizes UX, security, code quality, dependency, and performance findings into a single severity-ranked report. This consolidation makes it easier to plan and execute technical debt remediation.

Does the platform audit require Lighthouse evidence for performance testing?

Lighthouse evidence is optional for the performance analysis track. The audit orchestrates multiple delegated skills to cover performance optimization, but it can run without Lighthouse by relying on other delegated performance analysis agents.

How do I verify incident-driven security and dependency fixes safely?

Verify incident-driven fixes by applying changes in isolated git worktrees per fix group and running verification checks before merging. Destructive changes are gated behind explicit approval to ensure platform stability during security and dependency verification.