983 skills · sorted by relevance
Trace failing cmux Swift package tests to the commits that introduced them by running older revisions in CI, the automated testing environment. It helps distinguish outdated expectations, code regressions, and intermittent failures, then guides focused fixes and verification.
Write regression tests that catch recurring bugs in FastMCP changes using pytest. Covers reproducing failures before a fix, testing requests without a network server, and checking outgoing requests while replacing external services with test substitutes.
Add Storybook stories, examples of component states, for the Kilo VS Code extension UI. The existing Playwright runner turns them into screenshot comparisons to check visual changes across states and widths.
Refine a game feature or area through performance measurement, visual and audio polish, and stress and regression testing. Report before-and-after metrics, remaining issues, and release readiness, with work limited to the enabled team roles.
Build Handsontable demo pages for visual regression tests, which compare screenshots for appearance changes. It guides feature routes, URL-driven display states, sample data, and decisions about testing the same feature across framework wrappers.
Review Apache ShardingSphere pull requests or authorized downstream changes using repository evidence. Assess code correctness, merge readiness, or CI failures, then produce consolidated findings or a ready-to-copy reply to a review discussion.
Evaluate AI agent outputs with code checks and model-based grading. Run repeated trials to measure reliability, compare prompts or models, and check whether changes reduce quality, with saved transcripts for reviewing the results.
Save a page's SEO settings and compare them with later versions to detect changes after updates or deployments. Review differences in titles, headings, indexing controls, structured data, and available performance metrics, with severity levels and stored comparison history.
Implement an authorized fix for a reviewed security issue, check the plan against current code, and add regression tests to catch recurrence. Verify affected components and open a pull request that closes the issue while respecting disclosure rules.
Triage incorrect MNN outputs and regressions by matching symptoms to focused debugging guides. Use backend comparisons, minimal reproductions, and controlled experiments to investigate memory issues, quantization, concurrency, numeric limits, caches, and inconsistent results across runs.
Analyze failures in CI, the automated checks run during development. Identify the failing job and step, classify the likely cause, and suggest a small fix, continued monitoring, or human review.
Assess a fixed patch or pull request diff before merging. Trace affected behavior, evaluate regression risks, tests, and recovery options, then provide an evidence-based recommendation and advisory automatic-merge eligibility without modifying or merging the patch.
Investigate a bug's root cause, implement a focused repair, and verify the same behavior before and after the change. Select lasting regression tests, preserve reproduction evidence, and record the corrected user journey when possible.
Investigate Bifrost GitHub issues by examining reports, related code, and library documentation. Produce an implementation plan with impact analysis and regression tests, including a demonstrated failing test for bugs before requesting approval to fix them.
Review a branch, pull request, or uncommitted changes for interface problems involving accessibility, layout, text, typography, and color. The report distinguishes newly introduced issues, regressions, and existing problems, including effects on screens that use changed components.
Handle one known local bug or testable bug hypothesis through reproduction, independent validation, repair, and regression checks. Produce a local patch commit and evidence reports that help reviewers judge whether the fix is ready.
Build and run systems before and after a change, then execute the same reproduction procedure against both. Save environment details, inputs, commands, and separate logs to document observed behavior and any setup blockers.
Compares code relationships before and after a branch, pull request, or release change using Trailmark. Flags structural security regressions, such as removed authorization checks or newly reachable sensitive operations, and provides evidence for reviewers.
Validate security patches by comparing vulnerable and patched code against exploit tests, related attack variants, and normal behavior. Produce reproducible logs showing remaining flaws, regressions, newly introduced security failures, and gaps that still need testing.
Assess a fixed code patch for behavior changes, regression risks, test coverage, and recovery options. Receive an evidence-based report and structured assessment indicating whether it is ready to merge and qualifies as an automatic merge candidate.
Review Python changes against shared team standards to find bugs, missing regression tests, and security issues. Findings are ordered by severity and include file names and line numbers so reviewers can locate each problem.
Compare Sentry issues across selected time windows and releases to find new or recurring problems and changes in frequency or affected users. Prioritize findings using user impact and the strength of available evidence.
Test browser games through repeatable game states and short real playthroughs. Check controls, progression, saves, device layouts, and visible feedback, then report bugs with reproduction steps, severity, and browser evidence.
Implement and tune Three.js game cameras so players, threats, and objectives stay readable. Covers smooth following, isometric views, zoom and orbit limits, obstruction handling, target lock-on, camera shake, touch controls, and checks for regressions.