e2e-template-testing

Validates coordinator and agent template changes through real end-to-end squad sessions.

1|Updated Jul 7, 2026
One-click install
npx skills add https://github.com/seiggy/maf-copilot-studio-demo --skill e2e-template-testing-seiggy
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: e2e-template-testing
Source: https://github.com/seiggy/maf-copilot-studio-demo/tree/main/.squad/templates/skills/e2e-template-testing
Command: npx skills add https://github.com/seiggy/maf-copilot-studio-demo --skill e2e-template-testing-seiggy

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve? Prompt-level changes to coordinator and agent templates cannot be caught by unit tests because the prompts are interpreted by an LLM at runtime, so regressions only surface during real sessions. This Skill provides a repeatable end-to-end workflow for validating template changes against a locally built CLI before merging. ## Core Features & Use Cases - Local Build Validation: Builds and links the squad CLI from your feature branch, with fast-fail checks that stop the run on build, link, or version errors. - Disposable Test Repos: Creates isolated git repositories, runs squad init, and executes real Copilot CLI sessions with --allow-all-tools to verify template behavior. - PR Progress Reporting: Posts and updates a live tracking comment on the pull request with per-step status, durations, and progressive per-scenario verdicts. - Use Case: After editing squad.agent.md to add state-backend-aware spawn logic, run this Skill to build the CLI, init a test squad, run a coordinator session, and confirm state lands in the expected git-notes location with evidence posted to the PR. ## Quick Start Ask the agent to run end-to-end validation of your squad template changes on the current feature branch and post progress to the open PR.

Frequently Asked Questions about e2e-template-testing

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I test squad template changes end-to-end?

Build and link the CLI from your feature branch with npm, create a disposable git test repo, run squad init, then execute a real session using copilot --agent squad --allow-all-tools. Verify outcomes via git state and session logs, then record a verdict.

Why does copilot CLI fail with permission denied in non-interactive mode?

The Copilot CLI requires explicit tool permission in non-interactive mode. Always pass --allow-all-tools (or set COPILOT_ALLOW_ALL=1) with the -p flag, otherwise tool calls like file writes block on confirmation prompts that cannot be displayed.

How many copilot sessions can one agent run in E2E testing?

Limit each agent to one scenario containing a copilot --agent squad session, since background agents lose their AI model connection after roughly 15 minutes. Run additional session scenarios in separate parallel agents and batch up to four static-only scenarios per agent.

How do I post E2E progress comments to a GitHub PR?

Post an initial all-pending tracking comment with gh api before any other step, capture the comment ID, then PATCH it in place at each step boundary. On Windows PowerShell 5.1, write the body to a UTF-8 file without BOM and use --field body=@file.

What should I do when the squad build fails before E2E runs?

Stop immediately and report BUILD_FAILED rather than skipping scenarios. First remove any stale @bradygaster/squad-sdk copy under packages/squad-cli/node_modules, run npm install if binaries like tsc are missing, then retry the build.