Skip to content
TrustedSkillsbeta
Back to all skills

Pr Quality Checklist

Checked
bobmatnyc·vlatest·productivity·MIT

This skill generates a detailed PR quality checklist to ensure consistent and effective pull requests, improving code review processes.

Install on your platform

Showing Claude Code. One command installs this skill into any of the agents below.

  1. 1

    Run this in your project

    terminal
    $ npx skills add bobmatnyc/claude-mpm-skills --skill pr-quality-checklist -a claude-code
  2. Uses the open-source skills CLI and needs Node.js. Add -g to install it for your user instead of this project.

What we know about this skill

Publisher

bobmatnyc

Taken from the source listing. We haven't verified who controls this account.

Install target

Live repository

Not pinned. Installing fetches whatever the repository holds at the time you run the command.

No human has reviewed this code. The checks below are a static scan of the files at one commit — nobody has run this skill or judged whether it works. A skill runs with whatever access you give your agent, so read the source before you install it.

Automated safety checks

scanned

This skill passed all 6 checks. We read its files at one commit and looked for the things that make a skill dangerous to run — not for whether it works.

  • Declares what it does: passed

    SKILL.md parses and declares a name and a description.

    SKILL.md exists, its frontmatter parses, and it declares a name and a description.

  • No undeclared network calls: passed

    Makes no network calls.

    Every host the skill dials — from its scripts, its config endpoints or the commands it tells the agent to run — is either well-known package and API infrastructure or declared in its own frontmatter. Links in documentation are not counted.

  • No obfuscated payloads: passed

    No encoded or obfuscated payloads.

    No base64, hex or compressed blob is decoded and then executed, and no encoded shell commands.

  • No credential access: passed

    Reads no keys, tokens, keychains or credential files.

    Neither the code nor the SKILL.md instructions read SSH keys, cloud credentials, keychains, token stores, browser cookie databases or dotfiles that hold secrets.

  • No pipe-to-shell installers: passed

    No pipe-to-shell or download-and-run installers.

    No `curl … | sh` pattern, in the code or in the instructions, that runs code fetched at run time.

  • Pinned to a commit: passed

    Scanned bobmatnyc/claude-mpm-skills at 718070a7d6.

    The exact upstream commit SHA that was scanned is recorded, so the result refers to specific bytes.

Scanned
2 files, 508 lines
This is a static scan, not a review. It reads the skill's files; it does not run them, and it cannot tell you whether the skill is any good or whether the code does what its description says. A skill runs with whatever access you give your agent.
What each check looks for →

About this skill

What it does

This skill provides a structured checklist for reviewing pull requests to ensure code quality and adherence to project standards. It helps agents systematically evaluate submissions before they are merged into the main branch.

When to use it

  • Before merging a pull request to catch potential bugs or style inconsistencies.
  • During code reviews to verify that all required documentation updates are included.
  • When onboarding new contributors to enforce consistent coding practices across the team.
  • To automate repetitive quality checks in large repositories with many frequent submissions.

Key capabilities

  • Generates a comprehensive list of items to check for each pull request.
  • Validates code style and formatting against project guidelines.
  • Ensures test coverage meets minimum requirements before approval.
  • Checks for proper commit messages and changelog entries.

Example prompts

  • "Run the PR quality checklist on this pull request and highlight any missing items."
  • "Use the quality checklist to review my latest code changes before I submit them."
  • "Generate a detailed report of what needs to be fixed based on the PR quality checklist."

Tips & gotchas

Ensure your project has clear guidelines for code style, testing, and documentation so the checklist can effectively validate compliance. Customize the checklist items if your team has specific requirements not covered by default checks.