Comprehensive security report

Skill JeremyMorgan/code-review-skills/skills/comprehensive-security-report

Aggregates findings from the other security audits into one prioritized security report. Use after running individual security reviews to produce a consolidated report.From its SKILL.md

Install

npx -y skills add JeremyMorgan/code-review-skills --skill comprehensive-security-report

Assembled from the repository path, not quoted from the project. Check it against their README if it does not work.

One thing to look at

12 stars12 stars. Stars are a popularity signal and not a quality one, but at this level it is likely that nobody has read this closely except its author, and you would be relying on your own review.

What its file declares

Copied from the file, not written here

The file declares its own license as CC0-1.0. That is the author’s claim about this one file, and it is not the same thing as the license GitHub reports for the repository, which is listed with the other numbers below.

SKILL.md

2.2 KB, as published. Nobody here has run it

Target: $ARGUMENTS

If no target path is given above, review the entire codebase.

Comprehensive Security Report

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:

Executive Summary

Summarize the overall security posture (Critical/High/Medium/Low), total vulnerability counts by severity, and the top immediate actions required.

Critical Vulnerabilities (Fix Immediately)

List each critical finding with its source audit file, CWE reference if applicable, and affected code locations.

High Priority Issues (Fix within 1 week)

List each high-severity finding with code locations and remediation steps.

Medium Priority Issues (Fix within 1 month)

List each medium-severity finding with recommendations.

Low Priority Issues (Fix in next release)

List low-severity improvements.

Security Recommendations

Implementation priorities
Security tools to adopt
Process improvements
Training needs

Compliance Checklist

OWASP Top 10 coverage
PCI DSS (if handling payments)
GDPR (if handling EU data)
SOC 2 requirements

Testing Guide

Include curl commands or test scripts to verify each fix.

Constraints & style:

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.