Feature: Add a security patch skill, and companion tool for grabbing skill specific context

GEMINI.md

@@ -178,6 +178,7 @@ This is your internal knowledge base of vulnerabilities. When you need to do a s
 ### Newly Introduced Vulnerabilities
 For each identified vulnerability, provide the following:
 
+*   **ID:** A unique identifier for the vulnerability, eg. `VULN-001`.
 *   **Vulnerability:** A brief name for the issue (e.g., "Cross-Site Scripting," "Hardcoded API Key," "PII Leak in Logs", "PII Sent to 3P").
 *   **Vulnerability Type:** The category that this issue falls closest under (e.g., "Security", "Privacy")
 *   **Severity:** Critical, High, Medium, or Low.

commands/security/analyze.toml

@@ -74,6 +74,16 @@ For EVERY task, you MUST follow this procedure. This loop separates high-level s
     *   **Action:** If, after the review, no vulnerabilities remain, your final output **MUST** be the standard "clean report" message specified by the task prompt.
     *   **Action:** ONLY IF the user requested JSON output (e.g., via `--json` in context or natural language), call the `convert_report_to_json` tool. Inform the user that the JSON version of the report is available at .gemini_security/security_report.json.
     *   **Action:** After the final report is delivered and any requested JSON report is complete, remove ONLY the temporary files (`SECURITY_ANALYSIS_TODO.md` and `DRAFT_SECURITY_REPORT.md`, you must keep `security_report.json` if generated) from the `.gemini_security/` directory. Only remove these files and do not remove any other user files under any circumstances.
+    *   **Action:** Use the `ask_user` tool for the following TWO questions:
+        a. Ask which of the vulnerabilities (using their IDs) they would like to act on, if any:
+            1. All Vulnerabilities (Suggested)
+            2. VULN-001
+            3. VULN-002
+            4. ...
+            999. VULN-999
+        b. For the selected vulnerabilities, ask they would like to:
+            1. Generate a Proof of Concept(PoC) for the selected vulnerability(s)
+            2. Patch the vulnerability(s) directly
 
 
 ### Example of the Workflow in `SECURITY_ANALYSIS_TODO.md`