933 skills · sorted by relevance
Use a real browser to verify web pages and apps through short, supervised interactions. Capture screenshots, inspect errors and network requests, and document reproducible steps for UI bugs or expected behavior checks.
Organize a GitHub issue backlog by shared root cause, with one main tracking issue and design document per group. Route new reports into existing plans and prepare pull requests that address related bugs together with regression checks.
Review Ant Design GitHub issues and prepare responses, labels, and closure recommendations. It distinguishes bugs from feature requests, checks bot answers, and presents a complete plan for approval before making changes.
Maintain VoiceStudio by investigating reported bugs, reviewing contributed changes, diagnosing automated check failures, and preparing requested releases. It guides focused fixes, testing, and packaging verification for the Electron app and Python backend.
Connect Claude to external apps through Composio to send emails, create issues, post messages, and update data. It also supports linked tasks, such as summarizing GitHub issues and posting the results to Slack.
Analyze all open GitHub issues and pull requests, then produce reports backed by links to specific code commits. Assess bugs, feature requests, and merge readiness without changing anything on GitHub.
Test app interfaces on an Android emulator using ADB, a command-line device tool. Inspect element positions, perform taps and text entry, then check screenshots and React Native logs to verify behavior and investigate layout or interaction bugs.
Capture unexpected behavior and workarounds encountered while using Prisma 8, Prisma Compute, or Prisma Postgres. Record symptoms, causes, versions, and reproduction steps in a local log linked to a Linear ticket, checking for duplicates first.
Explore a web application as a user to find reproducible bugs and usability problems. Produce a structured report with reproduction steps, screenshots, and videos for interactive issues, giving responsible teams concrete evidence to investigate.
Review Python code for common mistakes in error handling, asynchronous operations, type annotations, and tests. Use a practical checklist and correction examples to guide code reviews, investigate bugs, and improve existing implementations.
Create technical documentation that people and AI can navigate by separating facts, context, known bugs, and uncertain claims. Convert existing Markdown to HADS, a structured documentation format, and check its required elements.
Build and debug sglang tests comparing token probabilities during prompt processing and step-by-step generation. Separate numerical differences from reused-state bugs, choose test thresholds, and locate the first operation that diverges.
Fix defects in Composio SDK through focused reproduction, root-cause analysis, regression tests that check for recurrence, and targeted verification. Use it for reported bugs, failing tests, CI regressions, runtime errors, or incorrect SDK behavior.
Reproduce Mastra Code bugs with a real model and compare timestamped logs across network, streaming, execution, and terminal interface layers. Use the evidence to locate timing problems, incorrect token rates, flicker, or stuck status displays.
Reviews pull requests for bugs, error handling, code quality, and style consistency. Organizes feedback into an overview, must-fix issues with file locations, improvement suggestions, and positive notes so reviewers can distinguish urgent problems from refinements.
Coordinate QA agents to plan testing for a game development sprint or feature. Produce test cases, collect results from human testers, document bugs and visual evidence, and prepare a sign-off report based on recorded findings.
Create a game playtest report template or turn session notes into organized feedback. Separate gameplay problems from bugs, compare observations with design intent, and identify priorities for design changes, balance adjustments, and polish.
Compare existing game tests with key paths in the game design document, find fixed bugs without tests to catch recurrence, and identify coverage gaps from new features. Maintain a release checklist of existing tests.
Investigate Apache ShardingSphere issues using official documentation, code, tests, and issue discussions. Distinguish bugs, unsupported usage, duplicates, and enhancement requests, then draft a concise maintainer-style reply explaining the evidence and next action.
Review code for security risks, logic bugs, and performance problems. Receive specific feedback explaining the affected lines or patterns, why they matter, and how to fix them, with required changes separated from optional improvements.
Review GitHub pull requests with specialized agents that check for clear bugs and violations of project instructions in CLAUDE.md. Validate bug findings before posting focused comments on the affected lines, with fix suggestions where appropriate.
Diagnose errors and incorrect inference results in MNN's QNN backend for Qualcomm HTP processors. Compare intermediate calculation data against CPU results to locate the first faulty operator, distinguish bugs from precision limits, and guide operator support and performance fixes.
Turn GitHub issue reports into actionable work by searching for duplicates, attempting reproduction, and assessing user impact. Organize issues with existing labels, appropriate owners, and milestones, while clearly recording what was and was not verified.
Review code changes and files for bugs, security risks, performance problems, design issues, and test coverage. Receive a structured report with prioritized findings, concrete improvement examples, positive feedback, and an overall review verdict.