ai-reviewer

Created By
JFinchya year ago
Create AI code reviewer that can be used on github and locally through an MCP server
Overview

what is ai-reviewer?

ai-reviewer is an AI-powered code reviewer designed to assist developers by providing automated code reviews on GitHub and locally through an MCP server.

how to use ai-reviewer?

To use ai-reviewer, integrate it with your GitHub repository or set it up on your local MCP server. Once configured, it will analyze your code and provide feedback on best practices, potential bugs, and improvements.

key features of ai-reviewer?

  • Automated code review process
  • Integration with GitHub for seamless workflow
  • Local deployment option via MCP server
  • Customizable review criteria

use cases of ai-reviewer?

  1. Enhancing code quality in collaborative projects on GitHub.
  2. Providing instant feedback to developers during the coding process.
  3. Ensuring adherence to coding standards and best practices.

FAQ from ai-reviewer?

  • Can ai-reviewer be used for any programming language?

Yes! ai-reviewer supports multiple programming languages and can be customized for specific needs.

  • Is ai-reviewer free to use?

The licensing details are not specified, please check the repository for more information.

  • How does ai-reviewer ensure code quality?

ai-reviewer uses advanced AI algorithms to analyze code and provide actionable feedback.

Project Info
Created At
a year ago
Updated At
a year ago
Author Name
JFinchy
Star
0
Language
-
License
-

Recommend Servers

View All
Bring your real authenticated browser session to AI coding agents. Local-first MCP server + Chrome MV3 extension. No cloud. No telemetry.
@Cubenest

peek records the user's actual logged-in browser (DOM via rrweb, console events, network metadata, optional response bodies via opt-in Deep capture) through a Chrome MV3 extension. The extension ships events through a native-messaging stdio bridge to a local MCP server (peek-mcp), which persists them to a SQLite database at ~/.peek/sessions.db. AI coding agents (Claude Code, Cursor, Cline, Windsurf) read sessions from the database via 10 MCP tools: Tool What it does list_recent_sessions List recently recorded sessions (id, origin, ts, event count). get_session_summary LLM-readable narrative summary of a session. get_session_console_errors Console errors recorded in a session. get_session_network_errors Failed/notable network requests in a session. get_user_action_before_error Last N user actions before a console error. generate_playwright_repro Generate a runnable Playwright test from a session. get_dom_snapshot Reconstruct the DOM at a given timestamp. query_dom_history Timeline of attribute/text changes for a selector. request_authorization Side-panel consent for write actions (Level 3). execute_action Dispatch a UI action (gated by permission level + destructive blocklist). Why local-first matters Every other "browser session for AI" tool ships to a vendor cloud. peek's SQLite + extension live on the user's machine — no remote endpoints, no telemetry. The privacy policy (docs/peek/PRIVACY_POLICY.md) is the source of truth. Install # 1. Add the MCP server to Claude Code claude mcp add peek -- npx -y @peekdev/mcp # 2. Install the Chrome extension from the Chrome Web Store # (link added once the CWS listing is approved)

a day ago