Skip to content
TrustedSkillsbeta
Back to all skills

Comprehensive Review Pr Enhance

Listed
sickn33·vlatest·backend·MIT

Analyzes pull requests, identifies potential issues, suggests improvements, and ensures code quality for enhanced collaboration.

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 sickn33/agentic-awesome-skills --skill comprehensive-review-pr-enhance -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

sickn33

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 failed 1 of 6 checks. A failure is not proof of bad intent; it means something in the code needs a human to look at it before you run it.

  • Declares what it does: failed

    No SKILL.md was found in the skill's directory.

    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 sickn33/antigravity-awesome-skills at 5a4cdd9df8.

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

Scanned
0 files
Copies in repo
3 — all of them scanned
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 analyzes git diffs to generate reviewer-friendly pull request (PR) descriptions and checklists. It categorizes changes into areas like source, test, config, docs, and build, providing a structured summary of modifications. The skill also flags potential risks and suggests splitting large PRs for better manageability.

When to use it

  • You need to transform a git diff into a well-structured pull request description.
  • The diff is substantial, requiring explicit structure instead of a brief summary for reviewers.
  • You want a PR summary including change categories, risk assessments, testing notes, and a review checklist.
  • When a pull request exceeds 20 files or 1000 lines, prompting the need to split it into smaller features.

Key capabilities

  • Categorizes changes within a git diff (source, test, config, docs, build, styles).
  • Generates a PR description template with sections for Summary, Changes, Why, Testing, and Risks & Rollback.
  • Creates a review checklist based on the file categories present in the diff.
  • Flags breaking changes, security-sensitive files, or large diffs.
  • Suggests splitting large pull requests by feature area using git checkout and git cherry-pick.

Example prompts

  • "Analyze this git diff and generate a PR description."
  • "Create a review checklist for these changes."
  • “This is the output of git diff <base>...HEAD --stat, please create a pull request summary.”

Tips & gotchas

  • The skill requires the input of a git diff generated using git diff <base>...HEAD --stat.
  • Do not treat the output as a replacement for environment-specific validation, testing, or expert review.
  • If any required information (permissions, safety boundaries, success criteria) is missing, stop and ask for clarification.