devskill 2.0.7 → 2.0.8

package/skills/typespec-create-api-plugin/SKILL.md

@@ -0,0 +1,164 @@
+---
+name: typespec-create-api-plugin
+description: 'Generate a TypeSpec API plugin with REST operations, authentication, and Adaptive Cards for Microsoft 365 Copilot'
+---
+
+# Create TypeSpec API Plugin
+
+Create a complete TypeSpec API plugin for Microsoft 365 Copilot that integrates with external REST APIs.
+
+## Requirements
+
+Generate TypeSpec files with:
+
+### main.tsp - Agent Definition
+```typescript
+import "@typespec/http";
+import "@typespec/openapi3";
+import "@microsoft/typespec-m365-copilot";
+import "./actions.tsp";
+
+using TypeSpec.Http;
+using TypeSpec.M365.Copilot.Agents;
+using TypeSpec.M365.Copilot.Actions;
+
+@agent({
+  name: "[Agent Name]",
+  description: "[Description]"
+})
+@instructions("""
+  [Instructions for using the API operations]
+""")
+namespace [AgentName] {
+  // Reference operations from actions.tsp
+  op operation1 is [APINamespace].operationName;
+}
+```
+
+### actions.tsp - API Operations
+```typescript
+import "@typespec/http";
+import "@microsoft/typespec-m365-copilot";
+
+using TypeSpec.Http;
+using TypeSpec.M365.Copilot.Actions;
+
+@service
+@actions(#{
+    nameForHuman: "[API Display Name]",
+    descriptionForModel: "[Model description]",
+    descriptionForHuman: "[User description]"
+})
+@server("[API_BASE_URL]", "[API Name]")
+@useAuth([AuthType]) // Optional
+namespace [APINamespace] {
+  
+  @route("[/path]")
+  @get
+  @action
+  op operationName(
+    @path param1: string,
+    @query param2?: string
+  ): ResponseModel;
+
+  model ResponseModel {
+    // Response structure
+  }
+}
+```
+
+## Authentication Options
+
+Choose based on API requirements:
+
+1. **No Authentication** (Public APIs)
+   ```typescript
+   // No @useAuth decorator needed
+   ```
+
+2. **API Key**
+   ```typescript
+   @useAuth(ApiKeyAuth<ApiKeyLocation.header, "X-API-Key">)
+   ```
+
+3. **OAuth2**
+   ```typescript
+   @useAuth(OAuth2Auth<[{
+     type: OAuth2FlowType.authorizationCode;
+     authorizationUrl: "https://oauth.example.com/authorize";
+     tokenUrl: "https://oauth.example.com/token";
+     refreshUrl: "https://oauth.example.com/token";
+     scopes: ["read", "write"];
+   }]>)
+   ```
+
+4. **Registered Auth Reference**
+   ```typescript
+   @useAuth(Auth)
+   
+   @authReferenceId("registration-id-here")
+   model Auth is ApiKeyAuth<ApiKeyLocation.header, "X-API-Key">
+   ```
+
+## Function Capabilities
+
+### Confirmation Dialog
+```typescript
+@capabilities(#{
+  confirmation: #{
+    type: "AdaptiveCard",
+    title: "Confirm Action",
+    body: """
+    Are you sure you want to perform this action?
+      * **Parameter**: {{ function.parameters.paramName }}
+    """
+  }
+})
+```
+
+### Adaptive Card Response
+```typescript
+@card(#{
+  dataPath: "$.items",
+  title: "$.title",
+  url: "$.link",
+  file: "cards/card.json"
+})
+```
+
+### Reasoning & Response Instructions
+```typescript
+@reasoning("""
+  Consider user's context when calling this operation.
+  Prioritize recent items over older ones.
+""")
+@responding("""
+  Present results in a clear table format with columns: ID, Title, Status.
+  Include a summary count at the end.
+""")
+```
+
+## Best Practices
+
+1. **Operation Names**: Use clear, action-oriented names (listProjects, createTicket)
+2. **Models**: Define TypeScript-like models for requests and responses
+3. **HTTP Methods**: Use appropriate verbs (@get, @post, @patch, @delete)
+4. **Paths**: Use RESTful path conventions with @route
+5. **Parameters**: Use @path, @query, @header, @body appropriately
+6. **Descriptions**: Provide clear descriptions for model understanding
+7. **Confirmations**: Add for destructive operations (delete, update critical data)
+8. **Cards**: Use for rich visual responses with multiple data items
+
+## Workflow
+
+Ask the user:
+1. What is the API base URL and purpose?
+2. What operations are needed (CRUD operations)?
+3. What authentication method does the API use?
+4. Should confirmations be required for any operations?
+5. Do responses need Adaptive Cards?
+
+Then generate:
+- Complete `main.tsp` with agent definition
+- Complete `actions.tsp` with API operations and models
+- Optional `cards/card.json` if Adaptive Cards are needed

package/skills/typespec-create-api-plugin/SYNC.md

@@ -0,0 +1,5 @@
+# Sync Info
+
+- **Source:** `vendor/awesome-copilot/skills/typespec-create-api-plugin`
+- **Git SHA:** `23fb7006c132a0bba75b0e5af7a35cab11272812`
+- **Synced:** 2026-03-24

package/skills/unit-test-vue-pinia/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/unit-test-vue-pinia/SKILL.md

@@ -0,0 +1,198 @@
+---
+name: unit-test-vue-pinia
+category: testing
+description: 'Write and review unit tests for Vue 3 + TypeScript + Vitest + Pinia codebases. Use when creating or updating tests for components, composables, and stores; mocking Pinia with createTestingPinia; applying Vue Test Utils patterns; and enforcing black-box assertions over implementation details.'
+---
+
+# unit-test-vue-pinia
+
+Use this skill to create or review unit tests for Vue components, composables, and Pinia stores. Keep tests small, deterministic, and behavior-first.
+
+## Workflow
+
+1. Identify the behavior boundary first: component UI behavior, composable behavior, or store behavior.
+2. Choose the narrowest test style that can prove that behavior.
+3. Set up Pinia with the least powerful option that still covers the scenario.
+4. Drive the test through public inputs such as props, form updates, button clicks, emitted child events, and store APIs.
+5. Assert observable outputs and side effects before considering any instance-level assertion.
+6. Return or review tests with clear behavior-oriented names and note any remaining coverage gaps.
+
+## Core Rules
+
+- Test one behavior per test.
+- Assert observable input/output behavior first (rendered text, emitted events, callback calls, store state changes).
+- Avoid implementation-coupled assertions.
+- Access `wrapper.vm` only in exceptional cases when there is no reasonable DOM, prop, emit, or store-level assertion.
+- Prefer explicit setup in `beforeEach()` and reset mocks every test.
+- Use checked-in reference material in `references/pinia-patterns.md` as the local source of truth for standard Pinia test setups.
+
+## Pinia Testing Approach
+
+Use `references/pinia-patterns.md` first, then fall back to Pinia's testing cookbook when the checked-in examples do not cover the case.
+
+### Default pattern for component tests
+
+Use `createTestingPinia` as a global plugin while mounting.
+Prefer `createSpy: vi.fn` as the default for consistency and easier action-spy assertions.
+
+```ts
+const wrapper = mount(ComponentUnderTest, {
+	global: {
+		plugins: [
+			createTestingPinia({
+				createSpy: vi.fn,
+			}),
+		],
+	},
+});
+```
+
+By default, actions are stubbed and spied.
+Use `stubActions: true` (default) when the test only needs to verify whether an action was called (or not called).
+
+### Accepted minimal Pinia setups
+
+The following are also valid and should not be flagged as incorrect:
+
+- `createTestingPinia({})` when the test does not assert Pinia action spy behavior.
+- `createTestingPinia({ initialState: ... })` or `createTestingPinia({ stubActions: ... })` without `createSpy`, when the test only needs state seeding or action stubbing behavior and does not inspect generated spies.
+- `setActivePinia(createTestingPinia(...))` in store/composable-focused tests (without mounting a component) when mocking/seeding dependent stores is needed.
+
+Use `createSpy: vi.fn` when action spy assertions are part of the test intent.
+
+### Execute real actions only when needed
+
+Use `stubActions: false` only when the test must validate the action's real behavior and side effects. Do not switch it on by default for simple "was called" assertions.
+
+```ts
+const wrapper = mount(ComponentUnderTest, {
+	global: {
+		plugins: [
+			createTestingPinia({
+				createSpy: vi.fn,
+				stubActions: false,
+			}),
+		],
+	},
+});
+```
+
+### Seed store state with `initialState`
+
+```ts
+const wrapper = mount(ComponentUnderTest, {
+	global: {
+		plugins: [
+			createTestingPinia({
+				createSpy: vi.fn,
+				initialState: {
+					counter: { n: 20 },
+					user: { name: "Leia Organa" },
+				},
+			}),
+		],
+	},
+});
+```
+
+### Add Pinia plugins through `createTestingPinia`
+
+```ts
+const wrapper = mount(ComponentUnderTest, {
+	global: {
+		plugins: [
+			createTestingPinia({
+				createSpy: vi.fn,
+				plugins: [myPiniaPlugin],
+			}),
+		],
+	},
+});
+```
+
+### Getter override pattern for edge cases
+
+```ts
+const pinia = createTestingPinia({ createSpy: vi.fn });
+const store = useCounterStore(pinia);
+
+store.double = 999;
+// @ts-expect-error test-only reset of overridden getter
+store.double = undefined;
+```
+
+### Pure store unit tests
+
+Prefer pure store tests with `createPinia()` when the goal is to validate store state transitions and action behavior without component rendering. Use `createTestingPinia()` only when you need stubbed dependent stores, seeded test doubles, or action spies.
+
+```ts
+beforeEach(() => {
+	setActivePinia(createPinia());
+});
+
+it("increments", () => {
+	const counter = useCounterStore();
+	counter.increment();
+	expect(counter.n).toBe(1);
+});
+```
+
+## Vue Test Utils Approach
+
+Follow Vue Test Utils guidance: <https://test-utils.vuejs.org/guide/>
+
+- Mount shallow by default for focused unit tests.
+- Mount full component trees only when integration behavior is the subject.
+- Drive behavior through props, user-like interactions, and emitted events.
+- Prefer `findComponent(...).vm.$emit(...)` for child stub events instead of touching parent internals.
+- Use `nextTick` only when updates are async.
+- Assert emitted events and payloads with `wrapper.emitted(...)`.
+- Access `wrapper.vm` only when no DOM assertion, emitted event assertion, prop assertion, or store-level assertion can express the behavior. Treat it as an exception and keep the assertion narrowly scoped.
+
+## Key Testing Snippets
+
+Emit and assert payload:
+
+```ts
+await wrapper.find("button").trigger("click");
+expect(wrapper.emitted("submit")?.[0]?.[0]).toBe("Mango Mission");
+```
+
+Update input and assert output:
+
+```ts
+await wrapper.find("input").setValue("Agent Violet");
+await wrapper.find("form").trigger("submit");
+expect(wrapper.emitted("save")?.[0]?.[0]).toBe("Agent Violet");
+```
+
+## Test Writing Workflow
+
+1. Identify the behavior boundary to test.
+2. Build minimal fixture data (only fields needed by that behavior).
+3. Configure Pinia and required test doubles.
+4. Trigger behavior through public inputs.
+5. Assert public outputs and side effects.
+6. Refactor test names to describe behavior, not implementation.
+
+## Constraints and Safety
+
+- Do not test private/internal implementation details.
+- Do not overuse snapshots for dynamic UI behavior.
+- Do not assert every field in large objects if only one behavior matters.
+- Keep fake data deterministic; avoid random values.
+- Do not claim a Pinia setup is wrong when it is one of the accepted minimal setups above.
+- Do not rewrite working tests toward deeper mounting or real actions unless the behavior under test requires that extra surface area.
+- Flag missing test coverage, brittle selectors, and implementation-coupled assertions explicitly during review.
+
+## Output Contract
+
+- For `create` or `update`, return the finished test code plus a short note describing the selected Pinia strategy.
+- For `review`, return concrete findings first, then missing coverage or brittleness risks.
+- When the safest choice is ambiguous, state the assumption that drove the chosen test setup.
+
+## References
+
+- `references/pinia-patterns.md`
+- Pinia testing cookbook: <https://pinia.vuejs.org/cookbook/testing.html>
+- Vue Test Utils guide: <https://test-utils.vuejs.org/guide/>

package/skills/unit-test-vue-pinia/SYNC.md

@@ -0,0 +1,5 @@
+# Sync Info
+
+- **Source:** `vendor/awesome-copilot/skills/unit-test-vue-pinia`
+- **Git SHA:** `23fb7006c132a0bba75b0e5af7a35cab11272812`
+- **Synced:** 2026-03-24

package/skills/unit-test-vue-pinia/references/pinia-patterns.md

@@ -0,0 +1,95 @@
+# Pinia Testing Snippets (Cookbook-Aligned)
+
+Use these patterns directly when writing tests with `@pinia/testing`.
+
+## Component mount with `createTestingPinia`
+
+```ts
+import { mount } from "@vue/test-utils";
+import { createTestingPinia } from "@pinia/testing";
+import { vi } from "vitest";
+
+const wrapper = mount(ComponentUnderTest, {
+  global: {
+    plugins: [
+      createTestingPinia({
+        createSpy: vi.fn,
+      }),
+    ],
+  },
+});
+```
+
+## Execute real actions
+
+Use this only when behavior inside the action must run.
+If the test only checks call/no-call expectations, keep default stubbing (`stubActions: true`).
+
+```ts
+const wrapper = mount(ComponentUnderTest, {
+  global: {
+    plugins: [
+      createTestingPinia({
+        createSpy: vi.fn,
+        stubActions: false,
+      }),
+    ],
+  },
+});
+```
+
+## Seed starting state
+
+```ts
+const wrapper = mount(ComponentUnderTest, {
+  global: {
+    plugins: [
+      createTestingPinia({
+        createSpy: vi.fn,
+        initialState: {
+          counter: { n: 10 },
+          profile: { name: "Sherlock Holmes" },
+        },
+      }),
+    ],
+  },
+});
+```
+
+## Use store in test and assert action call
+
+```ts
+const pinia = createTestingPinia({ createSpy: vi.fn });
+const store = useCounterStore(pinia);
+
+store.increment();
+expect(store.increment).toHaveBeenCalledTimes(1);
+```
+
+## Add plugin under test
+
+```ts
+const wrapper = mount(ComponentUnderTest, {
+  global: {
+    plugins: [
+      createTestingPinia({
+        createSpy: vi.fn,
+        plugins: [myPiniaPlugin],
+      }),
+    ],
+  },
+});
+```
+
+## Override and reset getters for edge tests
+
+```ts
+const pinia = createTestingPinia({ createSpy: vi.fn });
+const store = useCounterStore(pinia);
+
+store.double = 42;
+expect(store.double).toBe(42);
+
+// @ts-expect-error test-only reset
+store.double = undefined;
+```

package/skills/update-avm-modules-in-bicep/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/update-avm-modules-in-bicep/SKILL.md

@@ -0,0 +1,60 @@
+---
+name: update-avm-modules-in-bicep
+description: 'Update Azure Verified Modules (AVM) to latest versions in Bicep files.'
+---
+
+# Update Azure Verified Modules in Bicep Files
+
+Update Bicep file `${file}` to use latest Azure Verified Module (AVM) versions. Limit progress updates to non-breaking changes. Don't output information other than the final output table and summary.
+
+## Process
+
+1. **Scan**: Extract AVM modules and current versions from `${file}`
+1. **Identify**: List all unique AVM modules used by matching `avm/res/{service}/{resource}` using `#search` tool
+1. **Check**: Use `#fetch` tool to get latest version of each AVM module from MCR: `https://mcr.microsoft.com/v2/bicep/avm/res/{service}/{resource}/tags/list`
+1. **Compare**: Parse semantic versions to identify AVM modules needing update
+1. **Review**: For breaking changes, use `#fetch` tool to get docs from: `https://github.com/Azure/bicep-registry-modules/tree/main/avm/res/{service}/{resource}`
+1. **Update**: Apply version updates and parameter changes using `#editFiles` tool
+1. **Validate**: Run `bicep lint` and `bicep build` using `#runCommands` tool to ensure compliance.
+1. **Output**: Summarize changes in a table format with summary of updates below.
+
+## Tool Usage
+
+Always use tools `#search`, `#searchResults`,`#fetch`, `#editFiles`, `#runCommands`, `#todos` if available. Avoid writing code to perform tasks.
+
+## Breaking Change Policy
+
+⚠️ **PAUSE for approval** if updates involve:
+
+- Incompatible parameter changes
+- Security/compliance modifications
+- Behavioral changes
+
+## Output Format
+
+Only display results in table with icons:
+
+```markdown
+| Module | Current | Latest | Status | Action | Docs |
+|--------|---------|--------|--------|--------|------|
+| avm/res/compute/vm | 0.1.0 | 0.2.0 | 🔄 | Updated | [📖](link) |
+| avm/res/storage/account | 0.3.0 | 0.3.0 | ✅ | Current | [📖](link) |
+
+### Summary of Updates
+
+Describe updates made, any manual reviews needed or issues encountered.
+```
+
+## Icons
+
+- 🔄 Updated
+- ✅ Current
+- ⚠️ Manual review required
+- ❌ Failed
+- 📖 Documentation
+
+## Requirements
+
+- Use MCR tags API only for version discovery
+- Parse JSON tags array and sort by semantic versioning
+- Maintain Bicep file validity and linting compliance

package/skills/update-avm-modules-in-bicep/SYNC.md

@@ -0,0 +1,5 @@
+# Sync Info
+
+- **Source:** `vendor/awesome-copilot/skills/update-avm-modules-in-bicep`
+- **Git SHA:** `23fb7006c132a0bba75b0e5af7a35cab11272812`
+- **Synced:** 2026-03-24

package/skills/update-implementation-plan/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.