Skip to content
TrustedSkillsbeta
Back to all skills

Requesting Code Review

Checked
davila7·vlatest·backend·MIT

Davila7's davila7-requesting-code-review automatically submits code changes for review, ensuring quality and adherence to standards.

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 davila7/claude-code-templates --skill requesting-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

davila7

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 davila7/claude-code-templates at 79182c51fb.

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

Scanned
2 files, 245 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 requesting-code-review skill enables AI agents to systematically solicit feedback on code changes from human developers or peer systems. It structures the review process by providing context, highlighting specific logic areas, and formatting output for clarity.

When to use it

  • Before merging a pull request to ensure alignment with team standards.
  • When refactoring legacy code to verify that new implementations maintain intended behavior.
  • During security audits to prompt checks on authentication or data handling logic.
  • When integrating third-party libraries to confirm compatibility and error handling.

Key capabilities

  • Generates structured review requests including commit diffs and file paths.
  • Highlights specific lines of code requiring attention based on complexity metrics.
  • Formats feedback into actionable items categorized by severity (critical, warning, suggestion).
  • Supports multiple programming languages and framework-specific conventions.

Example prompts

"Request a code review for the new user authentication module in auth-service.ts, focusing on SQL injection risks." "Ask the team to review the payment processing logic in checkout.js before deploying to production." "Submit a structured code review request for the updated API endpoints, emphasizing rate limiting implementation."

Tips & gotchas

Ensure the AI agent has access to the relevant repository branches and commit history to provide accurate context. Avoid requesting reviews for incomplete or experimental code without explicitly marking it as such to prevent confusion during evaluation.