Skip to content
TrustedSkillsbeta
Back to all skills

Receiving Code Review

Checked
jackiexiao·vlatest·backend

Automates code review feedback generation based on jackiexiao's style and common testing 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 makerjackie/jackie-skills-starter --skill receiving-code-review -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

jackiexiao

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 jackiexiao/jackie-skills-starter at 145241e853.

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

Commit
145241e853
Manifest
skills/receiving-code-review/SKILL.md
Scanned
1 file, 190 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 allows an AI agent to receive and process code review feedback. It can understand comments, suggestions, and questions related to a given codebase or pull request. The agent will then be able to incorporate this feedback into its understanding of the code's quality and areas for improvement.

When to use it

  • When you need an AI assistant to help you understand and act on code review comments.
  • To automatically summarize and prioritize feedback from multiple reviewers.
  • For onboarding new developers by having them process existing code reviews.
  • To identify recurring themes or patterns in code review feedback across a project.

Key capabilities

  • Understands code review comments
  • Processes suggestions for improvement
  • Incorporates feedback into understanding of codebase quality

Example prompts

  • "Here's the code review from pull request #123, can you summarize the key points?"
  • "I received these comments on my function calculate_average, what do they mean and how should I address them?"
  • “Please analyze this code review and suggest next steps for addressing the reviewer’s concerns.”

Tips & gotchas

The quality of the feedback depends heavily on the clarity and detail provided in the original code review. Ensure that the code review comments are well-written and specific to get the best results from this skill.