@abarcenas/ai-workflow-template 1.1.0

package/.github/skills/git-commit/SKILL.md

@@ -0,0 +1,124 @@
+---
+name: git-commit
+description: 'Execute git commit with conventional commit message analysis, intelligent staging, and message generation. Use when user asks to commit changes, create a git commit, or mentions "/commit". Supports: (1) Auto-detecting type and scope from changes, (2) Generating conventional commit messages from diff, (3) Interactive commit with optional type/scope/description overrides, (4) Intelligent file staging for logical grouping'
+license: MIT
+allowed-tools: Bash
+---
+
+# Git Commit with Conventional Commits
+
+## Overview
+
+Create standardized, semantic git commits using the Conventional Commits specification. Analyze the actual diff to determine appropriate type, scope, and message.
+
+## Conventional Commit Format
+
+```
+<type>[optional scope]: <description>
+
+[optional body]
+
+[optional footer(s)]
+```
+
+## Commit Types
+
+| Type       | Purpose                        |
+| ---------- | ------------------------------ |
+| `feat`     | New feature                    |
+| `fix`      | Bug fix                        |
+| `docs`     | Documentation only             |
+| `style`    | Formatting/style (no logic)    |
+| `refactor` | Code refactor (no feature/fix) |
+| `perf`     | Performance improvement        |
+| `test`     | Add/update tests               |
+| `build`    | Build system/dependencies      |
+| `ci`       | CI/config changes              |
+| `chore`    | Maintenance/misc               |
+| `revert`   | Revert commit                  |
+
+## Breaking Changes
+
+```
+# Exclamation mark after type/scope
+feat!: remove deprecated endpoint
+
+# BREAKING CHANGE footer
+feat: allow config to extend other configs
+
+BREAKING CHANGE: `extends` key behavior changed
+```
+
+## Workflow
+
+### 1. Analyze Diff
+
+```bash
+# If files are staged, use staged diff
+git diff --staged
+
+# If nothing staged, use working tree diff
+git diff
+
+# Also check status
+git status --porcelain
+```
+
+### 2. Stage Files (if needed)
+
+If nothing is staged or you want to group changes differently:
+
+```bash
+# Stage specific files
+git add path/to/file1 path/to/file2
+
+# Stage by pattern
+git add *.test.*
+git add src/components/*
+
+# Interactive staging
+git add -p
+```
+
+**Never commit secrets** (.env, credentials.json, private keys).
+
+### 3. Generate Commit Message
+
+Analyze the diff to determine:
+
+- **Type**: What kind of change is this?
+- **Scope**: What area/module is affected?
+- **Description**: One-line summary of what changed (present tense, imperative mood, <72 chars)
+
+### 4. Execute Commit
+
+```bash
+# Single line
+git commit -m "<type>[scope]: <description>"
+
+# Multi-line with body/footer
+git commit -m "$(cat <<'EOF'
+<type>[scope]: <description>
+
+<optional body>
+
+<optional footer>
+EOF
+)"
+```
+
+## Best Practices
+
+- One logical change per commit
+- Present tense: "add" not "added"
+- Imperative mood: "fix bug" not "fixes bug"
+- Reference issues: `Closes #123`, `Refs #456`
+- Keep description under 72 characters
+
+## Git Safety Protocol
+
+- NEVER update git config
+- NEVER run destructive commands (--force, hard reset) without explicit request
+- NEVER skip hooks (--no-verify) unless user asks
+- NEVER force push to main/master
+- If commit fails due to hooks, fix and create NEW commit (don't amend)

package/.github/skills/github-issues/SKILL.md

@@ -0,0 +1,134 @@
+---
+name: github-issues
+description: 'Create, update, and manage GitHub issues using MCP tools. Use this skill when users want to create bug reports, feature requests, or task issues, update existing issues, add labels/assignees/milestones, or manage issue workflows. Triggers on requests like "create an issue", "file a bug", "request a feature", "update issue X", or any GitHub issue management task.'
+---
+
+# GitHub Issues
+
+Manage GitHub issues using the `@modelcontextprotocol/server-github` MCP server.
+
+## Available MCP Tools
+
+| Tool                             | Purpose                |
+| -------------------------------- | ---------------------- |
+| `mcp__github__create_issue`      | Create new issues      |
+| `mcp__github__update_issue`      | Update existing issues |
+| `mcp__github__get_issue`         | Fetch issue details    |
+| `mcp__github__search_issues`     | Search issues          |
+| `mcp__github__add_issue_comment` | Add comments           |
+| `mcp__github__list_issues`       | List repository issues |
+
+## Workflow
+
+1. **Determine action**: Create, update, or query?
+2. **Gather context**: Get repo info, existing labels, milestones if needed
+3. **Structure content**: Use appropriate template from [references/templates.md](references/templates.md)
+4. **Execute**: Call the appropriate MCP tool
+5. **Confirm**: Report the issue URL to user
+
+## Creating Issues
+
+### Required Parameters
+
+```
+owner: repository owner (org or user)
+repo: repository name
+title: clear, actionable title
+body: structured markdown content
+```
+
+### Optional Parameters
+
+```
+labels: ["bug", "enhancement", "documentation", ...]
+assignees: ["username1", "username2"]
+milestone: milestone number (integer)
+```
+
+### Title Guidelines
+
+- Start with type prefix when useful: `[Bug]`, `[Feature]`, `[Docs]`
+- Be specific and actionable
+- Keep under 72 characters
+- Examples:
+  - `[Bug] Login fails with SSO enabled`
+  - `[Feature] Add dark mode support`
+  - `Add unit tests for auth module`
+
+### Body Structure
+
+Always use the templates in [references/templates.md](references/templates.md). Choose based on issue type:
+
+| User Request                    | Template        |
+| ------------------------------- | --------------- |
+| Bug, error, broken, not working | Bug Report      |
+| Feature, enhancement, add, new  | Feature Request |
+| Task, chore, refactor, update   | Task            |
+
+## Updating Issues
+
+Use `mcp__github__update_issue` with:
+
+```
+owner, repo, issue_number (required)
+title, body, state, labels, assignees, milestone (optional - only changed fields)
+```
+
+State values: `open`, `closed`
+
+## Examples
+
+### Example 1: Bug Report
+
+**User**: "Create a bug issue - the login page crashes when using SSO"
+
+**Action**: Call `mcp__github__create_issue` with:
+
+```json
+{
+  "owner": "github",
+  "repo": "awesome-copilot",
+  "title": "[Bug] Login page crashes when using SSO",
+  "body": "## Description\nThe login page crashes when users attempt to authenticate using SSO.\n\n## Steps to Reproduce\n1. Navigate to login page\n2. Click 'Sign in with SSO'\n3. Page crashes\n\n## Expected Behavior\nSSO authentication should complete and redirect to dashboard.\n\n## Actual Behavior\nPage becomes unresponsive and displays error.\n\n## Environment\n- Browser: [To be filled]\n- OS: [To be filled]\n\n## Additional Context\nReported by user.",
+  "labels": ["bug"]
+}
+```
+
+### Example 2: Feature Request
+
+**User**: "Create a feature request for dark mode with high priority"
+
+**Action**: Call `mcp__github__create_issue` with:
+
+```json
+{
+  "owner": "github",
+  "repo": "awesome-copilot",
+  "title": "[Feature] Add dark mode support",
+  "body": "## Summary\nAdd dark mode theme option for improved user experience and accessibility.\n\n## Motivation\n- Reduces eye strain in low-light environments\n- Increasingly expected by users\n- Improves accessibility\n\n## Proposed Solution\nImplement theme toggle with system preference detection.\n\n## Acceptance Criteria\n- [ ] Toggle switch in settings\n- [ ] Persists user preference\n- [ ] Respects system preference by default\n- [ ] All UI components support both themes\n\n## Alternatives Considered\nNone specified.\n\n## Additional Context\nHigh priority request.",
+  "labels": ["enhancement", "high-priority"]
+}
+```
+
+## Common Labels
+
+Use these standard labels when applicable:
+
+| Label              | Use For                       |
+| ------------------ | ----------------------------- |
+| `bug`              | Something isn't working       |
+| `enhancement`      | New feature or improvement    |
+| `documentation`    | Documentation updates         |
+| `good first issue` | Good for newcomers            |
+| `help wanted`      | Extra attention needed        |
+| `question`         | Further information requested |
+| `wontfix`          | Will not be addressed         |
+| `duplicate`        | Already exists                |
+| `high-priority`    | Urgent issues                 |
+
+## Tips
+
+- Always confirm the repository context before creating issues
+- Ask for missing critical information rather than guessing
+- Link related issues when known: `Related to #123`
+- For updates, fetch current issue first to preserve unchanged fields

package/.github/skills/github-issues/references/templates.md

@@ -0,0 +1,110 @@
+# Issue Templates
+
+Copy and customize these templates for issue bodies.
+
+## Bug Report Template
+
+```markdown
+## Description
+
+[Clear description of the bug]
+
+## Steps to Reproduce
+
+1. [First step]
+2. [Second step]
+3. [And so on...]
+
+## Expected Behavior
+
+[What should happen]
+
+## Actual Behavior
+
+[What actually happens]
+
+## Environment
+
+- Browser: [e.g., Chrome 120]
+- OS: [e.g., macOS 14.0]
+- Version: [e.g., v1.2.3]
+
+## Screenshots/Logs
+
+[If applicable]
+
+## Additional Context
+
+[Any other relevant information]
+```
+
+## Feature Request Template
+
+```markdown
+## Summary
+
+[One-line description of the feature]
+
+## Motivation
+
+[Why is this feature needed? What problem does it solve?]
+
+## Proposed Solution
+
+[How should this feature work?]
+
+## Acceptance Criteria
+
+- [ ] [Criterion 1]
+- [ ] [Criterion 2]
+- [ ] [Criterion 3]
+
+## Alternatives Considered
+
+[Other approaches considered and why they weren't chosen]
+
+## Additional Context
+
+[Mockups, examples, or related issues]
+```
+
+## Task Template
+
+```markdown
+## Objective
+
+[What needs to be accomplished]
+
+## Details
+
+[Detailed description of the work]
+
+## Checklist
+
+- [ ] [Subtask 1]
+- [ ] [Subtask 2]
+- [ ] [Subtask 3]
+
+## Dependencies
+
+[Any blockers or related work]
+
+## Notes
+
+[Additional context or considerations]
+```
+
+## Minimal Template
+
+For simple issues:
+
+```markdown
+## Description
+
+[What and why]
+
+## Tasks
+
+- [ ] [Task 1]
+- [ ] [Task 2]
+```

package/.github/skills/microsoft-docs/SKILL.md

@@ -0,0 +1,114 @@
+---
+name: microsoft-docs
+description: "Query official Microsoft documentation to find concepts, tutorials, and code examples across Azure, .NET, Agent Framework, Aspire, VS Code, GitHub, and more. Uses Microsoft Learn MCP as the default, with Context7 and Aspire MCP for content that lives outside learn.microsoft.com."
+---
+
+# Microsoft Docs
+
+Research skill for the Microsoft technology ecosystem. Covers learn.microsoft.com and documentation that lives outside it (VS Code, GitHub, Aspire, Agent Framework repos).
+
+---
+
+## Default: Microsoft Learn MCP
+
+Use these tools for **everything on learn.microsoft.com** — Azure, .NET, M365, Power Platform, Agent Framework, Semantic Kernel, Windows, and more. This is the primary tool for the vast majority of Microsoft documentation queries.
+
+| Tool                           | Purpose                                                                                                 |
+| ------------------------------ | ------------------------------------------------------------------------------------------------------- |
+| `microsoft_docs_search`        | Search learn.microsoft.com — concepts, guides, tutorials, configuration                                 |
+| `microsoft_code_sample_search` | Find working code snippets from Learn docs. Pass `language` (`python`, `csharp`, etc.) for best results |
+| `microsoft_docs_fetch`         | Get full page content from a specific URL (when search excerpts aren't enough)                          |
+
+Use `microsoft_docs_fetch` after search when you need complete tutorials, all config options, or when search excerpts are truncated.
+
+---
+
+## Exceptions: When to Use Other Tools
+
+The following categories live **outside** learn.microsoft.com. Use the specified tool instead.
+
+### .NET Aspire — Use Aspire MCP Server (preferred) or Context7
+
+Aspire docs live on **aspire.dev**, not Learn. The best tool depends on your Aspire CLI version:
+
+**CLI 13.2+** (recommended) — The Aspire MCP server includes built-in docs search tools:
+
+| MCP Tool      | Description                                       |
+| ------------- | ------------------------------------------------- |
+| `list_docs`   | Lists all available documentation from aspire.dev |
+| `search_docs` | Weighted lexical search across aspire.dev content |
+| `get_doc`     | Retrieves a specific document by slug             |
+
+These ship in Aspire CLI 13.2 ([PR #14028](https://github.com/dotnet/aspire/pull/14028)). To update: `aspire update --self --channel daily`. Ref: https://davidpine.dev/posts/aspire-docs-mcp-tools/
+
+**CLI 13.1** — The MCP server provides integration lookup (`list_integrations`, `get_integration_docs`) but **not** docs search. Fall back to Context7:
+
+| Library ID                 | Use for                                                   |
+| -------------------------- | --------------------------------------------------------- |
+| `/microsoft/aspire.dev`    | Primary — guides, integrations, CLI reference, deployment |
+| `/dotnet/aspire`           | Runtime source — API internals, implementation details    |
+| `/communitytoolkit/aspire` | Community integrations — Go, Java, Node.js, Ollama        |
+
+### VS Code — Use Context7
+
+VS Code docs live on **code.visualstudio.com**, not Learn.
+
+| Library ID                        | Use for                                                            |
+| --------------------------------- | ------------------------------------------------------------------ |
+| `/websites/code_visualstudio`     | User docs — settings, features, debugging, remote dev              |
+| `/websites/code_visualstudio_api` | Extension API — webviews, TreeViews, commands, contribution points |
+
+### GitHub — Use Context7
+
+GitHub docs live on **docs.github.com** and **cli.github.com**.
+
+| Library ID             | Use for                                       |
+| ---------------------- | --------------------------------------------- |
+| `/websites/github_en`  | Actions, API, repos, security, admin, Copilot |
+| `/websites/cli_github` | GitHub CLI (`gh`) commands and flags          |
+
+### Agent Framework — Use Learn MCP + Context7
+
+Agent Framework tutorials are on learn.microsoft.com (use `microsoft_docs_search`), but the **GitHub repo** has API-level detail that is often ahead of published docs — particularly DevUI REST API reference, CLI options, and .NET integration.
+
+| Library ID                                        | Use for                                                                        |
+| ------------------------------------------------- | ------------------------------------------------------------------------------ |
+| `/websites/learn_microsoft_en-us_agent-framework` | Tutorials — DevUI guides, tracing, workflow orchestration                      |
+| `/microsoft/agent-framework`                      | API detail — DevUI REST endpoints, CLI flags, auth, .NET `AddDevUI`/`MapDevUI` |
+
+**DevUI tip:** Query the Learn website source for how-to guides, then the repo source for API-level specifics (endpoint schemas, proxy config, auth tokens).
+
+---
+
+## Context7 Setup
+
+For any Context7 query, resolve the library ID first (one-time per session):
+
+1. Call `mcp_context7_resolve-library-id` with the technology name
+2. Call `mcp_context7_query-docs` with the returned library ID and a specific query
+
+---
+
+## Writing Effective Queries
+
+Be specific — include version, intent, and language:
+
+```
+# ❌ Too broad
+"Azure Functions"
+"agent framework"
+
+# ✅ Specific
+"Azure Functions Python v2 programming model"
+"Cosmos DB partition key design best practices"
+"GitHub Actions workflow_dispatch inputs matrix strategy"
+"Aspire AddUvicornApp Python FastAPI integration"
+"DevUI serve agents tracing OpenTelemetry directory discovery"
+"Agent Framework workflow conditional edges branching handoff"
+```
+
+Include context:
+
+- **Version** when relevant (`.NET 8`, `Aspire 13`, `VS Code 1.96`)
+- **Task intent** (`quickstart`, `tutorial`, `overview`, `limits`, `API reference`)
+- **Language** for polyglot docs (`Python`, `TypeScript`, `C#`)

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

@@ -0,0 +1,171 @@
+---
+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..."