security-review

Apply a security checklist to identify vulnerabilities in APIs and features.

Updated Jan 17, 2026
One-click install
npx skills add https://github.com/joonwon-space/kis-api-ai --skill security-review-joonwon-space
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: security-review
Source: https://github.com/joonwon-space/kis-api-ai/tree/main/.claude/skills/security-review
Command: npx skills add https://github.com/joonwon-space/kis-api-ai --skill security-review-joonwon-space

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This Skill helps teams identify and remediate security gaps across authentication, input handling, secrets management, API design, and payments.

Core Features & Use Cases

  • Security best-practice checklist covering secrets, input validation, authentication, authorization, logging, rate limiting, and data handling.
  • Practical patterns and examples for secure API design, secure coding, and secure deployment.
  • Use Case: When reviewing a new API or feature, apply this Skill to identify vulnerabilities and harden the implementation before release.

Quick Start

Run the security review on a new API endpoint or feature by applying the checklist to identify vulnerabilities before deployment.

Frequently Asked Questions about security-review

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

FAQPage Schema
How do I perform a security code review before deploying a new API?

Security code review identifies and remediates gaps across authentication, input handling, secrets management, and API design. It enforces a comprehensive checklist covering input validation, authorization, logging, and rate limiting to guide secure-by-default practices.

What areas does a comprehensive security review checklist cover?

A comprehensive security review checklist covers secrets, input validation, authentication, authorization, logging, rate limiting, and data handling. It provides practical patterns and examples for secure API design, secure coding, and secure deployment.

When do I need to check my code for secrets management and input validation vulnerabilities?

You need to check code for secrets management and input validation vulnerabilities during code reviews, API development, and infrastructure changes. This enforces secure-by-default practices and mitigates risks before deployment.

Can I use this security review to harden authentication and authorization logic?

Yes, you can use this security review to harden authentication and authorization logic. It applies practical patterns and examples to identify vulnerabilities and guide secure implementation, testing, and risk mitigation.

What is the best way to identify security gaps in API design and payments?

The best way to identify security gaps in API design and payments is applying a security checklist during code reviews. It guides secure-by-default practices, covering input handling, authorization, logging, and risk mitigation.

Are there limitations to using a security checklist for infrastructure changes?

Using a security checklist for infrastructure changes focuses on identifying gaps in authentication, input handling, and secrets management. It provides secure coding patterns but requires manual application during code reviews to ensure comprehensive risk mitigation.