npm package discovery and stats viewer.

Discover Tips

  • General search

    [free text search, go nuts!]

  • Package details

    pkg:[package-name]

  • User packages

    @[username]

Sponsor

Optimize Toolset

I’ve always been into building performant and accessible sites, but lately I’ve been taking it extremely seriously. So much so that I’ve been building a tool to help me optimize and monitor the sites that I build to make sure that I’m making an attempt to offer the best experience to those who visit them. If you’re into performant, accessible and SEO friendly sites, you might like it too! You can check it out at Optimize Toolset.

About

Hi, 👋, I’m Ryan Hefner  and I built this site for me, and you! The goal of this site was to provide an easy way for me to check the stats on my npm packages, both for prioritizing issues and updates, and to give me a little kick in the pants to keep up on stuff.

As I was building it, I realized that I was actually using the tool to build the tool, and figured I might as well put this out there and hopefully others will find it to be a fast and useful way to search and browse npm packages as I have.

If you’re interested in other things I’m working on, follow me on Twitter or check out the open source projects I’ve been publishing on GitHub.

I am also working on a Twitter bot for this site to tweet the most popular, newest, random packages from npm. Please follow that account now and it will start sending out packages soon–ish.

Open Software & Tools

This site wouldn’t be possible without the immense generosity and tireless efforts from the people who make contributions to the world and share their work via open source initiatives. Thank you 🙏

© 2026 – Pkg Stats / Ryan Hefner

code-review-unity

v1.0.5

Published

Claude Code skill for reviewing Unity C# code based on Unity's official style guide

Readme

code-review-unity

Claude Code skill for reviewing Unity C# code against Unity's Official C# Style Guide (Unity 6 Edition).

npm version License: MIT

Features

  • Multiple review modes — Review a single file, your local git diff, or a GitHub PR by URL.
  • Follow Unity 6 C# style guide — Naming (PascalCase/camelCase, booleans as questions), SRP, DRY, KISS, comments (why not what), YAGNI, extension methods, and UI Toolkit BEM naming.
  • Unity-specific checks — MonoBehaviour lifecycle (Awake/Start/OnEnable/OnDestroy), coroutine patterns, ScriptableObject usage, and API misuse (e.g. GetComponent in Update, CompareTag, non-alloc physics, pooling).
  • Performance and GC — Flags allocation in hot paths (strings, LINQ, boxing), Update bloat, and common anti-patterns (SendMessage, Invoke, FindObjectOfType in hot paths).
  • Structured output — Critical issues, style violations, and suggestions with file:line refs and concrete fix examples.

Install

npx code-review-unity

Or manually copy .claude/skills/code-review-unity/ to ~/.claude/skills/


Usage

Command Invocation

/code-review-unity Assets/Scripts/PlayerController.cs

Or review git changes:

/code-review-unity

or Just ask claude code:

"Review this Unity script"

Claude will automatically invoke this skill and review your code.


Example Output

## Code Review: PlayerController.cs

### Critical Issues

1. **SRP Violation - God Class** (lines 15-89)
   - Handles input, movement, audio, and inventory
   - Unity Style Guide: "Each MonoBehaviour should have one responsibility"
   - Split into: PlayerInput, PlayerMovement, PlayerAudio, PlayerInventory

2. **GetComponent in Update** (line 34)
   - Caching pattern not used - causes unnecessary overhead every frame
   - Use `[SerializeField]` or cache in `Awake()`

### Style Violations

3. **Poor Variable Naming** (line 23)
   - `int d` should be `int elapsedTimeInDays` - be specific about units
   - `bool dead` should be `bool isDead` - booleans ask questions

Resources


Links


License

MIT