Skip to content
TrustedSkillsbeta
Back to all skills

Peer Review

Checked
jackspace·vlatest·backend·MIT

Critically assesses code submissions from peers, identifying potential bugs, style issues, and areas for improvement.

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 jackspace/claudeskillz --skill peer-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

jackspace

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 jackspace/claudeskillz at aef4e299d1.

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

Commit
aef4e299d1
Manifest
skills/scientific-thinking-peer-review/SKILL.md
Scanned
2 files, 397 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

The jackspace-peer-review skill facilitates automated code review. It analyzes provided code snippets, identifies potential issues like bugs or style violations, and generates feedback in a structured format. This allows for faster iteration cycles and improved code quality through AI assistance.

When to use it

  • Reviewing pull requests before merging into a main branch.
  • Identifying common coding errors in new feature development.
  • Ensuring adherence to specific style guides or best practices within a project.
  • Providing feedback on student code submissions for educational purposes.

Key capabilities

  • Automated code analysis
  • Bug detection
  • Style violation identification
  • Structured feedback generation

Example prompts

  • "Please review this Python function and provide feedback: [code snippet]"
  • "Analyze the following JavaScript code for potential errors and suggest improvements: [code snippet]"
  • "Can you check this C++ code against the Google style guide? [code snippet]"

Tips & gotchas

The skill's effectiveness depends on the clarity and completeness of the provided code. Ensure that any necessary context or dependencies are included for accurate analysis.