Menu
Verify recent PRRadar changes by running the CLI against the test repo
Installer avec Codex ou Claude Copiez ce prompt, collez-le dans Codex, Claude ou un autre assistant, puis laissez-le vérifier la page du skill et l'installer pour vous.
Basé sur la classification professionnelle SOC
Analyzes git diffs and generates structured markdown summaries of code changes. Use when reviewing commits, understanding what changed in a branch, creating change documentation, or reviewing pull requests.
Debugging context for PRRadar with its configured repositories. Covers where rules, output, and settings live, and how to reproduce issues from the Mac app using CLI commands. Use this skill whenever debugging PRRadar behavior, investigating pipeline output, reproducing bug reports from the Mac app, or exploring rule evaluation results. Also use when Bill shares screenshots showing issues in the Mac app, or mentions code reviews, rule directories, output files, or PRRadar configs.
Create a new PRRadar review rule. Use when the user wants to add a code review rule, create a violation check, or set up a new pattern to detect in PRs. Handles choosing the project config, rule directory, evaluation mode (AI/script/regex), file targeting, and grep filtering.
Add an item to the project TODO list with t-shirt size categorization (Small, Medium, Large)
| name | pr-radar-verify-work |
| description | Verify recent PRRadar changes by running the CLI against the test repo |
We have a dedicated test repository at /Users/bill/Developer/personal/PRRadar-TestRepo that exists solely for validating real changes against actual PRs. You have full access to this repo and the GitHub account associated with it.
When this skill is invoked, verify your recent changes by running the PRRadar tools against that test repo. What exactly you run depends on what we're working on or what the user asks for — often this means running the Swift CLI to analyze a PR, but it could be any pipeline phase.
Clean the test repo before running. Previous runs may leave code-reviews/ directories or detached HEAD state that cause "uncommitted changes" errors:
cd /Users/bill/Developer/personal/PRRadar-TestRepo
rm -rf code-reviews
git checkout main
Clean old output data if needed:
rm -rf ~/Desktop/code-reviews
The Swift CLI must be run from the pr-radar-mac/ directory and should use the saved test-repo configuration:
cd /Users/bill/Developer/personal/PRRadar/pr-radar-mac
swift run PRRadarMacCLI diff 1 --config test-repo
swift run PRRadarMacCLI status 1 --config test-repo
swift run PRRadarMacCLI analyze 1 --config test-repo
The --config test-repo flag uses the saved configuration which points to the test repo path and ~/Desktop/code-reviews/ output directory. Without it, the CLI defaults to the ios config which points to the work repo.
To see all saved configurations: swift run PRRadarMacCLI config list
The CLI has built-in help. Use these to explore available commands rather than guessing:
swift run PRRadarMacCLI --help
swift run PRRadarMacCLI diff --help
swift run PRRadarMacCLI config --help
There are other commands beyond these examples — explore with --help as needed.