review — community review, nixfiles, community, ide skills

v1.0.0
GitHub

About this Skill

Perfect for Code Review Agents needing comprehensive content analysis for NixOS setup and pre-commit self-review. Pre-commit self-review. Use this to catch bugs, security issues, debug artifacts, and style problems in your changes before committing.

TheCactusBlue TheCactusBlue
[0]
[0]
Updated: 3/5/2026

Killer-Skills Review

Decision support comes first. Repository text comes second.

Reference-Only Page Review Score: 7/11

This page remains useful for operators, but Killer-Skills treats it as reference material instead of a primary organic landing page.

Original recommendation layer Concrete use-case guidance Explicit limitations and caution Locale and body language aligned
Review Score
7/11
Quality Score
18
Canonical Locale
en
Detected Body Locale
en

Perfect for Code Review Agents needing comprehensive content analysis for NixOS setup and pre-commit self-review. Pre-commit self-review. Use this to catch bugs, security issues, debug artifacts, and style problems in your changes before committing.

Core Value

Empowers agents to analyze diffs for bugs, security problems, leftover debug code, and style inconsistencies using Git commands like `git diff --staged` and `git diff`, providing findings for user decision-making without auto-fixing, leveraging protocols like Git and file formats like diffs.

Ideal Agent Persona

Perfect for Code Review Agents needing comprehensive content analysis for NixOS setup and pre-commit self-review.

↓ Capabilities Granted for review

Analyzing staged changes for issues before committing
Debugging unstaged changes for security problems and style inconsistencies
Reviewing project code for leftover debug code and bugs

! Prerequisites & Limits

  • Requires Git installation and configuration
  • Limited to analyzing changesets, does not auto-fix issues
  • Dependent on user decision-making for issue resolution

Why this page is reference-only

  • - The underlying skill quality score is below the review floor.

Source Boundary

The section below is imported from the upstream repository and should be treated as secondary evidence. Use the Killer-Skills review above as the primary layer for fit, risk, and installation decisions.

After The Review

Decide The Next Action Before You Keep Reading Repository Material

Killer-Skills should not stop at opening repository instructions. It should help you decide whether to install this skill, when to cross-check against trusted collections, and when to move into workflow rollout.

Install Path

Start With Installation And Validation

If this skill is worth continuing with, the next step is to confirm the install command, CLI write path, and environment validation.
Trusted Recheck

Cross-Check Against Trusted Picks

If you are still comparing multiple skills or vendors, go back to the trusted collection before amplifying repository noise.
Workflow

Move To Workflow Collections For Team Rollout

When the goal shifts from a single skill to team handoff, approvals, and repeatable execution, move into workflow collections.
Labs Demo

Browser Sandbox Environment

⚡️ Ready to unleash?

Experience this Agent in a zero-setup browser environment powered by WebContainers. No installation required.

Boot Container Sandbox

FAQ & Installation Steps

These questions and steps mirror the structured data on this page for better search understanding.

? Frequently Asked Questions

What is review?

Perfect for Code Review Agents needing comprehensive content analysis for NixOS setup and pre-commit self-review. Pre-commit self-review. Use this to catch bugs, security issues, debug artifacts, and style problems in your changes before committing.

How do I install review?

Run the command: npx killer-skills add TheCactusBlue/nixfiles/review. It works with Cursor, Windsurf, VS Code, Claude Code, and 19+ other IDEs.

What are the use cases for review?

Key use cases include: Analyzing staged changes for issues before committing, Debugging unstaged changes for security problems and style inconsistencies, Reviewing project code for leftover debug code and bugs.

Which IDEs are compatible with review?

This skill is compatible with Cursor, Windsurf, VS Code, Trae, Claude Code, OpenClaw, Aider, Codex, OpenCode, Goose, Cline, Roo Code, Kiro, Augment Code, Continue, GitHub Copilot, Sourcegraph Cody, and Amazon Q Developer. Use the Killer-Skills CLI for universal one-command installation.

Are there any limitations for review?

Requires Git installation and configuration. Limited to analyzing changesets, does not auto-fix issues. Dependent on user decision-making for issue resolution.

↓ How To Install

  1. 1. Open your terminal

    Open the terminal or command line in your project directory.

  2. 2. Run the install command

    Run: npx killer-skills add TheCactusBlue/nixfiles/review. The CLI will automatically detect your IDE or AI agent and configure the skill.

  3. 3. Start using the skill

    The skill is now active. Your AI agent can use review immediately in the current project.

! Reference-Only Mode

This page remains useful for installation and reference, but Killer-Skills no longer treats it as a primary indexable landing page. Read the review above before relying on the upstream repository instructions.

Upstream Repository Material

The section below is imported from the upstream repository and should be treated as secondary evidence. Use the Killer-Skills review above as the primary layer for fit, risk, and installation decisions.

Upstream Source

review

Install review, an AI agent skill for AI agent workflows and automation. Review the use cases, limitations, and setup path before rollout.

SKILL.md
Readonly
Upstream Repository Material
The section below is imported from the upstream repository and should be treated as secondary evidence. Use the Killer-Skills review above as the primary layer for fit, risk, and installation decisions.
Supporting Evidence

Pre-Commit Self-Review

Overview

Review the current changeset for issues before committing. Analyzes the diff for bugs, security problems, leftover debug code, and style inconsistencies. Presents findings for the user to decide on — does not auto-fix.

The Process

Gather the changeset:

  • Run git diff --staged to get staged changes
  • If nothing is staged, fall back to git diff for unstaged changes
  • If both are empty, inform the user there's nothing to review

Check project conventions:

  • If CLAUDE.md exists at the project root, read it for project-specific rules
  • Note any conventions around naming, error handling, imports, or formatting
  • Use these as additional review criteria alongside the defaults

Analyze changes for issues:

  • Bugs and logic errors - Off-by-one, null/undefined access, wrong comparisons, missing edge cases, race conditions
  • Leftover debug code - console.log, debugger, print() statements, TODO/FIXME/HACK comments added in this diff
  • Security issues - Hardcoded secrets, SQL injection, XSS, unsanitized input, overly permissive permissions
  • Missing error handling - Unhandled promise rejections, unchecked return values, bare except/catch blocks
  • Style inconsistencies - Naming convention mismatches, inconsistent patterns compared to surrounding code

Present findings:

  • Group issues by severity:
    • Blocking - Bugs, security issues, or errors that must be fixed before committing
    • Warning - Likely problems worth addressing but not strictly required
    • Nitpick - Style or preference issues, take-or-leave
  • For blocking issues, suggest a specific fix with code
  • For warnings and nitpicks, describe the issue and location
  • If the changeset is clean, confirm with a brief summary of what was reviewed

Key Principles

  • Diff-focused - Only review what changed, not the entire file
  • Advisory, not automatic - Present findings for the user to act on
  • Convention-aware - Respect project-specific rules from CLAUDE.md
  • Severity-driven - Clearly separate must-fix from nice-to-have
  • Concise - Don't repeat the code back; reference file and line, describe the issue, suggest the fix

Related Skills

Looking for an alternative to review or another community skill for your workflow? Explore these related open-source skills.

View All

openclaw-release-maintainer

Logo of openclaw
openclaw

Your own personal AI assistant. Any OS. Any Platform. The lobster way. 🦞

★ 333.8k
⑂ 0
AI

widget-generator

Logo of f
f

Generate customizable widget plugins for the prompts.chat feed system

★ 149.6k
⑂ 0
AI

flags

Logo of vercel
vercel

The React Framework

★ 138.4k
⑂ 0
Browser

pr-review

Logo of pytorch
pytorch

Tensors and Dynamic neural networks in Python with strong GPU acceleration

★ 98.6k
⑂ 0
Developer