SKILLEMALL.ai
GitHub ↗ RU Sign in

AB pr-description-writer

Write a clear, structured pull request description from a git diff, branch summary, or commit list. Use when asked to write a PR description, draft a pull request, or document code changes. Produces a description with summary, motivation, changes made, testing steps, and reviewer guidance.

mohitagw15856/pm-claude-skills Agent Skills author: mohitagw15856 MIT 4 files body ≈ 1 435 tokens Open the sourcegithub.com↗ analyzed 3 d ago

Write a clear, structured pull request description from a git diff, branch summary, or commit list.

As a process B 72/100 · Nearly there — weak spots: when it triggers, running it twice

GeneratorSoftware developmentWriting and documentstype 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
96/100
safety, quality, tests
Safety 60%
100
Quality 40%
89
Run on models
none yet
Process rating
B
72/100
Nearly there
When it triggers w 12
20
Running it twice w 4
30
Failures and branches w 10
55
the three weakest of ten parameters · all ten
This is a copy of a skill from another catalog; the rating counts the canonical one: pr-description-writer (mohitagw15856/pm-claude-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: 4. Evidence is masked. Grey chips explain why severity was lowered.

    Against the Agent Skills spec

    • note frontmatter-key unknown frontmatter key "deprecated"
    • note frontmatter-key unknown frontmatter key "supersededBy"

    Process rating: all ten parameters 72/100

    • 20When it triggers. No condition that starts the skill
    • 30Running it twice. 3 mutating operations with no state check
    • 55Failures and branches. 1 branches
    • 60Result and completion. Output format stated, no completion criterion
    • 70Inputs and preconditions. Inputs and preconditions are listed
    • 85Steps. 50 steps, 1 vague phrases
    • 100Tools and files. No external tools needed
    • 100Consistency. Name and required fields are in place
    • 100Execution cost. Instruction body is 1435 tokens
    • 100Progress reporting. Reports progress

    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)
    • +1No license
    • +2Single-language instructions
    • +3Description length 290: enough signal without eating the budget
    • +4Structure: 16 headings
    • +3Step-by-step instructions: 50 items
    • +3Output format is stated explicitly
    • +4Has examples (0 code blocks)
    • +4Reference files are cited in the instructions (1 of 2)

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