Move AI agent config to shared location for Claude Code and GitHub Copilot

.github/skills/issue-fix/SKILL.md → .claude/skills/issue-fix/SKILL.md

@@ -462,8 +462,8 @@ If the fix discovered that triage or repro got something wrong, record it:
 
 ```bash
 # Try pwsh first, fall back to python3
-pwsh .github/skills/issue-fix/scripts/validate-fix.ps1 /tmp/skiasharp/fix/{timestamp}/{number}.json \
-  || python3 .github/skills/issue-fix/scripts/validate-fix.py /tmp/skiasharp/fix/{timestamp}/{number}.json
+pwsh .claude/skills/issue-fix/scripts/validate-fix.ps1 /tmp/skiasharp/fix/{timestamp}/{number}.json \
+  || python3 .claude/skills/issue-fix/scripts/validate-fix.py /tmp/skiasharp/fix/{timestamp}/{number}.json
 ```
 
 > **⚠️ NEVER use hand-rolled validation.** Always use the scripts above.
@@ -473,7 +473,7 @@ pwsh .github/skills/issue-fix/scripts/validate-fix.ps1 /tmp/skiasharp/fix/{times
 Copy the validated JSON to `output/ai/` for collection.
 
 ```bash
-pwsh .github/skills/issue-fix/scripts/persist-fix.ps1 /tmp/skiasharp/fix/{timestamp}/{number}.json
+pwsh .claude/skills/issue-fix/scripts/persist-fix.ps1 /tmp/skiasharp/fix/{timestamp}/{number}.json
 ```
 
 This copies the JSON to `output/ai/` mirroring the data-cache structure.

.github/skills/issue-repro/SKILL.md → .claude/skills/issue-repro/SKILL.md

@@ -297,8 +297,8 @@ Use the same action types as triage. Common repro actions:
 
 ```bash
 # Try pwsh first, fall back to python3
-pwsh .github/skills/issue-repro/scripts/validate-repro.ps1 /tmp/skiasharp/repro/{timestamp}/{number}.json \
-  || python3 .github/skills/issue-repro/scripts/validate-repro.py /tmp/skiasharp/repro/{timestamp}/{number}.json
+pwsh .claude/skills/issue-repro/scripts/validate-repro.ps1 /tmp/skiasharp/repro/{timestamp}/{number}.json \
+  || python3 .claude/skills/issue-repro/scripts/validate-repro.py /tmp/skiasharp/repro/{timestamp}/{number}.json
 ```
 
 - **Exit 0** = ✅ valid → proceed to Phase 6
@@ -317,7 +317,7 @@ pwsh .github/skills/issue-repro/scripts/validate-repro.ps1 /tmp/skiasharp/repro/
 Copy the validated JSON to `output/ai/` for collection.
 
 ```bash
-pwsh .github/skills/issue-repro/scripts/persist-repro.ps1 /tmp/skiasharp/repro/{timestamp}/{number}.json
+pwsh .claude/skills/issue-repro/scripts/persist-repro.ps1 /tmp/skiasharp/repro/{timestamp}/{number}.json
 ```
 
 This copies the JSON to `output/ai/` mirroring the data-cache structure.

.github/skills/issue-triage/SKILL.md → .claude/skills/issue-triage/SKILL.md

@@ -84,7 +84,7 @@ If using cached JSON:
 
 ```bash
 mkdir -p /tmp/skiasharp/triage/{timestamp}
-pwsh .github/skills/issue-triage/scripts/issue-to-markdown.ps1 $CACHE/github/items/{number}.json > /tmp/skiasharp/triage/{timestamp}/{number}.md
+pwsh .claude/skills/issue-triage/scripts/issue-to-markdown.ps1 $CACHE/github/items/{number}.json > /tmp/skiasharp/triage/{timestamp}/{number}.md
 ```
 
 If fetched via API, work directly from the `gh` output (skip the script).
@@ -208,8 +208,8 @@ If any proposal `description`, `codeSnippet`, or `add-comment` `comment` contain
 
 ```bash
 # Try pwsh first, fall back to python3
-pwsh .github/skills/issue-triage/scripts/validate-triage.ps1 /tmp/skiasharp/triage/{timestamp}/{number}.json \
-  || python3 .github/skills/issue-triage/scripts/validate-triage.py /tmp/skiasharp/triage/{timestamp}/{number}.json
+pwsh .claude/skills/issue-triage/scripts/validate-triage.ps1 /tmp/skiasharp/triage/{timestamp}/{number}.json \
+  || python3 .claude/skills/issue-triage/scripts/validate-triage.py /tmp/skiasharp/triage/{timestamp}/{number}.json
 ```
 
 - **Exit 0** = ✅ valid → proceed to Phase 5
@@ -230,7 +230,7 @@ pwsh .github/skills/issue-triage/scripts/validate-triage.ps1 /tmp/skiasharp/tria
 Copy the validated JSON to `output/ai/` for collection.
 
 ```bash
-pwsh .github/skills/issue-triage/scripts/persist-triage.ps1 /tmp/skiasharp/triage/{timestamp}/{number}.json
+pwsh .claude/skills/issue-triage/scripts/persist-triage.ps1 /tmp/skiasharp/triage/{timestamp}/{number}.json
 ```
 
 This copies the JSON to `output/ai/` mirroring the data-cache structure.

.github/skills/issue-triage/references/workaround-search.md → .claude/skills/issue-triage/references/workaround-search.md

@@ -117,7 +117,7 @@ gh issue view {N} --repo mono/SkiaSharp --json comments \
 
 ```bash
 grep -n "DllNotFound\|NoDependencies\|container\|Docker\|Alpine\|ARM64" documentation/dev/packages.md
-grep -n "KEYWORD" .github/skills/issue-triage/references/skia-patterns.md
+grep -n "KEYWORD" .claude/skills/issue-triage/references/skia-patterns.md
 ```
 
 **Common instant workarounds:**

.github/skills/release-notes-audit/SKILL.md → .claude/skills/release-notes-audit/SKILL.md

@@ -142,7 +142,7 @@ Save as `output/ai/release-notes-audit-{date}.json` in the repo.
 > 🛑 **MANDATORY:** Always generate the HTML report.
 
 ```bash
-python3 .github/skills/release-notes-audit/scripts/render-release-notes-audit.py \
+python3 .claude/skills/release-notes-audit/scripts/render-release-notes-audit.py \
   output/ai/release-notes-audit-{date}.json
 ```
 

.github/skills/review-skia-update/SKILL.md → .claude/skills/review-skia-update/SKILL.md

@@ -37,7 +37,7 @@ A single script handles all mechanical work: fetching PR metadata, checking out
 running the generator, checking source integrity, auditing DEPS, and analyzing companion PR files.
 
 ```bash
-python3 .github/skills/review-skia-update/scripts/run_review.py \
+python3 .claude/skills/review-skia-update/scripts/run_review.py \
     --skia-pr {skia_pr_number} \
     --skiasharp-pr {skiasharp_pr_number}
 ```
@@ -99,8 +99,8 @@ The working tree is checked out to the companion PR, so you can read files direc
 
 ```bash
 # Try pwsh first, fall back to python3
-pwsh .github/skills/review-skia-update/scripts/validate-skia-review.ps1 {output_dir}/{pr_number}.json \
-  || python3 .github/skills/review-skia-update/scripts/validate-skia-review.py {output_dir}/{pr_number}.json
+pwsh .claude/skills/review-skia-update/scripts/validate-skia-review.ps1 {output_dir}/{pr_number}.json \
+  || python3 .claude/skills/review-skia-update/scripts/validate-skia-review.py {output_dir}/{pr_number}.json
 ```
 
 - **Exit 0** = ✅ valid → proceed to persist
@@ -117,7 +117,7 @@ pwsh .github/skills/review-skia-update/scripts/validate-skia-review.ps1 {output_
 Copy the validated JSON to `output/ai/` for collection.
 
 ```bash
-pwsh .github/skills/review-skia-update/scripts/persist-skia-review.ps1 {output_dir}/{pr_number}.json
+pwsh .claude/skills/review-skia-update/scripts/persist-skia-review.ps1 {output_dir}/{pr_number}.json
 ```
 
 This copies the JSON to `output/ai/repos/mono-skia/ai-review/` and generates an HTML report

.github/skills/security-audit/SKILL.md → .claude/skills/security-audit/SKILL.md

@@ -294,7 +294,7 @@ Save as `output/ai/security-audit-{date}.json` in the repo (same pattern as othe
 > 🛑 **MANDATORY:** Always generate the HTML report. The human needs a readable dashboard.
 
 ```bash
-python3 .github/skills/security-audit/scripts/render-security-audit.py \
+python3 .claude/skills/security-audit/scripts/render-security-audit.py \
   output/ai/security-audit-{date}.json
 ```
 

.github/skills/update-skia/SKILL.md → .claude/skills/update-skia/SKILL.md

@@ -256,7 +256,7 @@ must be updated when the underlying C++ APIs change.
 
 In the **SkiaSharp parent repo**, run:
 ```bash
-pwsh .github/skills/update-skia/scripts/update-versions.ps1 -Current {CURRENT} -Target {TARGET}
+pwsh .claude/skills/update-skia/scripts/update-versions.ps1 -Current {CURRENT} -Target {TARGET}
 ```
 
 The script handles all of these (so you don't have to do them manually):
@@ -276,7 +276,7 @@ The script handles all of these (so you don't have to do them manually):
 > and lists any new functions that may need C# wrappers.
 
 ```bash
-pwsh .github/skills/update-skia/scripts/regenerate-bindings.ps1
+pwsh .claude/skills/update-skia/scripts/regenerate-bindings.ps1
 ```
 
 The script handles all of these (so you don't forget any):

.github/skills/update-skia/scripts/regenerate-bindings.ps1 → .claude/skills/update-skia/scripts/regenerate-bindings.ps1

@@ -11,7 +11,7 @@
     4. Lists any NEW functions that may need C# wrappers
 
 .EXAMPLE
-    pwsh .github/skills/update-skia/scripts/regenerate-bindings.ps1
+    pwsh .claude/skills/update-skia/scripts/regenerate-bindings.ps1
 #>
 
 $ErrorActionPreference = 'Stop'

.github/skills/update-skia/scripts/update-versions.ps1 → .claude/skills/update-skia/scripts/update-versions.ps1

@@ -19,7 +19,7 @@
     The target Skia milestone number (e.g., 120)
 
 .EXAMPLE
-    pwsh .github/skills/update-skia/scripts/update-versions.ps1 -Current 119 -Target 120
+    pwsh .claude/skills/update-skia/scripts/update-versions.ps1 -Current 119 -Target 120
 #>
 
 param(

.github/skills/validate-samples/SKILL.md → .claude/skills/validate-samples/SKILL.md

@@ -66,7 +66,7 @@ Run the detection script — it prints the preview label and build number
 extracted from the downloaded nupkg filenames:
 
 ```powershell
-pwsh .github/skills/validate-samples/scripts/detect-preview-version.ps1
+pwsh .claude/skills/validate-samples/scripts/detect-preview-version.ps1
 ```
 
 Output:

.github/skills/validate-samples/scripts/detect-preview-version.ps1 → .claude/skills/validate-samples/scripts/detect-preview-version.ps1

@@ -1,6 +1,6 @@
 # detect-preview-version.ps1
 # Detects the preview label and build number from downloaded nupkg files in output/nugets/
-# Usage: pwsh .github/skills/validate-samples/scripts/detect-preview-version.ps1
+# Usage: pwsh .claude/skills/validate-samples/scripts/detect-preview-version.ps1
 #   Prints: Preview label, Build number, Full suffix
 
 param(