devskill 2.0.7 → 2.0.8

package/skills/plantuml-ascii/SKILL.md

@@ -0,0 +1,305 @@
+---
+name: plantuml-ascii
+description: "Generate ASCII art diagrams using PlantUML text mode. Use when user asks to create ASCII diagrams, text-based diagrams, terminal-friendly diagrams, or mentions plantuml ascii, text diagram, ascii art diagram. Supports: Converting PlantUML diagrams to ASCII art, Creating sequence diagrams, class diagrams, flowcharts in ASCII format, Generating Unicode-enhanced ASCII art with -utxt flag"
+license: MIT
+allowed-tools: Bash, Write, Read
+---
+
+# PlantUML ASCII Art Diagram Generator
+
+## Overview
+
+Create text-based ASCII art diagrams using PlantUML. Perfect for documentation in terminal environments, README files, emails, or any scenario where graphical diagrams aren't suitable.
+
+## What is PlantUML ASCII Art?
+
+PlantUML can generate diagrams as plain text (ASCII art) instead of images. This is useful for:
+
+- Terminal-based workflows
+- Git commits/PRs without image support
+- Documentation that needs to be version-controlled
+- Environments where graphical tools aren't available
+
+## Installation
+
+```bash
+# macOS
+brew install plantuml
+
+# Linux (varies by distro)
+sudo apt-get install plantuml  # Ubuntu/Debian
+sudo yum install plantuml      # RHEL/CentOS
+
+# Or download JAR directly
+wget https://github.com/plantuml/plantuml/releases/download/v1.2024.0/plantuml-1.2024.0.jar
+```
+
+## Output Formats
+
+| Flag    | Format        | Description                          |
+| ------- | ------------- | ------------------------------------ |
+| `-txt`  | ASCII         | Pure ASCII characters                |
+| `-utxt` | Unicode ASCII | Enhanced with box-drawing characters |
+
+## Basic Workflow
+
+### 1. Create PlantUML Diagram File
+
+```plantuml
+@startuml
+participant Bob
+actor Alice
+
+Bob -> Alice : hello
+Alice -> Bob : Is it ok?
+@enduml
+```
+
+### 2. Generate ASCII Art
+
+```bash
+# Standard ASCII output
+plantuml -txt diagram.puml
+
+# Unicode-enhanced output (better looking)
+plantuml -utxt diagram.puml
+
+# Using JAR directly
+java -jar plantuml.jar -txt diagram.puml
+java -jar plantuml.jar -utxt diagram.puml
+```
+
+### 3. View Output
+
+Output is saved as `diagram.atxt` (ASCII) or `diagram.utxt` (Unicode).
+
+## Diagram Types Supported
+
+### Sequence Diagram
+
+```plantuml
+@startuml
+actor User
+participant "Web App" as App
+database "Database" as DB
+
+User -> App : Login Request
+App -> DB : Validate Credentials
+DB --> App : User Data
+App --> User : Auth Token
+@enduml
+```
+
+### Class Diagram
+
+```plantuml
+@startuml
+class User {
+  +id: int
+  +name: string
+  +email: string
+  +login(): bool
+}
+
+class Order {
+  +id: int
+  +total: float
+  +items: List
+  +calculateTotal(): float
+}
+
+User "1" -- "*" Order : places
+@enduml
+```
+
+### Activity Diagram
+
+```plantuml
+@startuml
+start
+:Initialize;
+if (Is Valid?) then (yes)
+  :Process Data;
+  :Save Result;
+else (no)
+  :Log Error;
+  stop
+endif
+:Complete;
+stop
+@enduml
+```
+
+### State Diagram
+
+```plantuml
+@startuml
+[*] --> Idle
+Idle --> Processing : start
+Processing --> Success : complete
+Processing --> Error : fail
+Success --> [*]
+Error --> Idle : retry
+@enduml
+```
+
+### Component Diagram
+
+```plantuml
+@startuml
+[Client] as client
+[API Gateway] as gateway
+[Service A] as svcA
+[Service B] as svcB
+[Database] as db
+
+client --> gateway
+gateway --> svcA
+gateway --> svcB
+svcA --> db
+svcB --> db
+@enduml
+```
+
+### Use Case Diagram
+
+```plantuml
+@startuml
+actor "User" as user
+actor "Admin" as admin
+
+rectangle "System" {
+  user -- (Login)
+  user -- (View Profile)
+  user -- (Update Settings)
+  admin -- (Manage Users)
+  admin -- (Configure System)
+}
+@enduml
+```
+
+### Deployment Diagram
+
+```plantuml
+@startuml
+actor "User" as user
+node "Load Balancer" as lb
+node "Web Server 1" as ws1
+node "Web Server 2" as ws2
+database "Primary DB" as db1
+database "Replica DB" as db2
+
+user --> lb
+lb --> ws1
+lb --> ws2
+ws1 --> db1
+ws2 --> db1
+db1 --> db2 : replicate
+@enduml
+```
+
+## Command-Line Options
+
+```bash
+# Specify output directory
+plantuml -txt -o ./output diagram.puml
+
+# Process all files in directory
+plantuml -txt ./diagrams/
+
+# Include dot files (hidden files)
+plantuml -txt -includeDot diagrams/
+
+# Verbose output
+plantuml -txt -v diagram.puml
+
+# Specify charset
+plantuml -txt -charset UTF-8 diagram.puml
+```
+
+## Ant Task Integration
+
+```xml
+<target name="generate-ascii">
+  <plantuml dir="./src" format="txt" />
+</target>
+
+<target name="generate-unicode-ascii">
+  <plantuml dir="./src" format="utxt" />
+</target>
+```
+
+## Tips for Better ASCII Diagrams
+
+1. **Keep it simple**: Complex diagrams don't render well in ASCII
+2. **Short labels**: Long text breaks ASCII alignment
+3. **Use Unicode (`-utxt`)**: Better visual quality with box-drawing chars
+4. **Test before sharing**: Verify in terminal with fixed-width font
+5. **Consider alternatives**: For complex diagrams, use Mermaid.js or graphviz
+
+## Example Output Comparison
+
+**Standard ASCII (`-txt`)**:
+
+```
+     ,---.          ,---.
+     |Bob|          |Alice|
+     `---'          `---'
+      |   hello      |
+      |------------->|
+      |              |
+      |  Is it ok?   |
+      |<-------------|
+      |              |
+```
+
+**Unicode ASCII (`-utxt`)**:
+
+```
+┌─────┐        ┌─────┐
+│ Bob │        │Alice│
+└─────┘        └─────┘
+  │   hello      │
+  │─────────────>│
+  │              │
+  │  Is it ok?   │
+  │<─────────────│
+  │              │
+```
+
+## Quick Reference
+
+```bash
+# Create sequence diagram in ASCII
+cat > seq.puml << 'EOF'
+@startuml
+Alice -> Bob: Request
+Bob --> Alice: Response
+@enduml
+EOF
+
+plantuml -txt seq.puml
+cat seq.atxt
+
+# Create with Unicode
+plantuml -utxt seq.puml
+cat seq.utxt
+```
+
+## Troubleshooting
+
+**Problem**: Garbled Unicode characters
+
+- **Solution**: Ensure terminal supports UTF-8 and has proper font
+
+**Problem**: Diagram looks misaligned
+
+- **Solution**: Use fixed-width font (Courier, Monaco, Consolas)
+
+**Problem**: Command not found
+
+- **Solution**: Install PlantUML or use Java JAR directly
+
+**Problem**: Output file not created
+
+- **Solution**: Check file permissions, ensure PlantUML has write access

package/skills/plantuml-ascii/SYNC.md

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

package/skills/playwright-automation-fill-in-form/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/playwright-automation-fill-in-form/SKILL.md

@@ -0,0 +1,28 @@
+---
+name: playwright-automation-fill-in-form
+description: 'Automate filling in a form using Playwright MCP'
+---
+
+# Automating Filling in a Form with Playwright MCP
+
+Your goal is to automate the process of filling in a form using Playwright MCP.
+
+## Specific Instructions
+
+Navigate to https://forms.microsoft.com/url-of-my-form
+
+### Fill in the form with the following details:
+
+1. Show: playwright live
+
+2. Date: 15 July
+
+3. Time: 1:00 AM
+
+4. Topic: Playwright Live - Latest updates on Playwright MCP + Live Demo
+
+5. Upload image: /Users/myuserName/Downloads/my-image.png
+
+DO NOT SUBMIT THE FORM. 
+
+Ask for a review of the form before submitting it.

package/skills/playwright-automation-fill-in-form/SYNC.md

@@ -0,0 +1,5 @@
+# Sync Info
+
+- **Source:** `vendor/awesome-copilot/skills/playwright-automation-fill-in-form`
+- **Git SHA:** `23fb7006c132a0bba75b0e5af7a35cab11272812`
+- **Synced:** 2026-03-24

package/skills/playwright-explore-website/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/playwright-explore-website/SKILL.md

@@ -0,0 +1,17 @@
+---
+name: playwright-explore-website
+description: 'Website exploration for testing using Playwright MCP'
+---
+
+# Website Exploration for Testing
+
+Your goal is to explore the website and identify key functionalities.
+
+## Specific Instructions
+
+1. Navigate to the provided URL using the Playwright MCP Server. If no URL is provided, ask the user to provide one.
+2. Identify and interact with 3-5 core features or user flows.
+3. Document the user interactions, relevant UI elements (and their locators), and the expected outcomes.
+4. Close the browser context upon completion.
+5. Provide a concise summary of your findings.
+6. Propose and generate test cases based on the exploration.

package/skills/playwright-explore-website/SYNC.md

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

package/skills/playwright-generate-test/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/playwright-generate-test/SKILL.md

@@ -0,0 +1,17 @@
+---
+name: playwright-generate-test
+description: 'Generate a Playwright test based on a scenario using Playwright MCP'
+---
+
+# Test Generation with Playwright MCP
+
+Your goal is to generate a Playwright test based on the provided scenario after completing all prescribed steps.
+
+## Specific Instructions
+
+- You are given a scenario, and you need to generate a playwright test for it. If the user does not provide a scenario, you will ask them to provide one.
+- DO NOT generate test code prematurely or based solely on the scenario without completing all prescribed steps.
+- DO run steps one by one using the tools provided by the Playwright MCP.
+- Only after all steps are completed, emit a Playwright TypeScript test that uses `@playwright/test` based on message history
+- Save generated test file in the tests directory
+- Execute the test file and iterate until the test passes

package/skills/playwright-generate-test/SYNC.md

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

package/skills/polyglot-test-agent/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/polyglot-test-agent/SKILL.md

@@ -0,0 +1,161 @@
+---
+name: polyglot-test-agent
+description: 'Generates comprehensive, workable unit tests for any programming language using a multi-agent pipeline. Use when asked to generate tests, write unit tests, improve test coverage, add test coverage, create test files, or test a codebase. Supports C#, TypeScript, JavaScript, Python, Go, Rust, Java, and more. Orchestrates research, planning, and implementation phases to produce tests that compile, pass, and follow project conventions.'
+---
+
+# Polyglot Test Generation Skill
+
+An AI-powered skill that generates comprehensive, workable unit tests for any programming language using a coordinated multi-agent pipeline.
+
+## When to Use This Skill
+
+Use this skill when you need to:
+- Generate unit tests for an entire project or specific files
+- Improve test coverage for existing codebases
+- Create test files that follow project conventions
+- Write tests that actually compile and pass
+- Add tests for new features or untested code
+
+## How It Works
+
+This skill coordinates multiple specialized agents in a **Research → Plan → Implement** pipeline:
+
+### Pipeline Overview
+
+```
+┌─────────────────────────────────────────────────────────────┐
+│                     TEST GENERATOR                          │
+│  Coordinates the full pipeline and manages state            │
+└─────────────────────┬───────────────────────────────────────┘
+                      │
+        ┌─────────────┼─────────────┐
+        ▼             ▼             ▼
+┌───────────┐  ┌───────────┐  ┌───────────────┐
+│ RESEARCHER│  │  PLANNER  │  │  IMPLEMENTER  │
+│           │  │           │  │               │
+│ Analyzes  │  │ Creates   │  │ Writes tests  │
+│ codebase  │→ │ phased    │→ │ per phase     │
+│           │  │ plan      │  │               │
+└───────────┘  └───────────┘  └───────┬───────┘
+                                      │
+                    ┌─────────┬───────┼───────────┐
+                    ▼         ▼       ▼           ▼
+              ┌─────────┐ ┌───────┐ ┌───────┐ ┌───────┐
+              │ BUILDER │ │TESTER │ │ FIXER │ │LINTER │
+              │         │ │       │ │       │ │       │
+              │ Compiles│ │ Runs  │ │ Fixes │ │Formats│
+              │ code    │ │ tests │ │ errors│ │ code  │
+              └─────────┘ └───────┘ └───────┘ └───────┘
+```
+
+## Step-by-Step Instructions
+
+### Step 1: Determine the User Request
+
+Make sure you understand what user is asking and for what scope.
+When the user does not express strong requirements for test style, coverage goals, or conventions, source the guidelines from [unit-test-generation.prompt.md](unit-test-generation.prompt.md). This prompt provides best practices for discovering conventions, parameterization strategies, coverage goals (aim for 80%), and language-specific patterns.
+
+### Step 2: Invoke the Test Generator
+
+Start by calling the `polyglot-test-generator` agent with your test generation request:
+
+```
+Generate unit tests for [path or description of what to test], following the [unit-test-generation.prompt.md](unit-test-generation.prompt.md) guidelines
+```
+
+The Test Generator will manage the entire pipeline automatically.
+
+### Step 3: Research Phase (Automatic)
+
+The `polyglot-test-researcher` agent analyzes your codebase to understand:
+- **Language & Framework**: Detects C#, TypeScript, Python, Go, Rust, Java, etc.
+- **Testing Framework**: Identifies MSTest, xUnit, Jest, pytest, go test, etc.
+- **Project Structure**: Maps source files, existing tests, and dependencies
+- **Build Commands**: Discovers how to build and test the project
+
+Output: `.testagent/research.md`
+
+### Step 4: Planning Phase (Automatic)
+
+The `polyglot-test-planner` agent creates a structured implementation plan:
+- Groups files into logical phases (2-5 phases typical)
+- Prioritizes by complexity and dependencies
+- Specifies test cases for each file
+- Defines success criteria per phase
+
+Output: `.testagent/plan.md`
+
+### Step 5: Implementation Phase (Automatic)
+
+The `polyglot-test-implementer` agent executes each phase sequentially:
+
+1. **Read** source files to understand the API
+2. **Write** test files following project patterns
+3. **Build** using the `polyglot-test-builder` subagent to verify compilation
+4. **Test** using the `polyglot-test-tester` subagent to verify tests pass
+5. **Fix** using the `polyglot-test-fixer` subagent if errors occur
+6. **Lint** using the `polyglot-test-linter` subagent for code formatting
+
+Each phase completes before the next begins, ensuring incremental progress.
+
+### Coverage Types
+- **Happy path**: Valid inputs produce expected outputs
+- **Edge cases**: Empty values, boundaries, special characters
+- **Error cases**: Invalid inputs, null handling, exceptions
+
+## State Management
+
+All pipeline state is stored in `.testagent/` folder:
+
+| File | Purpose |
+|------|---------|
+| `.testagent/research.md` | Codebase analysis results |
+| `.testagent/plan.md` | Phased implementation plan |
+| `.testagent/status.md` | Progress tracking (optional) |
+
+## Examples
+
+### Example 1: Full Project Testing
+```
+Generate unit tests for my Calculator project at C:\src\Calculator
+```
+
+### Example 2: Specific File Testing
+```
+Generate unit tests for src/services/UserService.ts
+```
+
+### Example 3: Targeted Coverage
+```
+Add tests for the authentication module with focus on edge cases
+```
+
+## Agent Reference
+
+| Agent | Purpose | Tools |
+|-------|---------|-------|
+| `polyglot-test-generator` | Coordinates pipeline | runCommands, codebase, editFiles, search, runSubagent |
+| `polyglot-test-researcher` | Analyzes codebase | runCommands, codebase, editFiles, search, fetch, runSubagent |
+| `polyglot-test-planner` | Creates test plan | codebase, editFiles, search, runSubagent |
+| `polyglot-test-implementer` | Writes test files | runCommands, codebase, editFiles, search, runSubagent |
+| `polyglot-test-builder` | Compiles code | runCommands, codebase, search |
+| `polyglot-test-tester` | Runs tests | runCommands, codebase, search |
+| `polyglot-test-fixer` | Fixes errors | runCommands, codebase, editFiles, search |
+| `polyglot-test-linter` | Formats code | runCommands, codebase, search |
+
+## Requirements
+
+- Project must have a build/test system configured
+- Testing framework should be installed (or installable)
+- VS Code with GitHub Copilot extension
+
+## Troubleshooting
+
+### Tests don't compile
+The `polyglot-test-fixer` agent will attempt to resolve compilation errors. Check `.testagent/plan.md` for the expected test structure.
+
+### Tests fail
+Review the test output and adjust test expectations. Some tests may require mocking dependencies.
+
+### Wrong testing framework detected
+Specify your preferred framework in the initial request: "Generate Jest tests for..."

package/skills/polyglot-test-agent/SYNC.md

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