e2e-template-testing

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

2|Updated Jul 24, 2026
One-click install
npx skills add https://github.com/elbruno/ElBruno.MagenticUI --skill e2e-template-testing-elbruno
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: e2e-template-testing
Source: https://github.com/elbruno/ElBruno.MagenticUI/tree/main/.squad/templates/skills/e2e-template-testing
Command: npx skills add https://github.com/elbruno/ElBruno.MagenticUI --skill e2e-template-testing-elbruno

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve? Prompt-level changes to squad coordinator and agent charter 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 they ship. ## Core Features & Use Cases - Local build and link verification: Builds the squad SDK and CLI from your feature branch, links the CLI, and confirms the -preview version suffix so you test your changes rather than the published package. - Disposable test repo scenarios: Creates fresh git repos, runs squad init, executes real Copilot CLI sessions with --allow-all-tools, and verifies state landed in the expected location. - PR progress tracking and progressive verdicts: Posts a live tracking comment on the PR, updates it at every step boundary, and PATCHes each scenario verdict immediately so results survive connection drops. - Use Case: After editing squad.agent.md to add state-backend-aware spawn templates, run this Skill to build the CLI, spin up a test repo, run a coordinator session, and post a structured PASS/FAIL verdict table to the PR. ## Quick Start Ask the agent to run end-to-end validation of your squad template changes by building the local CLI, creating a disposable test repo, running a squad session, and posting the verdict to the 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 the squad SDK and CLI from your feature branch, link the CLI with npm link, then create a disposable git test repo and run squad init followed by a copilot --agent squad session. Verify the outcome by checking git state and session logs, then record a verdict.

How do I make the squad command use my local build?

Run npm run build for the squad-sdk and squad-cli workspaces, then npm link -w packages/squad-cli from the repo root. Verify with squad version, which must show a -preview suffix; a plain semver means the published package is still active.

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

The Copilot CLI requires explicit tool permission when running with the -p flag because interactive approval prompts cannot be displayed. Always pass --allow-all-tools or set COPILOT_ALLOW_ALL=1 so file writes and other tool calls execute without blocking.

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

Limit each agent run to one scenario that includes a copilot --agent squad session, because background agents lose their model connection after roughly 15 minutes. Run additional session scenarios in separate parallel agents and batch only static checks together.

Why should scenario verdicts be posted after each scenario instead of at the end?

The AI model connection can drop mid-run, which would lose all batched results. PATCHing the PR tracking comment immediately after each scenario guarantees the last successful state is always visible to reviewers.

What paths are safe to include in PR evidence comments?

Never post absolute paths containing a local username. Use ~ for home-relative paths and <repo-root> for paths inside the repository, scrubbing any machine-specific prefix before posting evidence tables or verdict files.