skills.rest
0x0pointer
0x0pointerOFFICIAL
Explore all skills by this author →
GitHub

gh-export

Format penetration testing findings from JSON into GitHub issue markdown blocks.

99|10|Updated Mar 1, 2026
Search Tags:#markdown#vulnerability#github#reporting#pentest#findings
One-click install
npx skills add https://github.com/0x0pointer/agent-smith --skill gh-export
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: gh-export
Source: https://github.com/0x0pointer/agent-smith/tree/main/skills/gh-export
Command: npx skills add https://github.com/0x0pointer/agent-smith --skill gh-export

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes scripts (resource) components.

What problem does it solve?

This Skill automates the conversion of penetration testing findings into a standardized GitHub issue format, streamlining the reporting process for security teams.

Core Features & Use Cases

  • Automated Formatting: Converts raw findings data into ready-to-use Markdown for GitHub issues.
  • Standardized Reporting: Ensures all issues follow a consistent structure including summary, impact, steps to reproduce, and PoC.
  • Use Case: After a pentest, use this Skill to generate GitHub issues for each confirmed vulnerability, allowing developers to quickly understand and address the security flaws.

Quick Start

Use the gh-export skill to format all confirmed pentest findings from findings.json into GitHub issue markdown blocks.

Frequently Asked Questions about gh-export

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

FAQPage Schema
How do I format penetration testing findings into GitHub issue markdown?▼

The Skill automates penetration testing reporting by converting confirmed findings from a JSON file into copy-pasteable GitHub issue markdown blocks. It parses JSON data and applies a strict template to generate actionable developer tickets.

What is the best way to automate vulnerability reporting for GitHub issues?▼

The best way to automate vulnerability reporting for GitHub issues is by parsing JSON finding records and formatting them into standardized markdown blocks. This ensures all security issues follow a consistent structure including summary, impact, and steps to reproduce.

Does this markdown formatting process require a specific JSON file structure?▼

Yes, this markdown formatting process requires parsing JSON data containing confirmed penetration testing findings. The JSON file must hold vulnerability records that can be mapped to a strict markdown template for GitHub issues.

Can I update finding records automatically when generating GitHub issue markdown?▼

Yes, you can update finding records automatically when generating GitHub issue markdown. The formatting process makes HTTP PATCH requests to update the original finding records after creating the standardized markdown blocks.

What sections are included in a standardized GitHub issue for security findings?▼

A standardized GitHub issue for security findings includes a summary, impact, steps to reproduce, and proof of concept. This consistent structure allows developers to quickly understand and address confirmed vulnerabilities.

Related Skills

Explore More Software Engineering Skills→
matteocervellimatteocervelli
25

planning-doc-generator

Generate project assessment Markdown reports from structured JSON data.

Community
Intermediate
enunoenuno

Vuln Tracker

Monitor vulnerability lifecycle status in GitHub repositories via API calls.

Community
Advanced
MinhThang1009MinhThang1009
15

modernize-harden

Scan legacy code for security vulnerabilities and generate a reviewable remediation patch.

Community
Intermediate
mindfortaimindfortai
16

finding-review

Triage cybersecurity findings for validity, exploitability, impact, and evidence quality.

Official
Advanced