Skip to content
TrustedSkillsbeta
Back to all skills

Security Pr Checklist Skill

Checked
patricio0312rev·vlatest·security·MIT

Generates a comprehensive pull request checklist to ensure secure code changes based on best practices.

Repository

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 patricio0312rev/skills --skill security-pr-checklist-skill -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

patricio0312rev

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 patricio0312rev/skills at 79ea6af485.

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

Commit
79ea6af485
Manifest
security/security-pr-checklist-skill/SKILL.md
Scanned
1 file, 61 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 security pull requests, helping teams identify common vulnerabilities before code merges. It standardizes the review process to ensure consistent application of security best practices across your repository.

When to use it

  • Before merging any pull request that introduces new authentication or authorization logic.
  • During code reviews for dependencies where third-party libraries are added to the project.
  • When auditing recent changes to sensitive configuration files or environment variables.
  • As a mandatory step in CI/CD pipelines before deploying production builds.

Key capabilities

  • Generates a comprehensive list of security questions tailored to the specific PR context.
  • Highlights potential issues related to input validation, output encoding, and secure defaults.
  • Facilitates communication between developers and security engineers during the review phase.

Example prompts

  • "Run the security PR checklist on this pull request to identify any authentication bypass risks."
  • "Use the security checklist to review the changes made to our database connection strings in this commit."
  • "Generate a security review list for the new user registration feature being added in this PR."

Tips & gotchas

Ensure your team has access to the specific repository context or provide relevant file paths when invoking the skill, as it relies on understanding the codebase changes. While this checklist covers common patterns, it should complement—not replace—manual expert review for complex security architectures.