security-diagnosis

Scan repositories for security and compliance weaknesses with prioritized findings.

8|2|Updated May 3, 2026
One-click install
npx skills add https://github.com/ejoongseok/claude-settings --skill security-diagnosis
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: security-diagnosis
Source: https://github.com/ejoongseok/claude-settings/tree/main/claude-code/skills/security-diagnosis
Command: npx skills add https://github.com/ejoongseok/claude-settings --skill security-diagnosis

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This Skill helps you regularly identify security and compliance gaps across an entire codebase by focusing on secrets exposure, authentication/authorization weaknesses, injection risks, dependency/CVE issues, logging/monitoring blind spots, and policy adherence.

Core Features & Use Cases

  • Codebase-wide security posture diagnosis: Performs a recurring, threat-model-driven review at the repository level (including delta mode against previous reports).
  • Targeted deep dives by domain: Supports focused modes such as secrets, auth, injection, dependencies/CVE, and quick summaries.
  • Safety-first reporting: Emphasizes masking sensitive values, avoids public exploit payloads, and validates findings to reduce false positives.

Quick Start

Run the security-diagnosis Skill to produce a full security and compliance diagnosis report for the current codebase by answering the threat-model questions when prompted.

Frequently Asked Questions about security-diagnosis

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

FAQPage Schema
How do I scan my codebase for security vulnerabilities and secrets exposure?

A codebase security audit identifies gaps in secrets management, authentication, input validation, dependency CVEs, and logging by performing read-only repository scanning. It generates prioritized findings while masking sensitive values and applying safety guardrails to reduce false positives.

How do I check my project dependencies for known CVEs and compliance issues?

You can check dependencies for CVEs by running a targeted deep dive mode that focuses on dependency and CVE issues alongside policy adherence. It scans the repository read-only and produces prioritized findings to help track security posture changes from PR to release.

Can I run a security diagnosis on only the recent code changes instead of the whole repository?

Yes, you can run a delta analysis mode security diagnosis to review only recent code changes instead of the entire repository. This mode compares current findings against previous reports to track security posture shifts from pull request to release.

Does the codebase security audit modify my source code or files?

No, the codebase security audit does not modify your source code. It executes strictly read-only repository scanning using grep and file reads to identify authentication weaknesses and injection risks, ensuring your files remain untouched during the compliance diagnosis.

What is the best way to track authentication and authorization weaknesses during pull requests?

The best way to track authentication and authorization weaknesses during pull requests is using a threat-model-driven security posture diagnosis. It performs domain-specific deep dives into auth issues, validates findings to reduce false positives, and supports quick summary modes for fast reviews.