Skip to content
TrustedSkillsbeta
Back to all skills

Github Code Review

Checked
ruvnet·vlatest·backend·MIT

Helps with GitHub, code review as part of developing backend services and APIs workflows.

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 ruvnet/ruflo --skill github-code-review --full-depth -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

ruvnet

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 ruvnet/claude-flow at 49da6ecc44.

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

Commit
49da6ecc44
Manifest
.agents/skills/github-code-review/SKILL.md
Scanned
3 files, 3,099 lines
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

The github-code-review skill enables AI agents to analyze pull requests on GitHub, generating detailed feedback on code quality, security vulnerabilities, and adherence to project standards. It automates the review process by scanning diffs against defined rulesets to ensure consistency before merging.

When to use it

  • Automating initial triage of incoming pull requests in large repositories.
  • Enforcing specific coding style guides or security policies across a team.
  • Reducing manual review time for routine changes while highlighting complex logic errors.
  • Providing consistent, objective feedback on code maintainability and documentation.

Key capabilities

  • Analyzes pull request diffs to identify potential bugs and security issues.
  • Generates structured comments directly within the GitHub interface.
  • Validates code against configurable linting rules and best practices.
  • Summarizes changes and suggests improvements for complex logic blocks.

Example prompts

  • "Review this pull request and check for any obvious security vulnerabilities or race conditions."
  • "Analyze the diff and provide feedback on whether the new functions follow our existing naming conventions."
  • "Summarize the changes in this PR and highlight any areas where documentation is missing."

Tips & gotchas

Ensure your GitHub repository has a .github/ configuration folder with the necessary rulesets or linting definitions for the AI to validate against. The skill works best when paired with clear context about the project's specific architecture and coding standards.