Run any Skill in Manus with one click

code-reviewer

Reviews Python code for quality, style, and common bugs. Use when the user submits code for review, asks for feedback on their code, or wants a code audit.

Run Skill in Manus

Overview

Reviews Python code for quality, style, and common bugs. Use when the user submits code for review, asks for feedback on their code, or wants a code audit.

Install command

npx skills add https://github.com/lavinigam-gcp/build-with-adk --skill code-reviewer

Copy and paste this command into Claude Code to install the skill

Source

lavinigam-gcp/build-with-adk

Stars43

Forks9

UpdatedMarch 7, 2026 at 18:30

File Explorer

2 files

SKILL.md

readonly

name	code-reviewer
description	Reviews Python code for quality, style, and common bugs. Use when the user submits code for review, asks for feedback on their code, or wants a code audit.
metadata	{"pattern":"reviewer","severity-levels":"error,warning,info"}

You are a Python code reviewer. Follow this review protocol exactly:

Step 1: Load 'references/review-checklist.md' for the complete review criteria.

Step 2: Read the user's code carefully. Understand its purpose before critiquing.

Step 3: Apply each rule from the checklist to the code. For every violation found:

Note the line number (or approximate location)
Classify severity: error (must fix), warning (should fix), info (consider)
Explain WHY it's a problem, not just WHAT is wrong
Suggest a specific fix with corrected code

Step 4: Produce a structured review with these sections:

Summary: What the code does, overall quality assessment (1-2 sentences)
Findings: Grouped by severity (errors first, then warnings, then info)
Score: Rate 1-10 with brief justification
Top 3 Recommendations: The most impactful improvements

More from this repository

same repository

agent-tester

lavinigam-gcp/build-with-adk

Tests generated ADK agent code through a save-first validation pipeline. Saves code to disk FIRST, then tests the saved code via start_agent and talk_to_agent. Drives the iterative refinement loop.

2026-03-1343

api-expert

lavinigam-gcp/build-with-adk

FastAPI development best practices and conventions. Use when building, reviewing, or debugging FastAPI applications, REST APIs, or Pydantic models.

2026-03-0743

doc-pipeline

lavinigam-gcp/build-with-adk

Generates API documentation from Python source code through a multi-step pipeline. Use when the user asks to document a module, generate API docs, or create documentation from code.

2026-03-0743

project-planner

lavinigam-gcp/build-with-adk

Plans a new software project by gathering requirements through structured questions before producing a plan. Use when the user says "I want to build", "help me plan", "design a system", or "start a new project".

2026-03-0743

report-generator

lavinigam-gcp/build-with-adk

Generates structured technical reports in Markdown. Use when the user asks to write, create, or draft a report, summary, or analysis document.

2026-03-0743

blog-writer

lavinigam-gcp/build-with-adk

Blog post writing skill with structure templates and style guidelines. Guides the agent through writing well-structured, engaging technical blog posts with proper formatting, section flow, and reader engagement techniques.

2026-03-0443

Source

lavinigam-gcp

lavinigam-gcp/build-with-adk

View GitHub Repository View Creator Repositories

Install command

Download

Run Skill in Manus

Useful forSOC

Software Quality Assurance Analysts and TestersComputer and Mathematical Occupations15-1253L4

name	code-reviewer
description	Reviews Python code for quality, style, and common bugs. Use when the user submits code for review, asks for feedback on their code, or wants a code audit.
metadata	{"pattern":"reviewer","severity-levels":"error,warning,info"}

You are a Python code reviewer. Follow this review protocol exactly:

Step 1: Load 'references/review-checklist.md' for the complete review criteria.

Step 2: Read the user's code carefully. Understand its purpose before critiquing.

Step 3: Apply each rule from the checklist to the code. For every violation found:

Note the line number (or approximate location)
Classify severity: error (must fix), warning (should fix), info (consider)
Explain WHY it's a problem, not just WHAT is wrong
Suggest a specific fix with corrected code

Step 4: Produce a structured review with these sections:

Summary: What the code does, overall quality assessment (1-2 sentences)
Findings: Grouped by severity (errors first, then warnings, then info)
Score: Rate 1-10 with brief justification
Top 3 Recommendations: The most impactful improvements