tpo-security-checklist

Enforces security review gates and acceptance checklists across the software development lifecycle.

Updated Mar 22, 2026
One-click install
npx skills add https://github.com/TECH-HY/SKILLS --skill tpo-security-checklist-tech-hy
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: tpo-security-checklist
Source: https://github.com/TECH-HY/SKILLS/tree/main/skills/tpo-security-checklist
Command: npx skills add https://github.com/TECH-HY/SKILLS --skill tpo-security-checklist-tech-hy

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve? Security is often treated as a final cleanup step, leading to missed authorization checks, leaked secrets, and unvalidated inputs reaching production. This Skill embeds structured security gates and checklists into planning, implementation, review, and deployment workflows. ## Core Features & Use Cases - Three Security Gates: Pre-development, during-implementation, and pre-acceptance checkpoints covering authentication, authorization, input validation, secrets, and deployment risk. - Domain Checklists: Detailed review criteria for API security, database security, frontend security, dependency hygiene, infrastructure, logging, and data protection. - Rejection Rules and Output Templates: Explicit conditions under which a Technical Product Owner must reject an implementation, plus a required security impact report format for developer agents. - Use Case: When reviewing a pull request that adds a file upload endpoint, apply the checklist to verify server-side validation, authorization enforcement, rate limits, and abuse-case tests before approval. ## Quick Start Use the security checklist to review this pull request for authentication, authorization, input validation, and secrets handling before approval.

Frequently Asked Questions about tpo-security-checklist

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

FAQPage Schema
How do I add security review to my development workflow?

Apply three security gates: check sensitive data and access rules before development, verify validation and secrets handling during implementation, and confirm security tests and deployment safety before acceptance. Each gate has explicit checklist items.

What should a security checklist for code review include?

Cover authentication, server-side authorization, input validation, output encoding, secrets management, dependency vulnerabilities, safe error handling, and logging hygiene. High-risk patterns like file uploads, payment flows, and webhooks need extra scrutiny.

When should a pull request be rejected for security reasons?

Reject when authorization is missing or unclear, secrets are hardcoded, user input reaches dangerous sinks without validation, webhook verification is absent, or security-sensitive behavior has no tests. Debug mode in production config is also grounds for rejection.

Does this checklist replace penetration testing or security audits?

No. It is a development-lifecycle review framework aligned with OWASP and NIST guidance, not a substitute for dedicated penetration testing, threat modeling, or formal compliance audits on production systems.

What security information should a developer report for sensitive changes?

Report the security impact, authentication and authorization approach, input validation points, sensitive data accessed or logged, abuse cases tested, and residual risks with recommended mitigations.