Skip to content
TrustedSkillsbeta
Back to all skills

Review Changes

Checked
artmann·vlatest·backend·MIT

Artmann's review-changes analyzes code diffs, highlighting potential issues and suggesting improvements for better quality.

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 artmann/review-changes --skill review-changes -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

artmann

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 artmann/review-changes at 72a2625e8b.

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

Commit
72a2625e8b
Manifest
skills/review-changes/SKILL.md
Scanned
7 files, 401 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 Review Changes skill analyzes code changes in a feature branch to identify potential issues and suggest improvements before merging. It can review either a remote pull request (PR) provided via URL or PR number, or the current local branch against the default branch. The skill prioritizes repository-specific coding guidelines when available and incorporates PR descriptions and comments as context for the review.

When to use it

  • Before merging a feature branch into the main codebase.
  • To proactively identify potential issues in code changes.
  • When needing to ensure adherence to specific coding standards or guidelines within a repository.
  • For reviewing pull requests from contributors.
  • To check for adequate test coverage of new or modified business logic.

Key capabilities

  • Remote PR Review: Reviews code changes directly from a provided GitHub Pull Request URL or number.
  • Local Branch Review: Reviews the current branch against the default branch.
  • Repository Guideline Integration: Loads and prioritizes repository-specific coding guidelines (e.g., CLAUDE.md, CODE_GUIDELINES.md).
  • Contextual Analysis: Uses PR descriptions, comments, and surrounding code context during review.
  • Test Coverage Check: Verifies the existence and adequacy of tests for new or modified business logic.
  • Performance Guardrails: Handles large diffs by prioritizing files and summarizing changes to maintain performance.

Example prompts

Tips & gotchas

  • The skill prioritizes repository-specific guidelines over general coding standards.
  • For very large diffs (over 3000 lines), the review may be summarized rather than a line-by-line analysis.
  • Certain file types like lock files, minified CSS/JS, and generated output are skipped to improve performance.