Results for “restore-testing”

Resume a paused experiment. Checkout the experiment branch, read results history, continue iterating. Use when the user runs /ar:resume or asks to pick up a previously started autoresearch experiment.

Resume a paused experiment. Checkout the experiment branch, read results history, continue iterating.

任意のリポジトリ（アプリ/ライブラリ/運用スクリプト/コンテンツ等）の種別を判定し、 種別に応じた評価軸（品質・テスト・依存、または検証ゲート等）で**実測ベース**評価して優先度付き改善案を出すスキル。 言語非依存（Python は AST 詳細・その他は近似と明記）。ベンダーコード混入・除外の空振り・偽の成功終了コードなど、 「黙って間違った数値を出す」失敗を構造的に封じる。 「リポジトリレビューして」「コード品質を評価して」「このプロジェクトを診断して」「包括レビュー」「repo-review」 「アーキテクチャ評価して」等で発火。/repo-review でも起動。

`analysis-agent`/`task-agent`/`review-agent`: use for recurrence guards on known defects, incidents, or escaped failures; skip speculative risk without a prior failure mechanism.

Resume an interrupted AgenTeam run with verify-first strategy.

Resume a paused experiment. Checkout the experiment branch, read results history, continue iterating.

Resume a paused experiment. Checkout the experiment branch, read results history, continue iterating.

`task-agent`/`review-agent`: use when protected state, restore objectives, dependency order, or recovery evidence changes; skip backup-job-only work with no recovery decision.

Test Retry Config - Auto-activating skill for Test Automation. Triggers on: test retry config, test retry config Part of the Test Automation skill category. Use when writing or running tests. Trigger with phrases like "test retry config", "test config", "test".

Autonomous error recovery — detect failures, diagnose root cause, apply fixes, and resume without stopping

セッション再開時に最新5件のhandoffを読み込み文脈を復元するスキル。「おはよう」「こんにちは」「こんばんは」「再開」「restart」または /resume-session を呼んだ時にトリガーする。new-session の対（読込側）。

Provides structured reverse engineering techniques for analyzing compiled, obfuscated, packed, or virtualized targets including binaries, APKs, WASM, firmware, and custom VMs using static and dynamic analysis workflows.

Refactors test files to improve behavioral coverage, clarity, structure, assertions, fixture setup, and mocking strategy, removing implementation-detail or low-value tests.

Verifies that tests for already-implemented behavior are meaningful by temporarily breaking the production code and confirming the test fails for the expected reason.

Use for bugs, unexpected behavior, regressions, or failing tests you did not write.

Restructure code while preserving behavior: confirm tests are green, refactor in small steps, keep tests green, review, and commit with a gated workflow.

Executes structured recovery from a ransomware incident following NIST and CISA frameworks, including environment isolation, forensic evidence preservation, clean infrastructure rebuild, prioritized system restoration from verified backups, credential reset, and validation against re-infection.

Rehearse

Provides a structured triage process for debugging test failures, build errors, runtime bugs, and production incidents, including steps to reproduce, localize, fix, and guard against recurrence.

Provides a structured methodology for authorized Android and iOS reverse engineering, covering static analysis, dynamic instrumentation with Frida and Objection, SSL pinning bypass, root/jailbreak detection evasion, and cryptographic key extraction.

Diagnose bugs, failing tests, or unexpected behavior by reproducing, isolating, hypothesizing with evidence, and confirming fixes before making changes.

Provides comprehensive testing patterns for Perl applications using Test2::V0, Test::More, prove runner, mocking, and coverage analysis with Devel::Cover.

Diagnose and fix a bug through a disciplined reproduce, isolate, diagnose, fix, verify loop driven by evidence and one hypothesis at a time — not guesswork.

Run a reproduce → isolate → verify debugging workflow for concrete bugs, regressions, flaky failures, and environment-specific behavior. Use when the user already has a failing command, test, request, UI flow, or narrowed symptom and needs root-cause diagnosis or fix verification rather than raw log-line selection, broad test-policy design, PR review, or generic performance tuning.

Systematic debugging — reproduce, read the error, isolate, hypothesize, fix, verify, document. Use when tracking down a bug, unexpected behavior, or test failure — including phrases like "this doesn't work", "why is this failing", or "help me debug".

Autonomously runs iterative experiment loops to optimize code against a measurable metric. Use when the user wants to improve execution time, memory usage, test pass rate, or any numeric performance goal across repeated experiments — NOT for one-shot bug fixes or simple code review.

Gera um plano de reconstrução bottom-up a partir das specs do Reversa e executa cada tarefa sob demanda, uma por vez, preservando tokens. Use quando quiser reimplementar o software do zero a partir das especificações geradas. Ativação: /reversa-reconstructor

Run tests and systematically fix all failing tests using smart error grouping. Use when user asks to fix failing tests, mentions test failures, runs test suite and failures occur, or requests to make tests pass.

Authorized reverse engineering of custom binary protocols, Protobuf/gRPC, WebSocket frames, and PCAP-driven protocol recovery with structured workflow and tooling.

使用Test2::V0、Test::More、prove runner、模拟、Devel::Cover覆盖率和TDD方法的Perl测试模式。

Perl testing patterns using Test2::V0, Test::More, prove runner, mocking, coverage with Devel::Cover, and TDD methodology.

通用多轮迭代改进：对任意研究制品反复调用 /review → 解析反馈 → 修复 → 更新 wiki，直到达标

Test React components with RTL and Jest/Vitest. Use when writing React component tests with React Testing Library, Jest, or Vitest.

Provides expert guidance for systematic backtesting of trading strategies, covering methodology, stress testing, bias prevention, and result interpretation.