e2e-template-testing

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

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

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 Verification: 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 repos, runs squad init, and executes real Copilot CLI sessions with --allow-all-tools to exercise modified templates. - PR Progress Reporting: Posts and updates a live tracking comment on the PR with per-step status, progressive per-scenario verdicts, and a final verdict table. - Use Case: After editing .squad-templates/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 verify state landed in the expected git-notes location. ## Quick Start Ask the agent to run end-to-end validation of your squad template changes by building the local CLI, initializing a disposable test repo, and running a Copilot squad session with verdicts posted 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 and link the squad CLI from your feature branch, create a disposable git test repo, run squad init, then execute a real session with copilot --agent squad --allow-all-tools. Verify the outcome by checking 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 because confirmation prompts cannot be displayed. Always pass --allow-all-tools (or set COPILOT_ALLOW_ALL=1) when using the -p flag, otherwise file writes fail silently or with a permission error.

How do I make the squad command use my local build instead of the published package?

Run npm run build for the sdk and 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 global package is still active.

Can I run multiple copilot squad sessions in one agent run?

No. Background agents lose their AI model connection after roughly 15 minutes, and each copilot session takes 5-15 minutes. Limit yourself to one copilot session per agent and split additional scenarios into parallel agents.

What should I do when the squad CLI build fails during E2E validation?

Stop immediately and report BUILD_FAILED rather than skipping scenarios. If the error is a missing binary like tsc, run npm install to reconcile node_modules with the lock file, clean any stale SDK copy under packages/squad-cli/node_modules, then retry the build.