873 skills · sorted by relevance
Add a reported Remotion bug to the bugs API with its affected versions, a short title, and upgrade guidance. Follow the existing entry format and place the new record first so recent bugs appear at the top.
Use when the user says "review bugs", "/review-bugs", "pull new bugs", "what was reported in Bugs", "update the bug list", or asks for an auto-review of reported bugs. Pulls the new messages from the Voxt Bugs and Bugs (Mobile) chats, turns them into entries in docs/bugs.md, reconciles the list with GitHub issues, pull requests and dev commits, moves finished bugs to docs/bugs-closed.md, and lists what needs a human decision.
The English summary is being prepared. Showing the original description.
Automate Bugsnag operations through Rube MCP and Composio. The skill identifies available tools, reads their current input requirements, checks the service connection, and follows the discovered specifications to run supported tasks.
Automate Bugsnag operations through Rube MCP and Composio. The skill identifies available tools, reads their current input requirements, checks the service connection, and follows the discovered specifications to run supported tasks.
Review open Mastra GitHub issues and trace reported defects to source code. Apply the @mastra/core label to confirmed core bugs, report uncertain ownership, and summarize whether fixes are active, stale, or unclaimed.
Review unresolved game bugs by separating impact from urgency, then recommend repair priorities and sprint assignments, meaning work planned for a development cycle. Reports also highlight recurring problems, older issues, and bugs in previously completed work.
Add browser WebCodecs bugs to the Remotion Mediabunny documentation. It checks the linked issue’s title, filing date, reporter, and resolution, then adds a table row while preserving the existing format.
Reproduce timing and ordering bugs in a CTF sandbox using controlled concurrent requests. Compare normal and racing runs, trace reads and writes, and preserve a minimal sequence that demonstrates duplicate actions or inconsistent state.
Investigate bugs and slow applications through reproducible examples, logs, environment comparisons, and hypothesis testing. The skill structures root cause analysis and performance measurement, helping developers narrow down failures and verify that a fix works.
Turn game bug descriptions or suspected code problems into structured reports with reproduction steps, severity, and priority. Follow reported bugs through fix verification and closure, recording test results or manual checks before marking an issue closed.
Prepare a game's launch day patch by selecting known bugs that are safe to fix quickly. Coordinate minimal fixes, verify affected areas, and document deferred issues, quality checks, rollback procedures, and patch notes.
Writes, reviews, and debugs property-based tests, which generate inputs to check general rules. Helps test conversions, parsers, normalization, and state invariants, assess whether existing assertions are meaningful, and distinguish faulty rules from implementation bugs.
4人の異なる専門家ペルソナ（20年ベテランエンジニア、TDDエキスパート、Clean Codeエキスパート、バグハンター）で ソースコードを批判的にレビューするスキル。設計判断、テスト容易性、可読性、バグ検出の観点から コードの問題を検出し、改善提案を行う。Python/JavaScriptに対しては追加のチェックポイントを適用。 バグハンターは状態遷移、例外パス、依存関係、非同期競合に特化し、本番環境での問題を事前に検出する。 Use when reviewing source code from multiple expert perspectives to find design flaws, testability issues, code quality problems, and runtime bugs. Triggers: "critical code review", "multi-persona code review", "expert code review", "code quality assessment", "find bugs".
The English summary is being prepared. Showing the original description.
コードベースの規模に応じた目標値計算、倍増エスカレーション、領域追跡、最終検証を備えた体系的なバグスウィープ。/bugsweep 実行時や体系的なバグ調査が要求された場合に使用します。
The English summary is being prepared. Showing the original description.
Investigate difficult bugs and performance slowdowns by building a repeatable test or script that detects the exact symptom. Reduce the failing case, compare possible causes, and verify the fix with checks that catch the bug if it returns.
Review code changes for bugs, security risks, failures under expected usage, missing tests, slow paths, and unnecessary code. Receive prioritized findings with concrete failure cases, small fixes, and the consequences of leaving each issue unresolved.
Find and fix bugs in websites, APIs, command-line tools, and background processes. Choose from three testing depths, verify fixes, and receive evidence of the changes plus a summary of readiness for release.
Investigate bugs in browser flows, APIs, command-line tools, background jobs, workers, and webhooks. Produce a structured report with reproduction steps and evidence or browser scores, without changing code to fix the issues.
Organize GitHub issues and pull requests found during quality assurance testing. Apply release tracking labels, classify bugs by four severity levels, and label multiple findings while keeping documentation issues and feature requests outside the severity scheme.
Investigate WorldMonitor production errors using Sentry event details and source code. Classify issues as noise, already fixed, product bugs, ingestion problems, or needing human review, with tested fixes when code changes are requested.
Review code for security flaws, bugs, performance problems, maintainability, and test quality. Produce structured feedback with issue locations, likely impact, suggested fixes, positive observations, and a recommendation on whether changes are ready to merge.
Set up or review production error monitoring to capture unhandled errors, failed requests, and performance signals. Check event context, release labels, and alert routing so teams receive useful information when problems occur.
Operate and test terminal apps without a display using named background sessions. Wait for visible screen changes, send keystrokes, reproduce Cline CLI bugs, capture text or PNG evidence, and write automated tests of interactive behavior.
Review code changes in a diff, pull request, branch, or file path to identify bugs and cleanup opportunities. Findings include file locations and concrete failure scenarios, with options to apply fixes or post comments.