security-patterns

Detect security weaknesses in TypeScript/JavaScript code during reviews.

Updated Jan 18, 2026
One-click install
npx skills add https://github.com/BenjaminRose805/react-basecamp --skill security-patterns-benjaminrose805
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: security-patterns
Source: https://github.com/BenjaminRose805/react-basecamp/tree/main/.claude/skills/core/security-patterns
Command: npx skills add https://github.com/BenjaminRose805/react-basecamp --skill security-patterns-benjaminrose805

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This Skill provides a security-focused checklist to help teams detect secrets, insecure logging, input validation gaps, and other common vulnerabilities during code reviews.

Core Features & Use Cases

  • Secret detection: Uncovers hardcoded API keys, credentials, and other sensitive data in the codebase.
  • Logging hygiene: Flags excessive or insecure console logging and unstructured logs that may leak data.
  • Validation discipline: Enforces presence of input validation on API endpoints and routes.
  • OWASP alignment: Provides practical guidance aligned with the OWASP Top 10 risks and remediation steps.
  • Audit & remediation: Generates actionable fixes and references to help PR resolutions.

Quick Start

Run the security-patterns skill during code reviews to automatically scan for secrets, logging issues, input validation gaps, and more, and guide remediation within the PR workflow.

Frequently Asked Questions about security-patterns

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

FAQPage Schema
How do I detect hardcoded secrets and exposed API keys during code reviews?

Secret detection during code reviews identifies hardcoded credentials and API keys by scanning the codebase against security patterns, providing remediation guidance directly in PR feedback.

How do I prevent XSS and SQL injection risks in TypeScript projects?

Preventing XSS and SQL injection risks in TypeScript projects involves applying an OWASP-aligned checklist during CI pipeline checks to detect vulnerabilities and enforce secure coding patterns.

What is the best way to enforce input validation on API endpoints in pull requests?

Enforcing input validation on API endpoints is achieved by running an automated security checklist during pull request checks to flag missing validation rules and suggest concrete fixes.

Does this security review skill work with JavaScript CI pipelines?

Yes, this security review skill is designed for TypeScript and JavaScript projects, integrating into CI pipelines and pull request workflows to surface issues like insecure logging and improper authorization.

How do I flag insecure console logging that might leak sensitive data?

Flagging insecure console logging involves scanning for excessive or unstructured logs during code reviews to prevent data leakage, generating actionable audit results for PR resolution.

How does an OWASP-aligned checklist improve secure code reviews?

An OWASP-aligned checklist improves secure code reviews by systematically evaluating code against the Top 10 risks, detecting authorization gaps and validation issues while providing practical remediation steps.