security-issue-importlisted
Install: claude install-skill apache/airflow-steward
<!-- Placeholder convention (see AGENTS.md#placeholder-convention-used-in-skill-files):
<project-config> → adopting project's `.apache-steward/` directory
<tracker> → value of `tracker_repo:` in <project-config>/project.md
(example: airflow-s/airflow-s for the Apache Airflow security team)
<upstream> → value of `upstream_repo:` in <project-config>/project.md
(example: apache/airflow)
Before running any bash command below, substitute these with the
concrete values from the adopting project's <project-config>/project.md. -->
# security-issue-import
This skill is the **on-ramp** of the security-issue handling process.
It converts an inbound `<security-list>` email thread into
an `<tracker>` tracking issue that follows the repo's issue
template, then drafts the receipt-of-confirmation reply to the reporter.
It never sends email. It never creates a tracker for a candidate the
user has explicitly rejected. It never assumes a report is valid —
the validity / invalid / CVE-worthy decision still happens later in
the discussion on the created tracker (Step 3 of
[`README.md`](../../../README.md)).
**Golden rule — propose, then default to import.** Every import this
skill performs is a *proposal* that lists the candidate emails, the
extracted fields, and the draft confirmation reply. The user's
default disposition for any `Report` or forwarder-relayed
candidate (the latter classified by the optional
[