Menu
Workflow for creating and submitting bug reports to GitHub
Install with Codex or Claude Copy this prompt, paste it into Codex, Claude, or another assistant, and let it review the skill page and install it for you.
Based on SOC occupation classification
Execute security scanning commands on remote worker agents. Use when you need to run CLI tools like nmap, subfinder, httpx, nuclei, or any shell command on worker nodes.
Perform deep analysis of CVEs and security vulnerabilities including CVSS scoring, affected versions, exploit maturity, and remediation steps. Use when the user needs detailed vulnerability intelligence.
Perform web research using CVE databases, security advisories, and threat intelligence sources. Use when the user asks about CVEs, security news, vulnerabilities, patch releases, or any external security information not available in the workspace.
Workflow for committing code with comprehensive validation from linting to deployment
Workflow for API development and modification with strict checks from design to deployment
Strict bug fix workflow from root cause analysis to deployment and regression testing
| name | bug-report |
| description | Workflow for creating and submitting bug reports to GitHub |
Use this when you need to create a high-quality, reproducible bug report and submit it as a GitHub issue. The final report must be written in English.
Before drafting, collect:
core-api, worker, or browser consolecore-api, console, worker, or infraUse .github/ISSUE_TEMPLATE/bug-report.yml with:
[Bug]: followed by concise summaryPresent the draft to the user and ask for confirmation before submitting.
gh issue create --title "[Bug]: Short description" --body "$(cat <<'EOF'
## What happened?
...
## Affected Component
...
EOF
)"
Confirm the issue was created successfully. Ensure no sensitive data (secrets, keys) were included in logs.