supabase-report-compare

Compare two Markdown security audit reports to identify changes in findings and remediation progress.

62|3|Updated Jan 31, 2026
One-click install
npx skills add https://github.com/yoanbernabeu/supabase-pentest-skills --skill supabase-report-compare
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: supabase-report-compare
Source: https://github.com/yoanbernabeu/supabase-pentest-skills/tree/main/skills/report/supabase-report-compare
Command: npx skills add https://github.com/yoanbernabeu/supabase-pentest-skills --skill supabase-report-compare

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This Skill helps security teams track remediation progress by comparing two security audit reports and highlighting changes in findings, scores, and status over time.

Core Features & Use Cases

  • Side-by-side comparison of two Markdown audit reports to show fixed, new, and remaining findings.
  • Trend and regression detection to identify regressions and measure remediation effectiveness across dates.
  • Use Case: After applying remediations, compare the latest report with the previous one to verify fixes and catch regressions.

Quick Start

Compare two audit reports by path, for example: Compare reports/old-audit.md with reports/new-audit.md

Frequently Asked Questions about supabase-report-compare

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

FAQPage Schema
How do I compare two security audit reports to track remediation progress?

Security audit report comparison identifies remediation progress by matching findings using ID, component, and location data to highlight fixed, new, and remaining vulnerabilities between two periods.

Can I use Markdown audit reports for regression analysis after applying fixes?

Yes, Markdown audit reports support regression analysis by comparing previous and latest reports to verify applied fixes and detect any newly introduced regressions across the same project over time.

What is the best way to detect security regressions in periodic audit reviews?

Detecting security regressions in periodic reviews involves comparing two structured audit reports side-by-side to measure remediation effectiveness and catch any findings that reappear across dates.

Do I need a consistent Markdown structure to compare security findings?

Yes, comparing security findings requires two Markdown-formatted reports with consistent structure to accurately match findings by ID, component, and location and determine status changes.