Skip to content
TrustedSkillsbeta
Back to all skills

Code Review Router

Checked
win4r·vlatest·backend

Automatically routes code review requests to appropriate team members based on file content and expertise.

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 win4r/agent-skills-code-review-router --skill code-review-router -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

win4r

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 win4r/agent-skills-code-review-router at dd3749640d.

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

Commit
dd3749640d
Manifest
SKILL.md
Scanned
2 files, 555 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 code-review-router skill intelligently routes code review requests to the appropriate reviewer based on factors like expertise, availability, and project context. It can analyze commit messages, file types, and assigned owners to ensure reviews are handled efficiently. This reduces bottlenecks in the development process and improves overall code quality.

When to use it

  • Large teams: Distribute code review workload evenly among team members with varying skillsets.
  • Specialized projects: Route specific files (e.g., database migrations, frontend components) to reviewers with relevant experience.
  • On-call rotations: Automatically assign reviews based on current on-call schedules.
  • Automated workflows: Integrate code review routing into CI/CD pipelines for seamless integration.

Key capabilities

  • Commit message analysis
  • File type recognition
  • Assignee identification
  • Availability checking (implied)
  • Project context awareness

Example prompts

  • "Route this pull request to the expert in database migrations."
  • "Find an available reviewer for changes to the frontend codebase."
  • “Who is on call for reviewing Python code?”

Tips & gotchas

The skill’s effectiveness depends on accurate project metadata and team member profiles. Ensure these are well-maintained for optimal routing accuracy.