Radar

Add missing coverage and stabilize flaky tests across JS/TS, Python, Go, Rust, and Java.

Updated Mar 18, 2026
One-click install
npx skills add https://github.com/Dinxeshh/agent-skills --skill radar-dinxeshh
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: Radar
Source: https://github.com/Dinxeshh/agent-skills/tree/main/skills/radar
Command: npx skills add https://github.com/Dinxeshh/agent-skills --skill radar-dinxeshh

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes references (resource) components.

What problem does it solve?

Radar stops test regressions and flaky suites from eroding deployment confidence by adding safety-net coverage, fixing nondeterministic failures, and revealing blind spots that slip past feature work.

Core Features & Use Cases

  • Edge-case and regression testing: Identify high-risk paths, add fail-first coverage, and keep tests behavior-focused rather than implementation-specific.
  • Flaky-test stabilization: Diagnose nondeterministic failures, fake timers or async flows as needed, and document the root cause before locking stability.
  • Multi-language toolkit: Work across JS/TS, Python, Go, Rust, and Java with native frameworks, coverage tools, and language-specific references.
  • Workflow guidance: Follow the SCAN → LOCK → PING → VERIFY loop, keep new tests concise (ideally under 50 lines), and route follow-ups to Builder, Judge, Voyager, or Guardian as required.

Quick Start

Prompt Radar to add targeted regression and edge-case tests for the flaky payment workflow.

Frequently Asked Questions about Radar

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I fix flaky tests in my CI pipeline?

Flaky tests are stabilized by diagnosing nondeterministic failures, faking timers or async flows, and documenting root causes before locking behavior. This workflow targets high-risk paths to ensure edge-case regression coverage passes consistently in continuous integration.

How do I add edge-case regression tests across multiple programming languages?

Edge-case regression tests are added across JS/TS, Python, Go, Rust, and Java by matching native local frameworks and coverage tools. New tests target behavior over implementation and stay concise, ideally under fifty lines.

What is the best way to improve test coverage for high-risk code paths?

Improving test coverage involves identifying high-risk paths, adding fail-first safety-net tests, and focusing on behavior rather than implementation specifics. This reveals blind spots that slip past feature work and stops regressions from eroding deployment confidence.

Does this testing approach support both unit and integration tests?

Yes, the approach supports unit, integration, and multi-language test work within JS/TS, Python, Go, Rust, and Java projects. It follows a scan, lock, ping, and verify loop to route follow-ups appropriately and keep test suites stable.

Why does my test suite keep failing nondeterministically during regression checks?

Nondeterministic failures occur due to uncontrolled async flows or timing issues. Stabilizing flaky suites requires diagnosing these failures, faking timers as needed, and documenting the root cause before adding edge-case regression coverage.