pr-radar-verify-work

Validate PRRadar changes by running the CLI against a test repository.

1|Updated Mar 21, 2026
One-click install
npx skills add https://github.com/gestrich/AIDevTools --skill pr-radar-verify-work
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: pr-radar-verify-work
Source: https://github.com/gestrich/AIDevTools/tree/main/.agents/skills/pr-radar-verify-work
Command: npx skills add https://github.com/gestrich/AIDevTools --skill pr-radar-verify-work

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Verifies that recent PRRadar changes work correctly by executing the PRRadar CLI against a dedicated test repository.

Core Features & Use Cases

  • Deterministic validation of new PRRadar changes against the test repo.
  • End-to-end workflow coverage for diff, status, and analyze commands using a saved configuration.
  • Clear guidance for preparing the test repo and cleaning previous outputs to ensure reliable results.

Quick Start

Run the PRRadar CLI against the test repository to validate your changes.

Frequently Asked Questions about pr-radar-verify-work

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

FAQPage Schema
How do I validate CLI changes against a test repository on macOS?

Validate CLI changes by running the PRRadar CLI from the pr-radar-mac directory against a dedicated test repository. This workflow cleans the test repo and removes previous outputs to ensure deterministic validation results across diff, status, and analysis phases.

What is the best way to ensure deterministic validation when testing workflow changes?

Deterministic validation is achieved by cleaning the test repository and removing previous output files before executing CLI commands. This preparation prevents stale artifacts from affecting new test runs and ensures reliable, repeatable validation outcomes.

Do I need a saved configuration to run diff, status, and analysis commands?

Yes, a saved configuration is required to execute the diff, status, and analyze commands end-to-end. The validation workflow uses this saved configuration to run the PRRadar CLI consistently across the dedicated test repository.

Why are my previous test outputs causing inconsistent validation results?

Previous test outputs cause inconsistent results because stale artifacts interfere with new validation runs. Remove previous outputs and clean the test repository before each execution to maintain deterministic workflow validation and prevent false positives.

Does PRRadar validation cover all CLI phases including diff, status, and analyze?

Yes, PRRadar validation covers the diff, status, and analyze phases comprehensively. The workflow executes each CLI command against the test repository using a saved configuration to verify end-to-end functionality of recent changes.

Can I test PRRadar changes without affecting my main repository?

Yes, you can test changes safely using a dedicated test repository. The validation workflow isolates CLI execution to this test environment, cleaning it before each run to prevent any impact on your main repositories or production code.