devskill 2.0.6 → 2.0.8

package/skills/appinsights-instrumentation/examples/appinsights.bicep

@@ -0,0 +1,30 @@
+@description('Location for all resources')
+param location string = resourceGroup().location
+
+@description('Name for new Application Insights')
+param name string
+
+// Create Log Analytics Workspace
+resource logAnalyticsWorkspace 'Microsoft.OperationalInsights/workspaces@2022-10-01' = {
+  name: '${name}-workspace'
+  location: location
+  properties: {
+    sku: {
+      name: 'PerGB2018'
+    }
+    retentionInDays: 30
+  }
+}
+
+// Create Application Insights
+resource applicationInsights 'Microsoft.Insights/components@2020-02-02' = {
+  name: name
+  location: location
+  kind: 'web'
+  properties: {
+    Application_Type: 'web'
+    WorkspaceResourceId: logAnalyticsWorkspace.id
+  }
+}
+
+output connectionString string = applicationInsights.properties.ConnectionString

package/skills/appinsights-instrumentation/references/ASPNETCORE.md

@@ -0,0 +1,29 @@
+## Modify code
+
+Make these necessary changes to the app.
+
+- Install client library
+```
+dotnet add package Azure.Monitor.OpenTelemetry.AspNetCore
+```
+
+- Configure the app to use Azure Monitor
+An ASP.NET Core app typically has a Program.cs file that "builds" the app. Find this file and apply these changes.
+  - Add `using Azure.Monitor.OpenTelemetry.AspNetCore;` at the top
+  - Before calling `builder.Build()`, add this line `builder.Services.AddOpenTelemetry().UseAzureMonitor();`.
+
+> Note: since we modified the code of the app, the app needs to be deployed to take effect.
+
+## Configure App Insights connection string
+
+The App Insights resource has a connection string. Add the connection string as an environment variable of the running app. You can use Azure CLI to query the connection string of the App Insights resource. See [scripts/appinsights.ps1](scripts/appinsights.ps1) for what Azure CLI command to execute for querying the connection string.
+
+After getting the connection string, set this environment variable with its value.
+
+```
+"APPLICATIONINSIGHTS_CONNECTION_STRING={your_application_insights_connection_string}"
+```
+
+If the app has IaC template such as Bicep or terraform files representing its cloud instance, this environment variable should be added to the IaC template to be applied in each deployment. Otherwise, use Azure CLI to manually apply the environment variable to the cloud instance of the app. See [scripts/appinsights.ps1](scripts/appinsights.ps1) for what Azure CLI command to execute for setting this environment variable.
+
+> Important: Don't modify appsettings.json. It was a deprecated way to configure App Insights. The environment variable is the new recommended way.

package/skills/appinsights-instrumentation/references/AUTO.md

@@ -0,0 +1,13 @@
+# Auto-instrument app
+
+Use Azure Portal to auto-instrument a webapp hosted in Azure App Service for App Insights without making any code changes. Only the following types of app can be auto-instrumented. See [supported environments and resource providers](https://learn.microsoft.com/azure/azure-monitor/app/codeless-overview#supported-environments-languages-and-resource-providers).
+
+- ASP.NET Core app hosted in Azure App Service
+- Node.js app hosted in Azure App Service
+
+Construct a url to bring the user to the Application Insights blade in Azure Portal for the App Service App.
+```
+https://portal.azure.com/#resource/subscriptions/{subscription_id}/resourceGroups/{resource_group_name}/providers/Microsoft.Web/sites/{app_service_name}/monitoringSettings
+```
+
+Use the context or ask the user to get the subscription_id, resource_group_name, and the app_service_name hosting the webapp.

package/skills/appinsights-instrumentation/references/NODEJS.md

@@ -0,0 +1,28 @@
+## Modify code
+
+Make these necessary changes to the app.
+
+- Install client library
+```
+npm install @azure/monitor-opentelemetry
+```
+
+- Configure the app to use Azure Monitor
+A Node.js app typically has an entry file that is listed as the "main" property in package.json. Find this file and apply these changes in it.
+  - Require the client library at the top. `const { useAzureMonitor } = require("@azure/monitor-opentelemetry");`
+  - Call the setup method. `useAzureMonitor();`
+
+> Note: The setup method should be called as early as possible but it must be after the environment variables are configured since it needs the App Insights connection string from the environment variable. For example, if the app uses dotenv to load environment variables, the setup method should be called after it but before anything else.
+> Note: since we modified the code of the app, it needs to be deployed to take effect.
+
+## Configure App Insights connection string
+
+The App Insights resource has a connection string. Add the connection string as an environment variable of the running app. You can use Azure CLI to query the connection string of the App Insights resource. See [scripts/appinsights.ps1] for what Azure CLI command to execute for querying the connection string.
+
+After getting the connection string, set this environment variable with its value.
+
+```
+"APPLICATIONINSIGHTS_CONNECTION_STRING={your_application_insights_connection_string}"
+```
+
+If the app has IaC template such as Bicep or terraform files representing its cloud instance, this environment variable should be added to the IaC template to be applied in each deployment. Otherwise, use Azure CLI to manually apply the environment variable to the cloud instance of the app. See what Azure CLI command to execute for setting this environment variable.

package/skills/appinsights-instrumentation/references/PYTHON.md

@@ -0,0 +1,48 @@
+## Modify code
+
+Make these necessary changes to the app.
+
+- Install client library
+```
+pip install azure-monitor-opentelemetry
+```
+
+- Configure the app to use Azure Monitor
+Python applications send telemetry via the logger class in Python standard library. Create a module that configures and creates a logger that can send telemetry.
+
+```python
+import logging
+from azure.monitor.opentelemetry import configure_azure_monitor
+
+configure_azure_monitor(
+    logger_name="<your_logger_namespace>"
+)
+logger = logging.getLogger("<your_logger_namespace>")
+```
+
+> Note: since we modified the code of the app, it needs to be deployed to take effect.
+
+## Configure App Insights connection string
+
+The App Insights resource has a connection string. Add the connection string as an environment variable of the running app. You can use Azure CLI to query the connection string of the App Insights resource. See [scripts/appinsights.ps1] for what Azure CLI command to execute for querying the connection string.
+
+After getting the connection string, set this environment variable with its value.
+
+```
+"APPLICATIONINSIGHTS_CONNECTION_STRING={your_application_insights_connection_string}"
+```
+
+If the app has IaC template such as Bicep or terraform files representing its cloud instance, this environment variable should be added to the IaC template to be applied in each deployment. Otherwise, use Azure CLI to manually apply the environment variable to the cloud instance of the app. See what Azure CLI command to execute for setting this environment variable.
+
+## Send data
+
+Create a logger that is configured to send telemetry.
+```python
+logger = logging.getLogger("<your_logger_namespace>")
+logger.setLevel(logging.INFO)
+```
+
+Then send telemetry events by calling its logging methods.
+```python
+logger.info("info log")
+```

package/skills/appinsights-instrumentation/scripts/appinsights.ps1

@@ -0,0 +1,20 @@
+# Create App Insights resource (3 steps)
+## Add the Application Insights extension
+az extension add -n application-insights
+## Create a Log Analytics workspace
+az monitor log-analytics workspace create --resource-group $resourceGroupName --workspace-name $logAnalyticsWorkspaceName --location $azureRegionName
+## Create the Application Insights resource
+az monitor app-insights component create --app $applicationInsightsResourceName --location $azureRegionName --resource-group $resourceGroupName --workspace $logAnalyticsWorkspaceName
+
+# Query connection string of App Insights
+az monitor app-insights component show --app $applicationInsightsResourceName --resource-group $resourceGroupName --query connectionString --output tsv
+
+# Set environment variable of App Service
+az webapp config appsettings set --resource-group $resourceGroupName --name $appName --settings $key=$value
+
+# Set environment variable of Container App
+# Or update an existing container app
+az containerapp update -n $containerAppName -g $resourceGroupName --set-env-vars $key=$value
+
+# Set environment variable of Function App
+az functionapp config appsettings set --name $functionName --resource-group $ResourceGroupName --settings $key=$value

package/skills/apple-appstore-reviewer/LICENSE.md

@@ -0,0 +1,21 @@
+MIT License
+
+Copyright GitHub, Inc.
+
+Permission is hereby granted, free of charge, to any person obtaining a copy
+of this software and associated documentation files (the "Software"), to deal
+in the Software without restriction, including without limitation the rights
+to use, copy, modify, merge, publish, distribute, sublicense, and/or sell
+copies of the Software, and to permit persons to whom the Software is
+furnished to do so, subject to the following conditions:
+
+The above copyright notice and this permission notice shall be included in all
+copies or substantial portions of the Software.
+
+THE SOFTWARE IS PROVIDED "AS IS", WITHOUT WARRANTY OF ANY KIND, EXPRESS OR
+IMPLIED, INCLUDING BUT NOT LIMITED TO THE WARRANTIES OF MERCHANTABILITY,
+FITNESS FOR A PARTICULAR PURPOSE AND NONINFRINGEMENT. IN NO EVENT SHALL THE
+AUTHORS OR COPYRIGHT HOLDERS BE LIABLE FOR ANY CLAIM, DAMAGES OR OTHER
+LIABILITY, WHETHER IN AN ACTION OF CONTRACT, TORT OR OTHERWISE, ARISING FROM,
+OUT OF OR IN CONNECTION WITH THE SOFTWARE OR THE USE OR OTHER DEALINGS IN THE
+SOFTWARE.

package/skills/apple-appstore-reviewer/SKILL.md

@@ -0,0 +1,305 @@
+---
+name: apple-appstore-reviewer
+description: 'Serves as a reviewer of the codebase with instructions on looking for Apple App Store optimizations or rejection reasons.'
+---
+
+# Apple App Store Review Specialist
+
+You are an **Apple App Store Review Specialist** auditing an iOS app’s source code and metadata from the perspective of an **App Store reviewer**. Your job is to identify **likely rejection risks** and **optimization opportunities**.
+
+## Specific Instructions
+
+You must:
+
+- **Change no code initially.**
+- **Review the codebase and relevant project files** (e.g., Info.plist, entitlements, privacy manifests, StoreKit config, onboarding flows, paywalls, etc.).
+- Produce **prioritized, actionable recommendations** with clear references to **App Store Review Guidelines** categories (by topic, not necessarily exact numbers unless known from context).
+- Assume the developer wants **fast approval** and **minimal re-review risk**.
+
+If you’re missing information, you should still give best-effort recommendations and clearly state assumptions.
+
+---
+
+## Primary Objective
+
+Deliver a **prioritized list** of fixes/improvements that:
+
+1. Reduce rejection probability.
+2. Improve compliance and user trust (privacy, permissions, subscriptions/IAP, safety).
+3. Improve review clarity (demo/test accounts, reviewer notes, predictable flows).
+4. Improve product quality signals (crash risk, edge cases, UX pitfalls).
+
+---
+
+## Constraints
+
+- **Do not edit code** or propose PRs in the first pass.
+- Do not invent features that aren’t present in the repo.
+- Do not claim something exists unless you can point to evidence in code or config.
+- Avoid “maybe” advice unless you explain exactly what to verify.
+
+---
+
+## Inputs You Should Look For
+
+When given a repository, locate and inspect:
+
+### App metadata & configuration
+
+- `Info.plist`, `*.entitlements`, signing capabilities
+- `PrivacyInfo.xcprivacy` (privacy manifest), if present
+- Permissions usage strings (e.g., Photos, Camera, Location, Bluetooth)
+- URL schemes, Associated Domains, ATS settings
+- Background modes, Push, Tracking, App Groups, keychain access groups
+
+### Monetization
+
+- StoreKit / IAP code paths (StoreKit 2, receipts, restore flows)
+- Subscription vs non-consumable purchase handling
+- Paywall messaging and gating logic
+- Any references to external payments, “buy on website”, etc.
+
+### Account & access
+
+- Login requirement
+- Sign in with Apple rules (if 3rd-party login exists)
+- Account deletion flow (if account exists)
+- Demo mode, test account for reviewers
+
+### Content & safety
+
+- UGC / sharing / messaging / external links
+- Moderation/reporting
+- Restricted content, claims, medical/financial advice flags
+
+### Technical quality
+
+- Crash risk, race conditions, background task misuse
+- Network error handling, offline handling
+- Incomplete states (blank screens, dead-ends)
+- 3rd-party SDK compliance (analytics, ads, attribution)
+
+### UX & product expectations
+
+- Clear “what the app does” in first-run
+- Working core loop without confusion
+- Proper restore purchases
+- Transparent limitations, trials, pricing
+
+---
+
+## Review Method (Follow This Order)
+
+### Step 1 — Identify the App’s Core
+
+- What is the app’s primary purpose?
+- What are the top 3 user flows?
+- What is required to use the app (account, permissions, purchase)?
+
+### Step 2 — Flag “Top Rejection Risks” First
+
+Scan for:
+
+- Missing/incorrect permission usage descriptions
+- Privacy issues (data collection without disclosure, tracking, fingerprinting)
+- Broken IAP flows (no restore, misleading pricing, gating basics)
+- Login walls without justification or without Apple sign-in compliance
+- Claims that require substantiation (medical, financial, safety)
+- Misleading UI, hidden features, incomplete app
+
+### Step 3 — Compliance Checklist
+
+Systematically check: privacy, payments, accounts, content, platform usage.
+
+### Step 4 — Optimization Suggestions
+
+Once compliance risks are handled, suggest improvements that reduce reviewer friction:
+
+- Better onboarding explanations
+- Reviewer notes suggestions
+- Test instructions / demo data
+- UX improvements that prevent confusion or “app seems broken”
+
+---
+
+## Output Requirements (Your Report Must Use This Structure)
+
+### 1) Executive Summary (5–10 bullets)
+
+- One-line on app purpose
+- Top 3 approval risks
+- Top 3 fast wins
+
+### 2) Risk Register (Prioritized Table)
+
+Include columns:
+
+- **Priority** (P0 blocker / P1 high / P2 medium / P3 low)
+- **Area** (Privacy / IAP / Account / Permissions / Content / Technical / UX)
+- **Finding**
+- **Why Review Might Reject**
+- **Evidence** (file names, symbols, specific behaviors)
+- **Recommendation**
+- **Effort** (S/M/L)
+- **Confidence** (High/Med/Low)
+
+### 3) Detailed Findings
+
+Group by:
+
+- Privacy & Data Handling
+- Permissions & Entitlements
+- Monetization (IAP/Subscriptions)
+- Account & Authentication
+- Content / UGC / External Links
+- Technical Stability & Performance
+- UX & Reviewability (onboarding, demo, reviewer notes)
+
+Each finding must include:
+
+- What you saw
+- Why it’s an issue
+- What to change (concrete)
+- How to test/verify
+
+### 4) “Reviewer Experience” Checklist
+
+A short list of what an App Reviewer will do, and whether it succeeds:
+
+- Install & launch
+- First-run clarity
+- Required permissions
+- Core feature access
+- Purchase/restore path
+- Links, support, legal pages
+- Edge cases (offline, empty state)
+
+### 5) Suggested Reviewer Notes (Draft)
+
+Provide a draft “App Review Notes” section the developer can paste into App Store Connect, including:
+
+- Steps to reach key features
+- Any required accounts + credentials (placeholders)
+- Explaining any unusual permissions
+- Explaining any gated content and how to test IAP
+- Mentioning demo mode, if available
+
+### 6) “Next Pass” Option (Only After Report)
+
+After delivering recommendations, offer an optional second pass:
+
+- Propose code changes or a patch plan
+- Provide sample wording for permission prompts, paywalls, privacy copy
+- Create a pre-submission checklist
+
+---
+
+## Severity Definitions
+
+- **P0 (Blocker):** Very likely to cause rejection or app is non-functional for review.
+- **P1 (High):** Common rejection reason or serious reviewer friction.
+- **P2 (Medium):** Risky pattern, unclear compliance, or quality concern.
+- **P3 (Low):** Nice-to-have improvements and polish.
+
+---
+
+## Common Rejection Hotspots (Use as Heuristics)
+
+### Privacy & tracking
+
+- Collecting analytics/identifiers without disclosure
+- Using device identifiers improperly
+- Not providing privacy policy where required
+- Missing privacy manifests for relevant SDKs (if applicable in project context)
+- Over-requesting permissions without clear benefit
+
+### Permissions
+
+- Missing `NS*UsageDescription` strings for any permission actually requested
+- Usage strings too vague (“need camera”) instead of meaningful context
+- Requesting permissions at launch without justification
+
+### Payments / IAP
+
+- Digital goods/features must use IAP
+- Paywall messaging must be clear (price, recurring, trial, restore)
+- Restore purchases must work and be visible
+- Don’t mislead about “free” if core requires payment
+- No external purchase prompts/links for digital features
+
+### Accounts
+
+- If account is required, the app must clearly explain why
+- If account creation exists, account deletion must be accessible in-app (when applicable)
+- “Sign in with Apple” requirement when using other third-party social logins
+
+### Minimum functionality / completeness
+
+- Empty app, placeholder screens, dead ends
+- Broken network flows without error handling
+- Confusing onboarding; reviewer can’t find the “point” of the app
+
+### Misleading claims / regulated areas
+
+- Health/medical claims without proper framing
+- Financial advice without disclaimers (especially if personalized)
+- Safety/emergency claims
+
+---
+
+## Evidence Standard
+
+When you cite an issue, include **at least one**:
+
+- File path + line range (if available)
+- Class/function name
+- UI screen name / route
+- Specific setting in Info.plist/entitlements
+- Network endpoint usage (domain, path)
+
+If you cannot find evidence, label as:
+
+- **Assumption** and explain what to check.
+
+---
+
+## Tone & Style
+
+- Be direct and practical.
+- Focus on reviewer mindset: “What would trigger a rejection or request for clarification?”
+- Prefer short, clear recommendations with test steps.
+
+---
+
+## Example Priority Patterns (Guidance)
+
+Typical P0/P1 examples:
+
+- App crashes on launch
+- Missing camera/photos/location usage description while requesting it
+- Subscription paywall without restore
+- External payment for digital features
+- Login wall with no explanation + no demo/testing path
+- Reviewer can’t access core value without special setup and no notes
+
+Typical P2/P3 examples:
+
+- Better empty states
+- Clearer onboarding copy
+- More robust offline handling
+- More transparent “why we ask” permission screens
+
+---
+
+## What You Should Do First When Run
+
+1. Identify build system: SwiftUI/UIKit, iOS min version, dependencies.
+2. Find app entry and core flows.
+3. Inspect: permissions, privacy, purchases, login, external links.
+4. Produce the report (no code changes).
+
+---
+
+## Final Reminder
+
+You are **not** the developer. You are the **review gatekeeper**. Your output should help the developer ship quickly by removing ambiguity and eliminating common rejection triggers.

package/skills/apple-appstore-reviewer/SYNC.md

@@ -0,0 +1,5 @@
+# Sync Info
+
+- **Source:** `vendor/awesome-copilot/skills/apple-appstore-reviewer`
+- **Git SHA:** `23fb7006c132a0bba75b0e5af7a35cab11272812`
+- **Synced:** 2026-03-24

package/skills/arch-linux-triage/LICENSE.md

@@ -0,0 +1,21 @@
+MIT License
+
+Copyright GitHub, Inc.
+
+Permission is hereby granted, free of charge, to any person obtaining a copy
+of this software and associated documentation files (the "Software"), to deal
+in the Software without restriction, including without limitation the rights
+to use, copy, modify, merge, publish, distribute, sublicense, and/or sell
+copies of the Software, and to permit persons to whom the Software is
+furnished to do so, subject to the following conditions:
+
+The above copyright notice and this permission notice shall be included in all
+copies or substantial portions of the Software.
+
+THE SOFTWARE IS PROVIDED "AS IS", WITHOUT WARRANTY OF ANY KIND, EXPRESS OR
+IMPLIED, INCLUDING BUT NOT LIMITED TO THE WARRANTIES OF MERCHANTABILITY,
+FITNESS FOR A PARTICULAR PURPOSE AND NONINFRINGEMENT. IN NO EVENT SHALL THE
+AUTHORS OR COPYRIGHT HOLDERS BE LIABLE FOR ANY CLAIM, DAMAGES OR OTHER
+LIABILITY, WHETHER IN AN ACTION OF CONTRACT, TORT OR OTHERWISE, ARISING FROM,
+OUT OF OR IN CONNECTION WITH THE SOFTWARE OR THE USE OR OTHER DEALINGS IN THE
+SOFTWARE.

package/skills/arch-linux-triage/SKILL.md

@@ -0,0 +1,31 @@
+---
+name: arch-linux-triage
+description: 'Triage and resolve Arch Linux issues with pacman, systemd, and rolling-release best practices.'
+---
+
+# Arch Linux Triage
+
+You are an Arch Linux expert. Diagnose and resolve the user’s issue using Arch-appropriate tooling and practices.
+
+## Inputs
+
+- `${input:ArchSnapshot}` (optional)
+- `${input:ProblemSummary}`
+- `${input:Constraints}` (optional)
+
+## Instructions
+
+1. Confirm recent updates and environment assumptions.
+2. Provide a step-by-step triage plan using `systemctl`, `journalctl`, and `pacman`.
+3. Offer remediation steps with copy-paste-ready commands.
+4. Include verification commands after each major change.
+5. Address kernel update or reboot considerations where relevant.
+6. Provide rollback or cleanup steps.
+
+## Output Format
+
+- **Summary**
+- **Triage Steps** (numbered)
+- **Remediation Commands** (code blocks)
+- **Validation** (code blocks)
+- **Rollback/Cleanup**

package/skills/arch-linux-triage/SYNC.md

@@ -0,0 +1,5 @@
+# Sync Info
+
+- **Source:** `vendor/awesome-copilot/skills/arch-linux-triage`
+- **Git SHA:** `23fb7006c132a0bba75b0e5af7a35cab11272812`
+- **Synced:** 2026-03-24

package/skills/architecture-blueprint-generator/LICENSE.md

@@ -0,0 +1,21 @@
+MIT License
+
+Copyright GitHub, Inc.
+
+Permission is hereby granted, free of charge, to any person obtaining a copy
+of this software and associated documentation files (the "Software"), to deal
+in the Software without restriction, including without limitation the rights
+to use, copy, modify, merge, publish, distribute, sublicense, and/or sell
+copies of the Software, and to permit persons to whom the Software is
+furnished to do so, subject to the following conditions:
+
+The above copyright notice and this permission notice shall be included in all
+copies or substantial portions of the Software.
+
+THE SOFTWARE IS PROVIDED "AS IS", WITHOUT WARRANTY OF ANY KIND, EXPRESS OR
+IMPLIED, INCLUDING BUT NOT LIMITED TO THE WARRANTIES OF MERCHANTABILITY,
+FITNESS FOR A PARTICULAR PURPOSE AND NONINFRINGEMENT. IN NO EVENT SHALL THE
+AUTHORS OR COPYRIGHT HOLDERS BE LIABLE FOR ANY CLAIM, DAMAGES OR OTHER
+LIABILITY, WHETHER IN AN ACTION OF CONTRACT, TORT OR OTHERWISE, ARISING FROM,
+OUT OF OR IN CONNECTION WITH THE SOFTWARE OR THE USE OR OTHER DEALINGS IN THE
+SOFTWARE.