skills.rest
xergioalex
xergioalexCOMMUNITY
Explore all skills by this author →
Website𝕏@XergioAleXGitHub

security-check

Review code changes for secrets, input sanitization, and logging issues.

3|1|Updated May 15, 2025
Search Tags:#code review#security#input validation#logging#owasp#secrets
One-click install
npx skills add https://github.com/xergioalex/xergioalex.com --skill security-check-xergioalex
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: security-check
Source: https://github.com/xergioalex/xergioalex.com/tree/main/.claude/skills/security-check
Command: npx skills add https://github.com/xergioalex/xergioalex.com --skill security-check-xergioalex

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes references (resource) components.

What problem does it solve?

This Skill provides a rapid, checklist-based security review for code changes, identifying common vulnerabilities like hardcoded secrets, improper input handling, and sensitive data in logs.

Core Features & Use Cases

  • Secret Detection: Flags hardcoded API keys, tokens, and passwords.
  • Input Validation Check: Assesses if user input is properly sanitized.
  • Logging Review: Ensures no sensitive data is present in log messages.
  • Use Case: Before merging a pull request, run this skill to quickly scan for obvious security flaws, ensuring basic security hygiene.

Quick Start

Run a security check on the current pull request focusing on secrets and input validation.

Frequently Asked Questions about security-check

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

FAQPage Schema
How do I run a quick security checklist on code changes before merging a pull request?▼

Run a lightweight security checklist on code changes to identify common vulnerabilities like hardcoded secrets, improper input sanitization, and sensitive data exposure in logs before merging a pull request.

What is the best way to detect hardcoded secrets and API keys in static site code?▼

A checklist-based code review detects hardcoded secrets by scanning static site code changes for API keys, tokens, and passwords to prevent sensitive data exposure.

How does a lightweight security review identify OWASP vulnerabilities in input validation?▼

A lightweight security review assesses input validation by checking if user input is properly sanitized, flagging potential OWASP vulnerabilities related to improper input handling.

Can I use this security check to ensure no sensitive data is present in log messages?▼

Yes, you can use this security check to review logging practices, ensuring no sensitive data is present in log messages and preventing accidental data exposure.

What are the limitations of a checklist-based security review for code?▼

A checklist-based security review is lightweight and focuses on obvious flaws; it recommends escalation for deeper analysis when complex OWASP vulnerabilities or advanced security threats are suspected.

Related Skills

Explore More Software Engineering Skills→
OpenHandsOpenHands
134

code-review

Review pull requests for security, readability, and correctness issues.

Official
Intermediate
gvkhoslagvkhosla
49

security-sentinel

Audit code for OWASP Top 10 vulnerabilities and generate remediation reports.

Community
Advanced
statick88statick88
1

vulnerability-scanning

Automate vulnerability detection across code, dependencies, containers, and infrastructure.

Community
Advanced
kollaboraikollaborai
1

security-review

Identify security vulnerabilities in Python codebases without modifying source files.

Community
Advanced