reviewing-code — community reviewing-code, dotfiles2.0, community, ide skills, Claude Code, Cursor, Windsurf

v1.0.0
GitHub

About this Skill

Perfect for Code Analysis Agents specializing in automated code review and quality assurance. The new dotfiles repo managed with yadm

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

Agent Capability Analysis

The reviewing-code skill by tdhopper is an open-source community AI agent skill for Claude Code and other IDE workflows, helping agents execute tasks with better context, repeatability, and domain-specific guidance.

Ideal Agent Persona

Perfect for Code Analysis Agents specializing in automated code review and quality assurance.

Core Value

Enables comprehensive code review focusing on substantive issues including bugs, missing tests, complexity, performance problems, and duplication while bypassing linting concerns. Integrates with external review systems like Codex and Gemini for enhanced analysis capabilities when available.

↓ Capabilities Granted for reviewing-code

Automating code quality assessments in CI/CD pipelines
Identifying performance bottlenecks and complexity issues
Detecting code duplication and incomplete implementations
Running external reviews through Codex/Gemini integration

! Prerequisites & Limits

  • Requires yadm-managed dotfiles repository structure
  • External reviewers (Codex/Gemini) must be locally available
  • Focuses exclusively on substantive issues, skipping formatting/style concerns
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

reviewing-code

Install reviewing-code, an AI agent skill for AI agent workflows and automation. Works with Claude Code, Cursor, and Windsurf with one-command setup.

SKILL.md
Readonly

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.

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 Analysis Agents specializing in automated code review and quality assurance. The new dotfiles repo managed with yadm

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 quality assessments in CI/CD pipelines, Identifying performance bottlenecks and complexity issues, Detecting code duplication and incomplete implementations, Running external reviews through Codex/Gemini integration.

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 yadm-managed dotfiles repository structure. External reviewers (Codex/Gemini) must be locally available. Focuses exclusively on substantive issues, skipping formatting/style concerns.

↓ 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.

Related Skills

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

View All

widget-generator

Logo of f
f

f.k.a. Awesome ChatGPT Prompts. Share, discover, and collect prompts from the community. Free and open source — self-host for your organization with complete privacy.

★ 149.6k
⑂ 0
AI

flags

Logo of vercel
vercel

flags is a Next.js feature management skill that enables developers to efficiently add or modify framework feature flags, streamlining React application development.

★ 138.4k
⑂ 0
Browser

zustand

Logo of lobehub
lobehub

The ultimate space for work and life — to find, build, and collaborate with agent teammates that grow with you. We are taking agent harness to the next level — enabling multi-agent collaboration, effortless agent team design, and introducing agents as the unit of work interaction.

★ 72.8k
⑂ 0
AI

data-fetching

Logo of lobehub
lobehub

The ultimate space for work and life — to find, build, and collaborate with agent teammates that grow with you. We are taking agent harness to the next level — enabling multi-agent collaboration, effortless agent team design, and introducing agents as the unit of work interaction.

★ 72.8k
⑂ 0
AI