sec-audit-remediate

Generate fixes and regression tests from detect-dev SARIF security findings.

25|1|Updated Jan 29, 2026
One-click install
npx skills add https://github.com/parhumm/jaan-to --skill sec-audit-remediate
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: sec-audit-remediate
Source: https://github.com/parhumm/jaan-to/tree/main/adapters/codex/skillpack/skills/sec-audit-remediate
Command: npx skills add https://github.com/parhumm/jaan-to --skill sec-audit-remediate

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Automates remediation workflows for detected security findings by generating targeted fixes and regression tests from detect-dev outputs, helping teams reduce risk faster.

Core Features & Use Cases

  • Parse SARIF/detect-dev results and map findings to CWE categories.
  • Generate code fixes and accompanying regression tests per vulnerability type.
  • Produce an integrated remediation report with integration instructions and risk assessment.

Quick Start

Run the remediation workflow on your detect-dev output to auto-generate fixes and regression tests.

Frequently Asked Questions about sec-audit-remediate

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

FAQPage Schema
How do I automate security remediation from SARIF outputs?

Automating security remediation from SARIF outputs involves parsing detect-dev results, mapping findings to CWE categories, and generating targeted code fixes under a fixes/ directory. It outputs structured remediation reports with risk assessments and integration instructions.

Can I generate regression tests automatically when fixing security vulnerabilities?

Yes, generating regression tests automatically when fixing security vulnerabilities is possible by applying per-CWE remediation patterns. The process creates both the targeted code fixes and their accompanying regression tests under a tests/ directory simultaneously.

Do I need detect-dev SARIF outputs to use automated security remediation?

Yes, detect-dev SARIF outputs are required as the input format for automated security remediation. The workflow parses these SARIF results from backend and frontend codebases to map findings to CWE categories before generating fixes and regression tests.

What is the best way to map SARIF security findings to CWE categories for remediation?

The best way to map SARIF security findings to CWE categories for remediation is using an automated workflow that parses detect-dev outputs and applies per-CWE remediation patterns. This generates targeted code fixes alongside regression tests and a structured report.

Does automated security remediation work with both frontend and backend codebases?

Automated security remediation works with both frontend and backend codebases when they have detect-dev SARIF outputs available. It maps the findings to CWE categories and generates the corresponding fixes and regression tests for the detected vulnerabilities.