Skip to content
TrustedSkillsbeta
Back to all skills

Code Review Playbook

Listed
yonatangross·vlatest·backend·MIT

Automates thorough backend code reviews using a structured playbook, identifying potential bugs, security flaws, and style inconsistencies.

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 yonatangross/orchestkit --skill code-review-playbook -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

yonatangross

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.

  • No undeclared network calls: failed

    Contacts 1 host that is neither well-known infrastructure nor declared in the skill's frontmatter: cli.github.com.

    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.

    Hosts contacted

    cli.github.comundeclared

    What it found

    • plugins/ork/skills/code-review-playbook/scripts/fetch-pr-data.sh:26contacts cli.github.com
      echo "Error: GitHub CLI (gh) not found. Install from https://cli.github.com/" >&2

  • 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 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 yonatangross/skillforge-claude-plugin at 8b46ac9a60.

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

Commit
8b46ac9a60
Manifest
src/skills/code-review-playbook/SKILL.md
Scanned
23 files, 3,065 lines
Copies in repo
2 — 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 provides a structured approach to code reviews, guiding the AI agent through key areas like correctness, design, and maintainability. It helps ensure code quality by prompting for specific considerations and suggesting improvements based on established best practices. The playbook aims to improve developer productivity and reduce technical debt.

When to use it

  • Reviewing pull requests before merging into a main branch.
  • Evaluating code contributions from external developers or contractors.
  • Performing a focused review of a specific feature or bug fix.
  • Ensuring adherence to coding standards within a project.

Key capabilities

  • Structured review process
  • Focus on correctness, design, and maintainability
  • Suggestion of improvements based on best practices
  • Guidance through key areas of code quality

Example prompts

  • "Review this pull request: [link to pull request]"
  • "Perform a code review focusing on potential security vulnerabilities in this file: [file path]"
  • "Can you check the design and maintainability of this function? [code snippet]"

Tips & gotchas

The skill is most effective when provided with clear context, such as a link to a pull request or specific code snippets. It assumes a basic understanding of software development principles.