fix▌

Automated code formatting and linting to resolve style issues before CI checks. \n \n Runs Prettier for code formatting and linc for lint validation in sequence \n Identifies remaining manual fixes needed after automated corrections \n Prevents CI failures by catching formatting and lint errors before commit \n

Design and audit internal link structures using hub-and-spoke topology, PageRank flow, and anchor text optimization. \n \n Supports five architecture models (hub-and-spoke, silo, flat, pyramid, mesh) with guidance on which fits different site sizes and content types \n Includes orphan page detection, link depth analysis, and anchor text diversity assessment to identify ranking barriers \n Provides concrete link injection plans with source pages, target pages, anchor text suggestions, and priorit

[Extended thinking: This workflow implements a sophisticated debugging and resolution pipeline that leverages AI-assisted debugging tools and observability platforms to systematically diagnose and resolve production issues. The intelligent debugging strategy combines automated root cause analysis with human expertise, using modern 2024/2025 practices including AI code assistants (GitHub Copilot, Claude Code), observability platforms (Sentry, DataDog, OpenTelemetry), git bisect automation for reg

Systematic workflow for verifying bug fixes to ensure quality and prevent regressions.

Use gh to locate failing PR checks, fetch GitHub Actions logs for actionable failures, summarize the failure snippet, then propose a fix plan and implement after explicit approval.

Workflow orchestrator for bug investigation and resolution. Chains specialized skills based on issue scope.

Diagnose and fix a Playwright test that fails or passes intermittently using a systematic taxonomy.

Verify that fix commits properly address audit findings without introducing new bugs or security vulnerabilities.

Verifies security audit fixes are correctly implemented without introducing new bugs. \n \n Analyzes commit ranges against security findings (Trail of Bits format, numbered findings, or JSON) to confirm root causes are addressed, not just symptoms \n Assigns status to each finding: FIXED, PARTIALLY_FIXED, NOT_ADDRESSED, or CANNOT_DETERMINE, with evidence linking commits to specific code changes \n Detects bug introduction patterns including access control weakening, validation removal, error han

When fixing an unhandled error from the telemetry dashboard, the issue typically contains an error message, a stack trace, hit count, and affected user count.