Use when reviewing pull requests, fixing CI failures, addressing review comments, resolving threads, cleaning commit history, getting a PR to mergeable state, or managing GitHub issues. Triggers include "check PR", "fix CI", "failing tests", "review comments", "resolve threads", "squash commits", "rebase", "DIRTY merge", "open issues", "close issue", or any request to review, merge, or track work in GitHub.
Analyze and fix SonarCloud quality gate issues. Use when the user mentions SonarCloud, SonarQube, quality gate failures, bugs, vulnerabilities, code smells, hotspots, duplications, or coverage. Goal: get Reliability and Security to grade "A". Scripts below eliminate API guesswork — run them first to gather facts, then fix code or accept via API as appropriate.
Browser automation CLI for AI agents. Use when the user needs to interact with websites, including navigating pages, filling forms, clicking buttons, taking screenshots, extracting data, testing web apps, or automating any browser task. Triggers include requests to "open a website", "fill out a form", "click a button", "take a screenshot", "scrape data from a page", "test this web app", "login to a site", "automate browser actions", or any task requiring programmatic web interaction. Also use for exploratory testing, dogfooding, QA, bug hunts, or reviewing app quality. Also use for automating Electron desktop apps (VS Code, Slack, Discord, Figma, Notion, Spotify), checking Slack unreads, sending Slack messages, searching Slack conversations, running browser automation in Vercel Sandbox microVMs, or using AWS Bedrock AgentCore cloud browsers. ALSO use for inspecting and debugging the two JCEF panels (chat console and tool calls) embedded in this IntelliJ plugin — they run on CDP port 9222. Prefer agent-browser