菜单
Use when asked to inspect GitHub code-scanning alerts across the repositories defined in one selected profile.
用 Codex 或 Claude 帮你安装 复制这段 Prompt，粘贴到 Codex、Claude 或其他助手里，让它检查 Skill 页面并帮你完成安装。
基于 SOC 职业分类
| name | github-security-code-scanning-triage |
| description | Use when asked to inspect GitHub code-scanning alerts across the repositories defined in one selected profile. |
Use this skill when the task is to classify open code scanning alerts for one selected profile.
Read these files before changing anything:
../../docs/runtime-contract.md../../docs/operating-model.md../../docs/code-scanning-policy.mdprofile.yamlcode scanning alertsThis skill does not patch repositories.
code_scanning.active repository entries.code scanning alerts for each repository entry.skipped with reason code_scanning_disabled.skipped with reason no_analysis_found.target_id mapping from the profile. For repository-level workflow alerts under .github/workflows/**, a single root target at . may serve as the stable target.defaults.code_scanning.allowlisted_rules, record skipped with reason unsupported_rule.../../docs/code-scanning-policy.md.../../docs/operating-model.md.code_scanning_disabled from no_analysis_found.Return, per repository entry:
Use when asked to reduce GitHub security alerts across all active repositories in one selected profile.
Use when asked to remediate GitHub Dependabot alerts across the repositories defined in one selected profile.
Use when a remediation diff already exists and you need a policy decision for merged, opened_pr, blocked, skipped, or failed.
Use when you need a consistent run summary across remediation units, outcomes, and remaining blockers.
Use when you need to validate a selected profile, inspect the runtime contract, and map repository entries to local clone paths before any remediation work starts.
Use when asked to remediate allowlisted deterministic GitHub code-scanning alerts across the repositories defined in one selected profile.