955건 · 관련도순
Analyze time until events such as recovery or relapse using Python. Account for censored observations, where the event has not been observed, create survival curves, compare groups, and estimate risk factors with Cox regression.
한국어 요약은 준비 중입니다. 영어 요약을 표시하고 있습니다.
Build a reproducible Stata analysis from data cleaning through modeling, diagnostic checks, and robustness tests. Generate runnable .do files, regression tables, and figures for empirical papers, with additional workflows for epidemiology and machine learning approaches to causal inference.
한국어 요약은 준비 중입니다. 영어 요약을 표시하고 있습니다.
Build and evaluate Bayesian models with PyMC and ArviZ, from choosing initial assumptions to checking predictions. The workflow covers sampling diagnostics, model comparison, and reports that explain results with uncertainty intervals.
한국어 요약은 준비 중입니다. 영어 요약을 표시하고 있습니다.
Inspect Agent activity in Observal through execution records, sessions, ratings, logs, and insight reports. Use the evidence to investigate telemetry problems, costs, and performance regressions, then identify practical next steps while accounting for limited data.
한국어 요약은 준비 중입니다. 영어 요약을 표시하고 있습니다.
Diagnose bugs, intermittent failures, and performance regressions through structured logging and reproduction. It ranks possible causes with confidence scores, tests competing explanations, and reports whether the evidence proves the cause or leaves the diagnosis incomplete.
한국어 요약은 준비 중입니다. 영어 요약을 표시하고 있습니다.
Review a git diff or selected files with parallel agents to find behavior regressions, security risks, reliability problems, and compatibility or test gaps. Receive filtered, evidence-backed findings and prioritized recommendations without changing files.
한국어 요약은 준비 중입니다. 영어 요약을 표시하고 있습니다.
End-to-end R data analysis pipeline — exploration → cleaning → regression → publication-ready tables and figures. Use when user says "analyze this dataset", "run a regression on X", "explore this CSV", "full analysis workflow", "get me summary stats and a regression", or points at a `.csv`/`.rds`/`.dta` and asks for empirical results. Produces numbered R scripts in `scripts/R/` and outputs to `output/`.
한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.
Compare this period's reliability against the prior period using Agent Monitor data — error rate (APIError/total) and tool-failure rate (PreToolUse→PostToolUse gap) — flag any regression where reliability got worse, and optionally wire a persistent alert rule so the dashboard catches the next regression automatically. Use when checking whether reliability degraded.
한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.
Disciplined diagnosis loop for hard bugs and performance regressions. Reproduce → minimise → hypothesise → instrument → fix → regression-test. Use when user says "diagnose this" / "debug this", reports a bug, says something is broken/throwing/failing, or describes a performance regression.
한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.
Disciplined diagnosis loop for hard bugs and performance regressions. Reproduce → minimise → hypothesise → instrument → fix → regression-test. Use when user says "diagnose this" / "debug this", reports a bug, says something is broken/throwing/failing, or describes a performance regression.
한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.
Turn a vague bug report into a VERIFIED minimal reproduction and then a failing regression test, agent-driven end to end. Covers extracting the implicit repro from a thin report (env, build, steps, data), the reproduce-minimize-isolate-capture loop, git bisect to find the introducing commit, building a deterministic minimal repro (fixed seeds, frozen time, stubbed network), writing the failing regression test BEFORE the fix (red) and confirming the fix flips it green, and writing repro evidence back into the ticket. Distinguishes flaky-not-reproducible from environment-specific. Use when: "reproduce this bug," "minimal reproduction," "repro steps," "find the commit that broke it," "git bisect," "make the repro deterministic," "write a failing test for this bug," "regression test for a defect," "can't reproduce this bug." Not for: Classifying/deduplicating/severity-routing existing failures without reproducing them — that is ai-bug-triage. Generating tests from specs rather than from a defect — that is ai-test-generation. Related: ai-bug-triage, ai-test-generation, test-reliability, systematic-debugging, qa-project-context.
한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.
Chromatic is a visual testing service from the Storybook team that snapshots every story in a cloud browser and shows visual diffs for review on each pull request. Use when the user wants visual regression testing with Storybook, or mentions "chromatic," "visual regression," "Storybook testing," "UI review," "visual diff," or "component snapshot testing." For general screenshot comparison, see percy.
한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.
Generate unit, integration, E2E, and visual regression tests following the Testing Trophy methodology (80% integration). Covers Vitest/Jest, Testing Library, Playwright, MSW for API mocking, snapshot strategy, visual regression (Chromatic/Percy/Playwright), test factories with Faker, and CI sharding. Use when user asks to write tests, set up testing framework, mock API/dependencies, improve coverage, or add visual regression. Do NOT use for performance/load testing, production monitoring, or type testing (covered by TypeScript).
한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.
Map test coverage to GDD critical paths, identify fixed bugs without regression tests, flag coverage drift from new features, and maintain tests/regression-suite.md. Run after implementing a bug fix or before a release gate.
한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.
Build automated regression suites — golden sets, threshold alerting, CI integration for model changes. Use when asked to "catch model regressions in CI", "build a golden set", or "automate eval regression".
한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.
Reproduce and repair a bounded Proto UI regression whose expected behavior and owning layer are already governed. Use this before domain implementation skills whenever work starts from a reproducible failure, including bug fixes, drift repairs, broken exports, Runtime failures, Adapter parity defects, Prototype defects, or public-projection regressions. Do not use when expected semantics or ownership is unresolved.
한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.
Disciplined diagnosis loop for hard bugs and performance regressions. Reproduce → minimise → hypothesise → instrument → fix → regression-test. Use when user says "diagnose this" / "debug this", reports a bug, says something is broken/throwing/failing, or describes a performance regression.
한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.
Use when setting up visual regression testing with Playwright - toHaveScreenshot baselines, masking dynamic content, handling animations, full-page and element screenshots, cross-browser runs, CI integration, VUDA MCP tooling, or debugging flaky visual diffs
한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.
The measurement surface for ALL Pulp DSP and audio-pipeline work — read it BEFORE writing or gating DSP, not only when something already sounds wrong. Covers the C++ harness (signal generators, metrics, assertions, RenderScenario, contracts), the offline Audio Doctor (magnitude/frequency response, THD/THD+N, phase/group delay), and their Python sibling the Audio Quality Lab (tools/audio/quality-lab — null residual + alignment, LTAS log-spectral distance, spectral flux/centroid, HNR, Theil-Sen drift slope, Kaiser-sinc resampling, license-guarded corpus, regression-net ratchet). TRIGGER on AUTHORING work — "build/design an oscillator/filter/synth/effect", "add a DSP module", "what should the acceptance gate be", "how do I measure aliasing / anti-aliasing / alias floor", "null against a reference", "is this DSP correct", "choose a tolerance", "golden/regression corpus for audio", "measure drift or jitter", "A/B two renders" — AND on DEBUGGING work — "is there sound / no audio / I hear nothing", "does this filter/compressor/synth/delay produce the right signal", "prove the DSP / prove the contract", "measure the frequency response", "what's the THD / is it distorting", "what's the group delay / phase response / measured latency", "magnitude response curve", "render a test tone and assert", "audio regression", "64-frame works but 128 is silent", "sample-rate change pitch-shifted it", "describe what's in this buffer", "audio doctor", "compare before/after a DSP refactor". Reach for this BEFORE hand-rolling any FFT, null test, alias measurement, pitch tracker, or golden-render script — most of it already exists in one of the two lanes. Test/tool layer over HeadlessHost — deterministic, no audio device, no speakers. Off the realtime thread entirely.
한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.
Set up, format, fix, and clean up LaTeX regression and estimation tables in empirical economics or finance papers. Use when (a) creating a .tex, results.tex, main.tex, or preamble to display regression or estimation output from Python (pyfixest), Stata, or R — including any mention of estout, esttab, estauto, estwide, or table fragments; (b) formatting or repairing estout-style regression tables that overflow the right margin, have cramped or boxed notes, misaligned columns, or poor significance stars, or when asked to match a reference paper, make the note fill the table width, or choose among \estwide, \estauto, and landscape layouts; (c) diagnosing "Misplaced \omit" errors from \input-ed table fragments inside tabular environments. Covers \@@input, \estwide, \estauto, \estautoLT, \specialcell, \sym, minipage notes below tabulars, and the convert-and-verify workflow. Do NOT trigger for general LaTeX documents like beamer presentations, problem sets, letters, or CVs.
한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.
Map test coverage to GDD critical paths, identify fixed bugs without regression tests, flag coverage drift from new features, and maintain tests/regression-suite.md. Run after implementing a bug fix or before a release gate.
한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.
Diagnose Yuzu bugs and performance regressions with a disciplined reproduce-minimize-hypothesize-instrument-fix-regression-test loop. Use when the user says `/diagnose`, "debug this", reports a failure, flake, broken behavior, or performance regression.
한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.
Use when testing, evaluating, or building regression suites for Agentforce agents: conversation testing in Agent Builder, topic (now subagent) coverage and utterance testing, Testing API and AiEvaluationDefinition metadata, Agentforce DX CLI test runs (sf agent generate test-spec, sf agent test create/run/resume/results/list), evaluation metrics (containment rate, escalation rate, CSAT, topic activation accuracy), and post-deploy analytics via Enhanced Event Logs. Triggers: 'how do I test my Agentforce agent', 'agent routes to wrong subagent', 'write utterance tests', 'regression test after topic change', 'measure agent quality', 'agent containment rate', 'run agent tests from the CLI'. NOT for agent creation, topic design, or action contract design — use agentforce/agentforce-agent-creation, agentforce/agent-topic-design, or agentforce/agent-actions respectively.
한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.
Check a change for performance regression against this machine's recorded baseline - decide whether the diff needs checking, run the deck benchmark under the hygiene wrapper, and attribute any regression to an element. Use before opening a PR that touches the simulation hot path.
한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.