القائمة
Aggregates findings from the other security audits into one prioritized security report. Use after running individual security reviews to produce a consolidated report.
التثبيت باستخدام Codex أو Claude انسخ هذا Prompt والصقه في Codex أو Claude أو مساعد آخر ليراجع صفحة Skill ويثبّتها لك.
استنادا إلى تصنيف SOC المهني
Reviews API and infrastructure security configuration, including endpoints, headers, transport, and deployment settings. Use when auditing API or infrastructure hardening.
Conducts a comprehensive authentication security review covering login, sessions, tokens, and credential handling. Use when auditing authentication for vulnerabilities.
Analyzes authorization and access-control logic across routes and resources for privilege and enforcement flaws. Use when auditing authorization, RBAC, or access control.
Analyzes business logic for security flaws such as workflow bypasses, race conditions, and abuse cases. Use when reviewing application logic for exploitable behavior.
Detects duplicated and near-duplicate code across the codebase and suggests consolidation. Use when reviewing for copy-paste code, repeated logic, or DRY violations.
Analyzes code complexity and adherence to quality standards, flagging overly complex functions and metric outliers. Use when auditing maintainability, cyclomatic complexity, or coding-standard compliance.
| name | comprehensive-security-report |
| description | Aggregates findings from the other security audits into one prioritized security report. Use after running individual security reviews to produce a consolidated report. |
| license | CC0-1.0 |
| metadata | {"category":"security"} |
| allowed-tools | Read Grep Glob Write |
| disable-model-invocation | true |
| argument-hint | [path or scope] |
Target: $ARGUMENTS
If no target path is given above, review the entire codebase.
Start by reading all existing audit files in the audits/ directory (e.g. audits/*.md). These were produced by the individual security audit skills. Synthesize their findings into one consolidated report. If no prior audit files exist, perform a fresh analysis of the target codebase before writing the report.
The consolidated report must include:
Summarize the overall security posture (Critical/High/Medium/Low), total vulnerability counts by severity, and the top immediate actions required.
List each critical finding with its source audit file, CWE reference if applicable, and affected code locations.
List each high-severity finding with code locations and remediation steps.
List each medium-severity finding with recommendations.
List low-severity improvements.
Include curl commands or test scripts to verify each fix.
Be concrete and cite exact code locations and identifiers from the source audit files or from direct analysis.
Prefer minimal, drop-in fix snippets over prose.
Do not invent files or functions that aren’t present; if context is missing, mark as Unable to verify and say what code would prove it.
Write this into a markdown file and place it in the audits/ folder.
