[pull] main from github:main

.github/aw/create-agentic-workflow.md

@@ -831,6 +831,7 @@ Based on the parsed requirements, determine:
 
 1. **Workflow ID**: Convert the workflow name to kebab-case (e.g., "Issue Classifier" → "issue-classifier")
 2. **Triggers**: Infer appropriate triggers from the description. **Always use `on:` as the YAML key** — never use `triggers:` (that is not a valid frontmatter key and will cause a compile error):
+   - **Security rule**: **Never suggest `pull_request_target` as a replacement for `pull_request`**. If a workflow should react to PR activity, keep `pull_request` unless the user explicitly requires a `pull_request_target`-only capability.
    - Issue automation → `on: issues: types: [opened, edited]` (add `workflow_dispatch:` manually if manual runs needed)
    - PR automation → `on: pull_request: types: [opened, synchronize]` (add `workflow_dispatch:` manually if manual runs needed)
    - PR automation scoped to specific files → add `paths:` under `pull_request:` to trigger only when matching files change (ideal for backend/QA scenarios such as DB migration review or API contract checks):

.github/aw/syntax.md

@@ -27,7 +27,7 @@ The YAML frontmatter supports these fields:
     - String format: `labels: "my-label"` (single label name)
     - Array format: `labels: [label-a, label-b]` (any matching label fires the workflow)
     - Unmatched label events show as Skipped (⊘) rather than Failed (❌)
-    - Use with `pull_request_target` triggers with `types: [labeled]` to respond only to specific labels
+    - Use with `pull_request` triggers with `types: [labeled]` to respond only to specific labels
   - **`skip-if-match:`** - Skip workflow execution when a GitHub search query returns results (string or object)
     - String format: `skip-if-match: "is:issue is:open label:bug"` (implies max=1)
     - Object format with threshold:
@@ -929,4 +929,3 @@ safe-outputs:
 - **Separation of Concerns**: Write operations are handled by dedicated jobs
 - **Permission Management**: Safe-outputs jobs automatically receive required permissions
 - **Audit Trail**: Clear separation between AI processing and GitHub API interactions
-

.github/aw/update-agentic-workflow.md

@@ -357,6 +357,7 @@ edit .github/workflows/<workflow-id>.md
 - Use `edit` tool to modify only the specific YAML fields
 - Preserve existing indentation and formatting
 - Don't rewrite sections that don't need changes
+- Never suggest replacing `pull_request` with `pull_request_target` unless the user explicitly asks for a `pull_request_target`-specific design
 - Recompilation REQUIRED after frontmatter changes
 
 **Example - Adding a Safe Output (Configuration Change)**:

.github/skills/agentic-workflows/SKILL.md

@@ -0,0 +1,12 @@
+---
+name: agentic-workflows
+description: Router skill for gh-aw workflow tasks. Load `.github/agents/agentic-workflows.agent.md` plus relevant prompts from `.github/aw/*.md`.
+---
+
+# Agentic Workflows Router
+
+Use this skill when a user asks to create, update, debug, or upgrade GitHub Agentic Workflows.
+
+1. Read `.github/agents/agentic-workflows.agent.md` (also referred to as `.github/actions/agentic-workflows.agent.md` in older notes).
+2. Select and read the matching prompt from `.github/aw/*.md`.
+3. Follow that prompt directly and keep responses concise.