reviewing-code — community reviewing-code, dotfiles2.0, community, ide skills

v1.0.0
GitHub

About this Skill

Perfect for Code Review Agents needing advanced pull request analysis and debugging capabilities. Review pull requests, branch changes, or code diffs. Triggers on review this PR, review my changes, code review, review branch, or GitHub PR URLs. Focuses on bugs, tests, complexity, and performance -

tdhopper tdhopper
[3]
[3]
Updated: 2/26/2026

Killer-Skills Review

Decision support comes first. Repository text comes second.

Reviewed Landing Page Review Score: 9/11

Killer-Skills keeps this page indexable because it adds recommendation, limitations, and review signals beyond the upstream repository text.

Original recommendation layer Concrete use-case guidance Explicit limitations and caution Quality floor passed for review Locale and body language aligned
Review Score
9/11
Quality Score
57
Canonical Locale
en
Detected Body Locale
en

Perfect for Code Review Agents needing advanced pull request analysis and debugging capabilities. Review pull requests, branch changes, or code diffs. Triggers on review this PR, review my changes, code review, review branch, or GitHub PR URLs. Focuses on bugs, tests, complexity, and performance -

Core Value

Empowers agents to review pull requests, branch changes, or code diffs, focusing on substantive issues like bugs, missing tests, complexity, performance, duplication, and incomplete implementations, utilizing tools like Codex and Gemini for external review.

Ideal Agent Persona

Perfect for Code Review Agents needing advanced pull request analysis and debugging capabilities.

↓ Capabilities Granted for reviewing-code

Automating code reviews for bugs and performance issues
Debugging missing tests and incomplete implementations in code diffs
Generating reports on code complexity and duplication for optimization

! Prerequisites & Limits

  • Requires Codex or Gemini for external review
  • Skips linting concerns like formatting, imports, and naming style
  • Priority given to Codex over Gemini for external review

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 reviewing-code?

Perfect for Code Review Agents needing advanced pull request analysis and debugging capabilities. Review pull requests, branch changes, or code diffs. Triggers on review this PR, review my changes, code review, review branch, or GitHub PR URLs. Focuses on bugs, tests, complexity, and performance -

How do I install reviewing-code?

Run the command: npx killer-skills add tdhopper/dotfiles2.0/reviewing-code. It works with Cursor, Windsurf, VS Code, Claude Code, and 19+ other IDEs.

What are the use cases for reviewing-code?

Key use cases include: Automating code reviews for bugs and performance issues, Debugging missing tests and incomplete implementations in code diffs, Generating reports on code complexity and duplication for optimization.

Which IDEs are compatible with reviewing-code?

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 reviewing-code?

Requires Codex or Gemini for external review. Skips linting concerns like formatting, imports, and naming style. Priority given to Codex over Gemini for external review.

↓ 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 tdhopper/dotfiles2.0/reviewing-code. 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 reviewing-code immediately in the current project.

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

reviewing-code

Install reviewing-code, 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

Code Review

Focus on substantive issues: bugs, missing tests, complexity, performance, duplication, incomplete implementations. Skip linting concerns (formatting, imports, naming style).

External Review (Optional)

Check for external reviewers and use if available. Priority: Codex > Gemini

bash
1command -v codex >/dev/null 2>&1 && echo "Codex available"
2command -v gemini >/dev/null 2>&1 && echo "Gemini available"

If Codex available:

  • Local branch: codex --config model_reasoning_effort="high" review --base BASE_BRANCH
  • Remote PR: gh pr diff NUMBER | codex review --config model_reasoning_effort="high" -

If only Gemini: Pipe diff to gemini with review prompt.

Workflow

  1. Get the diff

    • PR: gh pr view NUMBER --json title,body,files then gh pr diff NUMBER
    • Branch: git diff origin/master...HEAD
    • Uncommitted: git diff

  2. Gather context - Read PR description, commit messages, project CLAUDE.md

  3. Review each file for:

    • Completeness: All code paths handled? Stubs left behind?
    • Tests: Added? Meaningful? Edge cases covered?
    • Complexity: Justified abstractions? Simpler alternatives?
    • Performance: Hot path regressions? Unbatched I/O?
    • Duplication: Similar code already exists? (rg "pattern")

  4. Synthesize external review (if used) with your findings. Consensus issues = high confidence.

Output Format

markdown
1## Summary
2[1-2 sentences]
3
4## External Reviewer
5[If used: Codex or Gemini]
6
7## Key Findings
8
9### Must Address
101. **[Issue]** (`file:line`) [Models]
11   - Details
12   - **Risk**: Why it matters
13
14### Should Consider
152. **[Issue]** (`file:line`)
16   - Details
17
18### Minor Notes
19- Observations
20
21## Tests
22[Coverage and quality assessment]
23
24## Complexity
25[Net impact on codebase complexity]

Numbering: Single sequence across all sections. Model attribution: [Codex + Claude], [Claude], etc.

Scope

In scope: Logic errors, missing error handling, test gaps, performance regressions, unnecessary complexity, duplication, incomplete implementations, project guideline violations.

Out of scope (linters handle): Formatting, import order, naming style, type annotations, docstring format.

Related Skills

Looking for an alternative to reviewing-code 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