skills.rest
jwlutz
jwlutzCOMMUNITY
Explore all skills by this author →
WebsiteGitHub

risk-detection

Detect code risks and security issues during review and write findings to risks.md.

3|1|Updated Jan 23, 2026
Search Tags:#security#static-analysis#code-review#pattern-matching#risk-detection#risk-tracking#file-line-reference
One-click install
npx skills add https://github.com/jwlutz/claude_code_framework --skill risk-detection
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: risk-detection
Source: https://github.com/jwlutz/claude_code_framework/tree/main/skills/risk-detection
Command: npx skills add https://github.com/jwlutz/claude_code_framework --skill risk-detection

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Detects code risks and security issues during review, risk scanning, or code evaluation. Writes findings to risks.md with impact level and file:line references.

Core Features & Use Cases

  • Pattern-based risk detection across languages with impact tagging and file:line references.
  • Writes findings to risks.md to enable traceability and risk tracking.
  • Use Case: While reviewing a PR, surface potential secrets, insecure patterns, or maintainability concerns with precise locations.

Quick Start

Run a risk scan on your codebase to generate a risks.md report.

Frequently Asked Questions about risk-detection

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

FAQPage Schema
How do I detect security risks and insecure patterns during a code review?▼

Risk detection scans your codebase to identify potential secrets, insecure patterns, and maintainability concerns, generating a risks.md report with impact levels and file:line references for each issue.

What is pattern-matching risk detection and how does it surface code risks?▼

Pattern-based risk detection scans source code to identify security issues and maintainability concerns, writing findings to risks.md with impact levels and file:line references for tracking.

Can I use automated risk scanning to track secrets in pull requests?▼

Yes, automated risk scanning applies to pull request workflows to surface exposed secrets and insecure patterns, writing findings with impact levels and file:line references to risks.md for tracking.

What's the best way to track code risks with precise file and line locations?▼

Generating a risks.md report during code review captures pattern-matched security issues with exact file:line references and impact levels, enabling precise risk tracking and traceability.

Does static analysis for risk tracking work across multiple programming languages?▼

Yes, pattern-based risk detection applies across languages to identify security issues and maintainability concerns, centralizing findings in risks.md with impact levels and file:line references.

How do I generate a risks.md report for code evaluation?▼

Run a risk scan on your codebase to generate a risks.md report for code evaluation. The scan identifies security issues and maintainability concerns, documenting findings with impact levels and file:line references.

Related Skills

Explore More Software Engineering Skills→
jikig-aijikig-ai
12

semgrep-sast

Scan git-diff-selected source files with semgrep for vulnerability patterns.

Official
Intermediate
catlog22catlog22
511

manage-issue-discover

Scan JavaScript and TypeScript codebases to generate deduplicated issue records.

Community
Advanced
ofelixdevofelixdev

fp-check

Verify suspected security bugs and produce TRUE POSITIVE or FALSE POSITIVE verdicts.

Community
Advanced
matteocervellimatteocervelli
25

security-scanner

Scan codebases for secrets, vulnerable dependencies, and insecure patterns.

Community
Advanced