菜单
Use when the user says "triage issues", "/triage", or "what should I work on next". Pulls open GitHub issues assigned to or authored by the user and groups them by priority, staleness, and required action.
用 Codex 或 Claude 帮你安装 复制这段 Prompt，粘贴到 Codex、Claude 或其他助手里，让它检查 Skill 页面并帮你完成安装。
基于 SOC 职业分类
Use when reviewing a backend HTTP / GraphQL handler for validation, authz, errors, performance, observability, and security, or "/backend-review". Produces a structured review with file:line citations.
Use when running a cloud security posture scan (CSPM) on AWS, Azure, or GCP using prowler, scout-suite, or checkov, or "/cloud-scan". Requires read-only credentials; produces CIS-benchmark-aligned findings with remediation.
Use when scanning a container image or Dockerfile for vulnerabilities, misconfigurations, and best-practice violations using trivy, dockle, or hadolint, or "/image-scan". Flags base-image CVEs, root user, missing healthchecks, and bloat.
Use when running an authorized non-intrusive DAST baseline scan (OWASP ZAP baseline, nuclei, nikto) against a web app or API endpoint you own, or "/dast". Requires explicit authorization; refuses unowned targets.
Use when handed a stack trace, error log, or "this is broken" with a paste of output, and asked to find the root cause across frontend, backend, or DB tiers, or "/debug-trace". Produces a hypothesis tree, the evidence supporting each branch, and the next diagnostic step.
Use when scanning a project's third-party dependencies for known CVEs across npm, pip, Go, Maven, Cargo, etc., or "/dep-scan". Runs trivy, npm audit, pip-audit, govulncheck, or osv-scanner and produces a prioritized fix list.
| name | triage-issues |
| description | Use when the user says "triage issues", "/triage", or "what should I work on next". Pulls open GitHub issues assigned to or authored by the user and groups them by priority, staleness, and required action. |
Pull candidates (repo-scoped unless user asks org-wide):
gh issue list --assignee @me --state open --limit 100 \
--json number,title,labels,updatedAt,url,repository
Enrich with last comment time if needed: gh issue view <n> --json comments.
Bucket into:
p0/bug/urgent, or assigned and updated in last 24h.p1, or touched in last 7 days.Produce output:
### Act today
- #123 <title> (<repo>) — <one-line why>
### This week
- ...
### Stale (>30d, consider closing)
- ...
### Waiting on you (needs reply)
- ...
Offer to open the top one in the browser with gh issue view <n> --web.