verify-pr vs frb-debugging
verify-pr and frb-debugging are both developer tools skills. frb-debugging scores higher (84 vs 68 out of 100). frb-debugging has more GitHub stars (5.5k), and verify-pr was updated more recently (3 days ago). The table compares them side by side.
| verify-pr | frb-debugging | |
|---|---|---|
| Score | 68 / 100 | 84 / 100 |
| What it does | Verifies an autoconsent pull request by running local CI checks, reviewing rule quality, and inspecting Jenkins E2E results. Use when reviewing, verifying, or approving a PR, when checking if a PR is ready to merge, or when the user asks to validate PR changes. | Use when generated code looks wrong, code generation fails, or you need to understand FRB internals |
| Publisher | Community: duckduckgo | Community: fzyzcjy |
| Grades | Maintenance A, Licence A, Quality B | Maintenance A, Licence A, Quality A |
| npm downloads a week | Not on npm | Not on npm |
| Runs | Skill | Skill |
| Works with | Claude Code, Claude apps | Claude Code, Claude apps |
| GitHub stars | 131 | 5,460 |
| Last commit | 20 Oct 2026 | 19 Oct 2026 |
| Licence | MPL-2.0 | MIT |
| Listed since | 19 Oct 2026 | 20 Oct 2026 |
| Install verify-pr | Install frb-debugging |
Questions
Is verify-pr or frb-debugging more popular?
frb-debugging has more GitHub stars: 5,460.
Can I use verify-pr and frb-debugging together?
Yes. AI assistants can load several skills at once. Install both and the assistant picks the right one for each task.