pr-radar-debug

Debug PRRadar issues by analyzing repository configurations and CLI outputs.

1|Updated Mar 21, 2026

Search Tags:#debugging #cli #config #pipeline #reproduction #pr-radar

Ready to run

npx skills add https://github.com/gestrich/AIDevTools --skill pr-radar-debug

💬 Prompt for ChatGPT / Claude Chat▼

Please help me install this Agent Skill.
Skill: pr-radar-debug
Source: https://github.com/gestrich/AIDevTools/tree/main/.agents/skills/pr-radar-debug
Command: npx skills add https://github.com/gestrich/AIDevTools --skill pr-radar-debug

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Debugging PRRadar issues by providing clear context about configured repositories, including where rules, output, and settings live, and how to reproduce issues from the Mac app using CLI commands.

Core Features & Use Cases

Contextual guidance for PRRadar debugging across Mac app and CLI, covering pipelines, rule evaluation results, and output artifacts.
Step-by-step repro workflows for common bugs using repository configurations and PRRadar settings.
Quick references to Bill-shared screenshots, code reviews, and rule directories to accelerate issue reproduction.

Quick Start

Describe the issue you want to debug and run the PRRadar CLI commands against your configured repositories to reproduce the behavior.

Frequently Asked Questions about pr-radar-debug

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

FAQPage Schema

How do I debug PRRadar pipeline rules and settings from the CLI?▼

Debug PRRadar by analyzing repository configurations and output artifacts to reproduce issues from the Mac app. Use CLI commands against configured repositories to inspect pipeline outputs, rule evaluation results, and settings directories to identify root causes.

What is the best way to reproduce a PRRadar issue from the Mac app using CLI commands?▼

Reproduce PRRadar issues by running CLI commands against your configured repositories to mirror Mac app behavior. Analyze local rule directories, pipeline outputs, and repository settings to replicate the exact environment and trigger the bug.

Can I use local repository configurations to diagnose PRRadar rule evaluation failures?▼

Yes, you can diagnose PRRadar rule evaluation failures using local repository configurations. Analyze the configured rules, pipeline output artifacts, and settings directories to trace how rules are evaluated and identify where the evaluation logic breaks.

Why does my PRRadar pipeline output differ between the Mac app and CLI?▼

PRRadar pipeline output discrepancies between the Mac app and CLI often stem from mismatched repository configurations or settings. Analyze local rule directories and pipeline outputs to compare environments and locate the configuration differences causing the issue.

Are there limitations to debugging PRRadar issues with CLI commands?▼

Debugging PRRadar with CLI commands is limited to safe, non-destructive guidance using local configurations and publicly available commands. It focuses on analyzing pipeline outputs and settings but does not modify or destructively alter your repository configurations.

Do I need specific repository settings to debug PRRadar rules and output artifacts?▼

You need access to your configured PRRadar repository settings, rule directories, and output artifacts to debug effectively. These local configurations provide the necessary context to reproduce issues, evaluate rules, and verify fixes across your repos.