“regressions”的搜索结果

Classify failures in CI, automated checks run during development, to distinguish code regressions, temporary infrastructure problems, security test failures, and inconsistent results. Record each failure's category, suggested next action, and attempt count in a structured report.

中文简介正在准备中。当前显示英语简介。

• Sort failed CI checks by likely cause
• Identify small regressions that may qualify for automatic fixes
• Refer infrastructure and security failures to a human

Investigate failing macOS tests in Xcode or SwiftPM by running a focused test scope, classifying errors, and separating setup issues from code regressions. Get a concise explanation of likely causes and the next verification step.

中文简介正在准备中。当前显示英语简介。

• Narrowing down failing macOS tests
• Distinguishing setup issues from code regressions
• Investigating assertions and crashes

Checks whether a new version of a repository preserves the behavior observed by tests on the old version. Use this skill when comparing two versions of code to detect regressions, verify refactoring safety, validate bug fixes don't break existing functionality, or ensure backward compatibility. Detects differences in function outputs, exceptions, observable states, and performance between versions. Generates reports highlighting potential regressions (critical, high, medium, low severity), improvements, and areas requiring verification. Triggers when users ask to check for regressions between versions, compare test behavior across versions, verify behavior preservation, or validate that changes don't break existing tests.

中文简介正在准备中。当前显示原文说明。

测量网页加载与交互、API响应以及构建和测试的耗时，对比修改前后的结果，并以通过Git共享的基准值检查性能是否下降。

• 比较代码修改前后的性能
• 调查页面缓慢的反馈
• 发布前检查性能目标

在修改代码前调查原因不明的故障、间歇性异常和性能下降，区分实测症状与推测，依据证据筛选原因假设，并报告原因及其依据。

• 调查原因不明的故障
• 查找间歇性异常的原因
• 定位性能下降的原因

Measure and optimize claude-flow v3 startup, search, attention processing, and memory use. Compare benchmarks against performance targets, track changes over time, and identify regressions to guide further optimization.

中文简介正在准备中。当前显示英语简介。

• Compare performance before and after v3 optimization
• Evaluate vector search speed and memory use
• Track performance regressions over time

Measure code performance and run benchmarks to investigate slow operations, regressions, or memory pressure. Establish a baseline, compare results under matching conditions, report variability, and rerun correctness tests after optimization.

中文简介正在准备中。当前显示英语简介。

• Investigate slow operations
• Compare performance before and after a change
• Measure performance when memory pressure occurs

Check a codebase for known dependency vulnerabilities, hard-coded secrets, and risky code patterns using Ruflo security tools. Choose a scan depth, inspect matching lines, and report verified concerns with a clear account of what was checked.

中文简介正在准备中。当前显示英语简介。

• Checking pull requests for security regressions
• Inspecting authentication and input-handling code for risky patterns
• Running security checks before production deployment

Track documented code fixes across releases with a signed manifest, a list of fixes and their identifying text. Verify that markers remain in source files, inspect file changes, and use recorded history to identify commits associated with regressions.

中文简介正在准备中。当前显示英语简介。

• Check that documented fixes remain before a release
• Trace a regression through release history
• Verify signed fix records in CI

Measure and optimize claude-flow v3 startup, search, attention processing, and memory use. Compare benchmarks against performance targets, track changes over time, and identify regressions to guide further optimization.

中文简介正在准备中。当前显示英语简介。

• Compare performance before and after v3 optimization
• Evaluate vector search speed and memory use
• Track performance regressions over time

Investigate SGLang serving failures by collecting server state, preserving failing requests, and replaying them on a clean target. Summarize evidence and likely causes, then choose the next debugging tool for crashes, stalls, or performance regressions.

中文简介正在准备中。当前显示英语简介。

• Investigate failed health checks and growing queues
• Reproduce request-specific timeouts or crashes
• Investigate output changes after deployment

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.

中文简介正在准备中。当前显示英语简介。

• Reproducing and fixing reported SDK bugs
• Investigating failing tests
• Fixing regressions in automated CI checks

Re-review a pull request after new commits arrive. Check every previous finding, inspect the new changes for regressions, and review the full current change. Run relevant verification and publish a test report and review verdict within Factory.

中文简介正在准备中。当前显示英语简介。

• Checking whether previous review findings were addressed
• Finding regressions introduced by follow-up commits
• Re-running tests against the current PR head

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.

中文简介正在准备中。当前显示英语简介。

• Investigating a package suite failing on main
• Finding the PR that first broke a test
• Distinguishing outdated tests from code regressions

Design evaluation systems that measure agent results across accuracy, completeness, citations, and tool efficiency. Build repeatable tests, compare changes against a baseline, and define quality checks that catch regressions before deployment and monitor production performance.

中文简介正在准备中。当前显示英语简介。

• Compare agent configurations against a baseline
• Catch quality regressions before deployment
• Measure the effects of context strategies

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.

中文简介正在准备中。当前显示英语简介。

• Investigating garbled or degraded MNN output
• Comparing results across execution backends
• Tracking regressions after optimization changes

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.

中文简介正在准备中。当前显示英语简介。

• Review interface changes in a pull request
• Check whether shared component changes affect other screens
• Find accessibility regressions before merging

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.

中文简介正在准备中。当前显示英语简介。

• Checking structural security changes before merging a PR
• Reviewing call paths after a security fix
• Assessing attack surface changes in a release

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.

中文简介正在准备中。当前显示英语简介。

• Validate an AI-generated security patch before review
• Check related attack variants for incomplete fixes
• Check whether a fix breaks normal behavior

Improve code through repeated changes, checks, and decisions to keep or discard each result. Start with a goal or measurable target, limit iteration counts, and review logs for progress, stalled improvements, or regressions.

中文简介正在准备中。当前显示英语简介。

• Improve code against a measurable target
• Investigate and fix recurring errors
• Check whether changes introduce regressions

Diagnose difficult bugs and performance regressions by first building a repeatable check for the exact symptom. Minimize the reproduction, test ranked hypotheses, apply a fix, and verify the original scenario with regression tests where suitable.

中文简介正在准备中。当前显示英语简介。

• Investigating persistent errors or incorrect output
• Increasing reproduction rates for intermittent bugs
• Measuring and diagnosing performance regressions

SEO drift monitoring — snapshot a site's SEO state and detect regressions over time. Captures a baseline (rankings/positions, indexed page count, titles & meta descriptions, canonical/robots directives, schema presence, key on-page elements) and on later runs diffs against it to surface what changed: ranking drops, pages that fell out of the index, titles/metas that were accidentally overwritten (a CMS/redeploy classic), canonicals or noindex flipped, schema that disappeared. Use this skill when the user wants to monitor SEO over time, catch regressions after a site change / migration / redeploy, set a baseline, diff against a previous state, or asks "what changed on my site's SEO" or "did my redesign break SEO". Trigger on: "SEO drift", "SEO monitoring", "track SEO over time", "did my site change break SEO", "after migration SEO", "SEO regression", "baseline my SEO", "compare SEO to last month", "my titles changed", "pages fell out of the index". For a one-time full audit use /seo-analysis.

中文简介正在准备中。当前显示原文说明。

Compare current benchmark results against historical baselines to spot performance regressions. Use as an explicit/manual helper for build-to-build degradation review, not for broad optimization strategy or low-level profiling ownership.

中文简介正在准备中。当前显示原文说明。

Review .NET changes for bugs, regressions, architectural drift, missing tests, incorrect async or disposal behavior, and platform-specific pitfalls before you approve or merge them. USE FOR: reviewing a pull request or patch in a .NET repository; checking for behavioral regressions, API misuse, or missing tests; auditing architectural or framework-specific. DO NOT USE FOR: unrelated stacks; generic tasks that do not need this specific guidance. INVOKES: inspect the repository context, edit targeted files, and run relevant build, test, lint, or validation commands when changes are made.

中文简介正在准备中。当前显示原文说明。