auto-sec-report

Aggregate security findings from merged pull requests into markdown and HTML reports.

Updated May 31, 2026
One-click install
npx skills add https://github.com/zizzfizzix/agentic-engineering-framework --skill auto-sec-report
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: auto-sec-report
Source: https://github.com/zizzfizzix/agentic-engineering-framework/tree/main/core/ai/skills/auto-sec-report
Command: npx skills add https://github.com/zizzfizzix/agentic-engineering-framework --skill auto-sec-report

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill requires auto-sec-report-pr, and includes scripts (resource) and references (resource) and assets (resource) components.

What problem does it solve?

This Skill automates the security analysis of merged pull requests, aggregating findings into a single report for review.

Core Features & Use Cases

  • Aggregate Security Analysis: Loops over a window of merged PRs and aggregates findings.
  • Documentation & HTML Output: Writes markdown and HTML reports for review.
  • Use Case: Ideal for organizations that want to streamline the process of reviewing security findings across multiple pull requests.

Quick Start

Generate a security report for the past 7 days of merged PRs.

Frequently Asked Questions about auto-sec-report

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

FAQPage Schema
How do I automate security analysis across multiple merged pull requests?

Automate security analysis across merged pull requests by looping over a specified window and aggregating findings into a single report. This Skill processes PRs based on date, PR number, branch, or spec to generate comprehensive security reviews.

What is the best way to generate an aggregate security report for merged PRs?

The best way to generate an aggregate security report is to run an automated analysis over a range of merged PRs. It consolidates individual PR security findings and outputs both markdown and HTML formats for streamlined review.

Can I filter the security analysis of merged pull requests by branch and date?

Yes, you can filter the security analysis of merged pull requests by branch, date, PR number, and spec. These parameters define the window of analysis to ensure the aggregate report covers only the relevant merged PRs.

Do I need a per-unit PR security analysis tool before aggregating findings?

Yes, you need a per-PR security analysis tool. This Skill requires the auto-sec-report-pr dependency to perform individual pull request analysis before it can loop through the window and aggregate the findings into a comprehensive report.

Does the aggregate security report output in HTML and markdown formats?

Yes, the aggregate security report outputs in both HTML and markdown formats. Once the analysis loops through the defined window of merged pull requests, it writes these documentation files for immediate organizational review.