kwp-engineering-code-review

Analyze source code for security vulnerabilities, performance bottlenecks, and maintainability issues from pull request URLs or local file paths.

7|5|Updated May 7, 2026
One-click install
npx skills add https://github.com/14790897/MiQi --skill kwp-engineering-code-review
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: kwp-engineering-code-review
Source: https://github.com/14790897/MiQi/tree/main/miqi/skills/kwp/engineering/code-review
Command: npx skills add https://github.com/14790897/MiQi --skill kwp-engineering-code-review

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This skill addresses the cognitive load and oversight risks inherent in manual code reviews by providing a structured, automated analysis of security, performance, and maintainability.

Core Features & Use Cases

  • Security Audit: Automatically scans for common vulnerabilities like SQL injection, XSS, and credential exposure.
  • Performance Analysis: Identifies potential bottlenecks such as N+1 queries, memory leaks, and inefficient algorithmic complexity.
  • Maintainability Checks: Evaluates code against best practices for naming, modularity, and documentation.
  • Use Case: Before merging a pull request, use this skill to ensure the new changes adhere to team standards and do not introduce critical security or performance regressions.

Quick Start

Ask the agent to review the code changes by providing the URL of the pull request or the path to the local file.

Frequently Asked Questions about kwp-engineering-code-review

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

FAQPage Schema
How do I automate code review for security vulnerabilities and performance bottlenecks?

Automated code review analyzes source code to detect security vulnerabilities like SQL injection and XSS, alongside performance bottlenecks such as N+1 queries and memory leaks. It provides actionable feedback to improve code quality.

Can I run static analysis directly on a pull request URL before merging?

Yes, static analysis can operate directly on a pull request URL or local file paths. It evaluates new changes against team standards and integrates with source control to link findings directly to development workflows.

What specific performance and maintainability issues does static code analysis detect?

Static code analysis identifies performance bottlenecks like inefficient algorithmic complexity and N+1 queries, while also evaluating maintainability by checking naming conventions, modularity, and documentation.

Does automated code review require integrating source control tools to function?

Automated code review operates on local file paths or pull request URLs independently. However, integrating source control and project management tools links findings directly to development workflows.

What is the best way to check for credential exposure and security flaws in new code changes?

The best way to check for credential exposure is using an automated security audit that scans source code for common vulnerabilities. This ensures new changes do not introduce critical security regressions before merging.