devsec-saving-report

Save security artifacts to local markdown files with date-stamped filenames.

Updated Aug 27, 2026
One-click install
npx skills add https://github.com/wizeline/sdlc-agents --skill devsec-saving-report
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: devsec-saving-report
Source: https://github.com/wizeline/sdlc-agents/tree/main/aicores/security-agent/skills/devsec-saving-report
Command: npx skills add https://github.com/wizeline/sdlc-agents --skill devsec-saving-report

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This Skill helps you save security artifacts generated during a session into well-structured markdown files on your local filesystem, preventing data loss and ensuring easy access.

Core Features & Use Cases

  • Automated File Saving: Saves security reports (code reviews, threat models, vulnerability maps, etc.) to a specified local path.
  • Filename Convention: Automatically suggests and applies a date-stamped filename based on the report type.
  • Use Case: After a security code review, you can use this Skill to save the generated report as code-review-YYYY-MM-DD.md in a dedicated security-reports directory.

Quick Start

Use the devsec-saving-report skill to save the current security report to a markdown file.

Frequently Asked Questions about devsec-saving-report

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

FAQPage Schema
How do I save security reports to a local markdown file?

You can save security reports to a local markdown file by specifying a target directory path, which triggers automated file generation with date-stamped filenames to preserve full content for audit trails.

Can I automatically generate filenames for vulnerability maps and threat models?

Yes, the Skill automatically suggests and applies date-stamped filenames for vulnerability maps and threat models, such as generating a `code-review-YYYY-MM-DD.md` file in a designated directory.

What is the best way to maintain an audit trail for DevSecOps code review reports?

Saving security artifacts as structured local markdown files ensures preservation of standards references and full content, providing a reliable audit trail for DevSecOps code review reports.

Does saving security artifacts locally support custom directory path overrides?

Yes, the Skill supports user-defined path overrides, allowing you to specify custom local directories for saving code review reports, threat models, and vulnerability maps.

When do I need to export security artifacts to markdown files?

You need to export security artifacts to markdown files after generating code reviews or threat models during a session to prevent data loss and ensure easy local access for compliance auditing.