Code Review Skill

Name: Code Review Skill
Availability: InStock
Author: powerfulmoves

Analyze code for OWASP Top 10 vulnerabilities and generate risk scores.

1|Updated Nov 7, 2025

Search Tags:#developer tools #static analysis #code review #security #owasp #vulnerability scanning

Ready to run

npx skills add https://github.com/POWERFULMOVES/PMOVES-BoTZ --skill code-review-skill-powerfulmoves

💬 Prompt for ChatGPT / Claude Chat▼

Please help me install this Agent Skill.
Skill: Code Review Skill
Source: https://github.com/POWERFULMOVES/PMOVES-BoTZ/tree/main/features/agent_sdk/slices/code_review
Command: npx skills add https://github.com/POWERFULMOVES/PMOVES-BoTZ --skill code-review-skill-powerfulmoves

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes scripts (resource) and references (resource) components.

What problem does it solve?

This Skill automates the process of identifying security vulnerabilities in code, ensuring that code changes are reviewed for potential risks before being merged.

Core Features & Use Cases

Security Vulnerability Detection: Scans code for common security flaws aligned with OWASP Top 10.
Automated Risk Assessment: Assigns severity levels (Critical, High, Medium, Low) to identified findings.
Use Case: Integrate this skill into your CI/CD pipeline to automatically fail builds that introduce critical security vulnerabilities, or use it during code reviews to flag potential issues for developers.

Quick Start

Use the code review skill to analyze the 'src/api/' and 'src/auth/' directories for injection and authentication vulnerabilities.

Frequently Asked Questions about Code Review Skill

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

FAQPage Schema

How do I automate vulnerability scanning for OWASP Top 10 flaws in my code?▼

Automating vulnerability scanning detects OWASP Top 10 flaws like injection issues and weak cryptography by analyzing code changes. This process assigns severity levels and generates detailed findings to prevent risks before merging.

How do I integrate static analysis into a CI/CD pipeline to fail builds with security vulnerabilities?▼

Integrating static analysis into a CI/CD pipeline scans code changes to identify critical security vulnerabilities. It automatically fails builds by generating a risk score and detailed findings before code is merged.

Can I use automated code reviews to check for exposed secrets and authentication issues?▼

Automated code reviews can check for exposed secrets and authentication issues by analyzing source directories. The review identifies these vulnerabilities and generates a risk assessment based on the findings.

What is the best way to identify input validation problems during a pull request review?▼

The best way to identify input validation problems during a pull request review is through security-focused static analysis. This approach flags potential issues and assigns severity levels to the findings for developer action.

Does automated security scanning generate risk scores for pre-commit hooks?▼

Automated security scanning generates risk scores and detailed findings suitable for integration into pre-commit hooks. It evaluates code for injection flaws, exposed secrets, and weak cryptography to ensure secure commits.

What types of weak cryptography are detected during security-focused code reviews?▼

Security-focused code reviews detect weak cryptography by analyzing code for vulnerabilities aligned with OWASP Top 10 categories. They generate a risk score and detailed findings for integration into pipelines and pull request reviews.