Skip to content
TrustedSkillsbeta
Back to all skills

Github Code Review

Checked
proffesor-for-testing·vlatest·backend·MIT

Helps with testing, GitHub, code review as part of testing, debugging, and quality assurance 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 proffesor-for-testing/agentic-qe --skill github-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

proffesor-for-testing

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 proffesor-for-testing/agentic-qe at 124d8c735e.

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

Commit
124d8c735e
Manifest
.claude/skills/github-code-review/SKILL.md
Scanned
1 file, 1,028 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

The github-code-review skill empowers AI agents to act as senior software engineers, performing deep code analysis and generating comprehensive review comments directly within GitHub. It automates the detection of logical errors, security vulnerabilities, and style inconsistencies to ensure high-quality code integration.

When to use it

  • Automating initial pull request reviews for large teams to reduce manual overhead.
  • Identifying potential security flaws or logic bugs before they reach production environments.
  • Enforcing consistent coding standards and best practices across a distributed development team.
  • Providing immediate, actionable feedback on complex code changes during the merge window.

Key capabilities

  • Performs deep static analysis of submitted code changes.
  • Generates detailed comments highlighting specific issues like bugs or style violations.
  • Acts as an automated gatekeeper to maintain code quality standards.
  • Integrates seamlessly with GitHub workflows for real-time feedback.

Example prompts

  • "Review this pull request and identify any potential security vulnerabilities or logic errors."
  • "Analyze the code changes for adherence to our team's coding style guide and suggest improvements."
  • "Act as a senior engineer and provide a comprehensive review of this feature branch before merging."

Tips & gotchas

Ensure your AI agent has read access to the specific GitHub repositories it is reviewing to avoid permission errors. While the skill excels at identifying common patterns, complex architectural decisions may still require human oversight for final approval.