SKILLEMALL.ai
GitHub ↗ RU Sign in

AB check-pr

Checks a GitHub, GitLab, or Perforce (p4) pull request (or merge request, or shelved changelist) for unresolved review comments, failing status checks, and incomplete PR descriptions. Waits for pending checks to complete, categorizes issues as actionable or informational, and optionally fixes and resolves them. Use when the user wants to check a PR/MR/CL, address review feedback, or prepare a change for submission.

onyx-dot-app/onyx Agent Skills author: onyx-dot-app NOASSERTION 3 files body ≈ 2 144 tokens Open the sourcegithub.com↗ analyzed 6 d ago

Checks a GitHub, GitLab, or Perforce (p4) pull request (or merge request, or shelved changelist) for unresolved review comments, failing status checks, and…

As a process B 75/100 · Nearly there — weak spots: progress reporting

AnalyzerGitHubGitLabSoftware developmentData and analyticstype and topics are labelled automatically from the skill text
Runs in: Claude / Claude Code ChatGPT / Codex Gemini CLI Cursor GitHub Copilot / VS Code Qwen Code Kimi Code CLI Z.ai (GLM) DeepSeek (Deep Code) Mistral Vibe LangChain (deepagents) OpenClaw Goose OpenCode
JSON
Technical rating
A
95/100
safety, quality, tests
Safety 60%
100
Quality 40%
87
Run on models
none yet
Process rating
B
75/100
Nearly there
Progress reporting w 2
0
Failures and branches w 10
55
Steps w 15
60
the three weakest of ten parameters · all ten
This is a copy of a skill from another catalog; the rating counts the canonical one: check-pr (Lord1Egypt/RA-Skills)

How to improve

    For the model run — optional
    • Your own cases (evals/evals.json, 4–6 real requests with expected answers): the full check would then run those instead of a model-drafted suite.
    • A spec.yaml with trigger phrases and assertions — a behaviour contract for CI; `skilltest init` writes a template.

    Guard findings · 0

    ✓ No critical or high findings

    Files scanned: 3. Evidence is masked. Grey chips explain why severity was lowered.

    Against the Agent Skills spec

    ✓ No remarks against the Agent Skills spec

    Process rating: all ten parameters 75/100

    • 0Progress reporting. Says nothing while it works
    • 55Failures and branches. 1 branches
    • 60Steps. 31 steps, 7 vague phrases
    • 60Result and completion. Output format stated, no completion criterion
    • 70When it triggers. States when to use, but not when not to
    • 70Inputs and preconditions. Inputs and preconditions are listed
    • 100Tools and files. Tools declared in frontmatter
    • 100Consistency. Name and required fields are in place
    • 100Execution cost. Instruction body is 2144 tokens
    • 100Running it twice. Mutating operations check current state

    Everything here is measured from the skill text rather than judged by a model, so the numbers are checkable. A parameter weighs more when it is a more common reason for the process to stall.

    Quality signals

    • +5Description has no quoted example phrases that should trigger the skill
    • +4Description does not say when NOT to use the skill (false activations)
    • -5TODO / placeholder text left in the skill
    • +2Single-language instructions
    • +3Description length 418: enough signal without eating the budget
    • +4Structure: 18 headings
    • +3Step-by-step instructions: 31 items
    • +3Output format is stated explicitly
    • +4Has examples (16 code blocks)
    • +4Reference files are cited in the instructions (2 of 2)
    • +1License stated

    Quality base 70; lint remarks subtract, signals add up to 100. Result: 87.