skills.rest
KentoShimizu
KentoShimizuCOMMUNITY
Explore all skills by this author →
𝕏@KStartup_GitHub

code-review-security

Identify security weaknesses in code changes crossing trust boundaries.

7|Updated Feb 14, 2026
Search Tags:#authorization#security#authentication#vulnerabilities#code-review#risk#threat-model
One-click install
npx skills add https://github.com/KentoShimizu/sw-agent-skills --skill code-review-security-kentoshimizu
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: code-review-security
Source: https://github.com/KentoShimizu/sw-agent-skills/tree/main/skills/code-review-security
Command: npx skills add https://github.com/KentoShimizu/sw-agent-skills --skill code-review-security-kentoshimizu

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Identify security weaknesses and data-protection risks in code changes before merge.

Core Features & Use Cases

  • Map changed code to trust boundaries and assets.
  • Evaluate exploit paths across input handling, authentication/authorization, and data handling.
  • Verify security controls are present and correctly ordered.
  • Identify regressions introduced by fallback or bypass logic.
  • Publish prioritized findings and remediation requirements.

Quick Start

Run a security-focused code review on the changed components before merging to surface exploitable weaknesses.

Frequently Asked Questions about code-review-security

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

FAQPage Schema
How do I catch security vulnerabilities in a pull request before merging?▼

Identify security vulnerabilities in code changes by evaluating exploit paths across input handling, authentication, authorization, and data handling. This verifies security controls are correctly ordered and present before merge.

What is the best way to find authorization and authentication regressions in code reviews?▼

Find authentication and authorization regressions in code reviews by identifying bypass logic introduced by fallback mechanisms. This verifies security controls are correctly ordered and present across trust boundaries.

How do I review code changes for data exposure and input validation risks?▼

Review code changes for data exposure and input validation risks by evaluating exploit paths across data handling and input processing. This produces prioritized findings with remediation guidance for security-sensitive areas.

Can I get prioritized risk levels and remediation guidance for security weaknesses?▼

Get prioritized risk levels and remediation guidance for security weaknesses by running a security-focused code review on changed components. This yields structured deliverables with evidence-based findings and remediation requirements.

When do I need to map trust boundaries and assets during a security code review?▼

Map trust boundaries and assets during a security code review when changes cross trust boundaries in security-sensitive areas. This identifies data-protection risks and ensures security controls are correctly ordered before merge.

Related Skills

Explore More Software Engineering Skills→
esopianesopian
2

review

Analyze code diffs for security, correctness, and structural integrity.

Community
Intermediate
SpencerGossSpencerGoss

security-audit

Identify security issues, exposed credentials, and insecure configurations in codebases.

Community
Advanced
qdzshqdzsh
12

security-review

Run STRIDE-based threat modeling and generate a prioritized security findings report.

Community
Advanced
zebbernzebbern
4.5k

AWS Penetration Testing

Enumerate AWS IAM misconfigurations and privilege escalation paths.

Community
Advanced