security-check

Review code changes for input validation, secrets, and dependency security.

Updated Feb 5, 2026
One-click install
npx skills add https://github.com/twlines/maslow --skill security-check-twlines
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: security-check
Source: https://github.com/twlines/maslow/tree/main/skills/security-check
Command: npx skills add https://github.com/twlines/maslow --skill security-check-twlines

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This Skill helps developers identify and mitigate common security vulnerabilities in their code changes before they are merged, reducing the risk of security breaches.

Core Features & Use Cases

  • Input Validation: Ensures all external inputs are properly validated to prevent injection attacks.
  • Secrets Management: Verifies that no sensitive information like API keys or passwords are hardcoded or logged.
  • Dependency Review: Checks for the introduction of new dependencies and ensures existing ones are used securely.
  • Use Case: Before committing a new feature, run this security checklist to ensure no hardcoded secrets or insecure data handling practices are introduced.

Quick Start

Run the security check skill to review the current code changes for vulnerabilities.

Frequently Asked Questions about security-check

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

FAQPage Schema
How do I check my code changes for security vulnerabilities before merging?

To check code changes for security vulnerabilities, run a security checklist focusing on input validation, secrets management, and dependency security to enforce best practices and prevent common issues like SQL injection.

What is the best way to prevent hardcoded secrets and SQL injection in feature development?

The best way to prevent hardcoded secrets and SQL injection is to enforce secure coding standards via a security checklist that verifies external input validation and ensures sensitive information is not hardcoded or logged.

Does this security checklist verify dependency security and external input validation?

Yes, this security checklist verifies dependency security by checking for new dependencies and ensures external input validation to prevent injection attacks during code review.

How do I review dependencies for secure coding standards compliance?

To review dependencies for secure coding standards compliance, run a security check that identifies newly introduced dependencies and ensures existing ones are used securely to mitigate vulnerability risks.

When do I need to run a secure coding checklist for code review?

You need to run a secure coding checklist for code review before committing a new feature, ensuring no hardcoded secrets or insecure data handling practices are introduced into the codebase.