Skip to content
TrustedSkillsbeta
Back to all skills

Diff Preview

Checked
johnlindquist·vlatest·utilities

This skill generates a visual preview of code changes (diff) for quick understanding and review, saving time & reducing errors.

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 johnlindquist/claude --skill diff-preview -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

johnlindquist

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 johnlindquist/claude at eb37d88225.

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

Scanned
1 file, 207 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

This skill enables AI agents to generate and display visual side-by-side comparisons of code changes. It allows agents to highlight specific modifications, additions, and deletions directly within the chat interface rather than just outputting raw text diffs.

When to use it

  • Reviewing complex refactoring tasks where context is vital for understanding logic shifts.
  • Validating AI-generated patches against existing production codebases to catch unintended side effects.
  • Explaining technical changes to non-technical stakeholders who need a clear visual representation of updates.
  • Iterating on code snippets during collaborative debugging sessions to quickly spot syntax errors or logic flaws.

Key capabilities

  • Renders formatted diff blocks with clear visual indicators for added and removed lines.
  • Provides an intuitive, inline view of file changes without requiring external tools.
  • Supports detailed context display around modified code sections.

Example prompts

  • "Show me a side-by-side diff of the updated authentication module compared to the original version."
  • "Generate a visual comparison of my new feature implementation against the legacy code structure."
  • "Display the changes made in this file as a formatted diff so I can review the specific line modifications."

Tips & gotchas

Ensure your source code is properly formatted before requesting a diff to avoid rendering artifacts. For large files, consider asking the agent to focus on specific functions or sections to keep the preview readable and relevant.