safety-check

Identify runtime and security vulnerabilities in codebases during reviews.

4|Updated Sep 6, 2013

Search Tags:#security #vulnerability #owasp #runtime #static-analysis #code-review #safety-audit

Ready to run

npx skills add https://github.com/mway/dotfiles --skill safety-check

💬 Prompt for ChatGPT / Claude Chat▼

Please help me install this Agent Skill.
Skill: safety-check
Source: https://github.com/mway/dotfiles/tree/main/home/dot_codex/skills/safety-check
Command: npx skills add https://github.com/mway/dotfiles --skill safety-check

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Audits codebases for runtime safety and security vulnerabilities to prevent defects before commits and during reviews.

Core Features & Use Cases

Runtime safety coverage across common categories (nil/null dereferences, race conditions, resource leaks, bounds checks, integer overflow, uninitialized values, error handling, panics, deadlocks).
Security safety aligned with OWASP Top 10+ to detect injections, authentication/authorization gaps, data exposure, input validation, cryptography pitfalls.
Practical guidance and references to a central safety checklist for both runtime and security assessments.

Quick Start

Audit your codebase now by applying the safety-check workflow to identify and remediate runtime and security issues.

Frequently Asked Questions about safety-check

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

FAQPage Schema

How do I check my codebase for runtime vulnerabilities like null dereferences and race conditions?▼

Audit codebases for runtime vulnerabilities by applying a structured safety checklist covering nil/null dereferences, race conditions, resource leaks, bounds checks, integer overflows, uninitialized values, panics, and deadlocks during code reviews or pre-commit checks.

Can I detect OWASP Top 10 security issues during a code review?▼

Detect OWASP Top 10+ security issues during code reviews by checking for injections, authentication gaps, data exposure, input validation errors, and cryptography pitfalls using a structured security safety checklist referenced by the audit workflow.

What is the best way to prevent security defects before committing code?▼

Prevent security defects before commits by running a safety audit that identifies runtime issues and OWASP Top 10+ threat areas across languages, providing practical remediation guidance aligned with a central safety checklist.

Does this static analysis safety audit work across different programming languages?▼

This safety audit works across languages and projects, applying a unified checklist to identify runtime safety issues and security vulnerabilities without requiring language-specific static analysis tool configurations.

How do I audit code for deadlocks and resource leaks?▼

Audit code for deadlocks and resource leaks by applying the runtime safety checklist, which systematically scans for concurrency issues, memory leaks, uninitialized values, and error handling gaps across your codebase.

Why should I use a structured checklist for security assessments instead of ad hoc code review?▼

A structured checklist ensures comprehensive coverage of both runtime safety issues and OWASP Top 10+ security vulnerabilities, preventing missed defects during code reviews and pre-commit checks across diverse languages and projects.