skills.rest
Terry-Mao
Terry-MaoCOMMUNITY
Explore all skills by this author →
WebsiteGitHub

security-review-spec

Audit GitHub pull request diffs for security threats in product or tech specs.

144|16|Updated May 3, 2026
Search Tags:#github#security review#specification analysis#vulnerability identification#PR diff audit
One-click install
npx skills add https://github.com/Terry-Mao/AICodingFlow --skill security-review-spec-terry-mao
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: security-review-spec
Source: https://github.com/Terry-Mao/AICodingFlow/tree/main/.github/skills/security-review-spec
Command: npx skills add https://github.com/Terry-Mao/AICodingFlow --skill security-review-spec-terry-mao

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes scripts (resource) and references (resource) components.

What problem does it solve?

The Skill addresses the issue of identifying high-level security concerns in pull request diffs for product or tech specs.

Core Features & Use Cases

  • Security Audit: Identifies and reports security threats in spec pull requests.
  • Supplemental to Review: Works as a supplement to review-spec, adding security findings to the same review report.
  • Use Case: Enhance the security review process in GitHub PRs by identifying and highlighting potential security vulnerabilities.

Quick Start

Run the security-review-spec skill on the pull request to audit its spec for security concerns.

Frequently Asked Questions about security-review-spec

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

FAQPage Schema
How do I conduct a security audit on GitHub PR diffs for specification documents?▼

A design-level security audit on spec PR diffs identifies gaps and ambiguities in product or tech specifications that could lead to insecure implementations. It focuses on high-level threats rather than executing code-level vulnerability scans.

What is the best way to identify security vulnerabilities in specification pull requests?▼

The best way to identify security vulnerabilities in specification pull requests is performing a design-level audit on the PR diffs. This process detects potential threats and ambiguities in tech specs before they translate into insecure code implementations.

Does this spec security review process check for code-level vulnerabilities?▼

No, this spec security review does not perform code-level vulnerability checks. It conducts a design-level audit strictly focused on identifying potential threats, gaps, and ambiguities within product or tech specification diffs.

Can I use this security audit to supplement an existing PR spec review report?▼

Yes, you can use this security audit to supplement an existing PR spec review report. It works alongside the standard review-spec process by appending identified security findings directly into the same review output.

Why should I audit specification ambiguities for potential security threats?▼

Auditing specification ambiguities for security threats prevents insecure implementations by highlighting gaps in product or tech specs early. Addressing these design-level vulnerabilities during the PR diff stage ensures secure foundational logic before coding finalizes.

Related Skills

Explore More Software Engineering Skills→
rickyanandarickyananda
1

github-code-review

Reviews GitHub pull requests and local diffs for security and quality issues.

Community
Advanced
NUMU-IONUMU-IO
2

speckit-red-team-run

Analyze functional specifications for adversarial gaps and generate structured findings reports.

Official
Advanced
shalevaminshalevamin

security-threat-model

Generate repository-grounded Markdown threat models with trust boundaries and abuse paths.

Community
Advanced
EastSwordEastSword
52

dfyx_code_security_review

Audit source code security vulnerabilities across nine programming languages.

Community
Advanced