backend-code-review

Analyze backend Python code against checklist rules for quality and security.

Updated Aug 23, 2026
One-click install
npx skills add https://github.com/bayazknn/elciai-platform-analysis --skill backend-code-review-bayazknn
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: backend-code-review
Source: https://github.com/bayazknn/elciai-platform-analysis/tree/main/langflow/.agents/skills/backend-code-review
Command: npx skills add https://github.com/bayazknn/elciai-platform-analysis --skill backend-code-review-bayazknn

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Review backend code for quality, security, maintainability, and best practices based on established checklist rules. Use when the user requests a review, analysis, or improvement of backend files (e.g., .py) under the src/backend/ directory. Do NOT use for frontend files (e.g., .tsx, .ts, .js).

Core Features & Use Cases

  • Pending-change review: inspect staged/working-tree changes to assess current diffs.
  • Snippet review: evaluate pasted code snippets for issues and improvements.
  • File-focused review: review specific files or small sets (e.g., src/backend/xxx).

Quick Start

Provide the backend file or code snippet you want reviewed to begin the assessment.

Frequently Asked Questions about backend-code-review

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
What is backend Python code review and what does it check for?

Backend Python code review analyzes source files to evaluate quality, security, maintainability, and best practices. It checks code against established checklist rules to identify issues and produce actionable fixes for your backend application.

How do I review backend Python code for security and maintainability issues?

To review backend Python code for security and maintainability, provide a specific file, staged changes, or a pasted code snippet. The review assesses the code against established checklist rules and outputs recommended improvements and optional code snippets to implement changes.

Can I review pending git changes or just specific backend files?

Yes, you can review pending git changes. The review supports pending-change reviews to inspect staged or working-tree diffs, snippet reviews for pasted code, and file-focused reviews for specific files under the src/backend/ directory.

Does this code review work for frontend TypeScript or JavaScript files?

No, this code review does not work for frontend files like .ts, .tsx, or .js. It is strictly designed to analyze backend Python files located within the src/backend/ directory structure.

What is the best way to review a small Python code snippet for best practices?

The best way to review a small Python code snippet is to paste the code directly for a snippet review. The analysis evaluates the snippet for quality and best-practice issues, then produces actionable fixes and recommended improvements.

Why should I not use a general code review for my backend Python files?

General code reviews lack specialized backend Python checklist rules for security and maintainability. This targeted review analyzes src/backend/ files specifically against established backend best practices to produce actionable fixes and recommended improvements.