Motivation
github/gh-aw#41459 — copilot engine: launch from ${GITHUB_WORKSPACE} to enable APM skill discovery
Before this fix, gh-aw launched the Copilot engine outside the workspace and passed skills via --add-dir, which does not register skill roots. APM-restored skills under .agents/skills were present on disk but invisible to the agent. The fix changes the engine launch directory to ${GITHUB_WORKSPACE}.
No E2E test exercises APM skill delivery or verifies that a skill placed in .agents/skills is discoverable by the Copilot engine.
Proposed test
- Workflow file:
test-copilot-apm-skill-discovery.md
- Trigger:
workflow_dispatch
- Engine: copilot (feature is Copilot-specific — APM is a Copilot SDK concept)
- Safe output:
create-issue
- Variant: standard
Minimal test prompt sketch
Pre-install a minimal skill definition under .agents/skills/<skill-name>/ in the test repo. Trigger a workflow that asks the Copilot agent to invoke that skill (e.g., a skill that returns a known string). The agent creates an issue containing the skill's response, confirming discovery and invocation succeeded.
New fixtures or secrets needed
New fixtures required: A minimal APM-compatible skill definition must be committed to githubnext/gh-aw-test under .agents/skills/. The skill needs to be structurally valid for the Copilot SDK's APM loader. The exact schema should be confirmed against the APM skill format before adding the fixture.
No new secrets needed — the test uses the standard copilot engine credentials already configured in the repo.
Notes
- This is a Copilot-only feature; no
claude/codex variants needed.
- The fixture complexity (skill definition format, APM loader requirements) is the main open question. If the skill schema is trivial, this could be promoted to a PR.
- Consider whether the skill fixture should live in
trials/ (scratch, ignored by tests) or at the real .agents/skills/ path required for discovery.
Generated by 🔍 Suggest New E2E Tests · 63.9 AIC · ⌖ 11.9 AIC · ⊞ 5.9K · ◷
Motivation
github/gh-aw#41459 — copilot engine: launch from
${GITHUB_WORKSPACE}to enable APM skill discoveryBefore this fix, gh-aw launched the Copilot engine outside the workspace and passed skills via
--add-dir, which does not register skill roots. APM-restored skills under.agents/skillswere present on disk but invisible to the agent. The fix changes the engine launch directory to${GITHUB_WORKSPACE}.No E2E test exercises APM skill delivery or verifies that a skill placed in
.agents/skillsis discoverable by the Copilot engine.Proposed test
test-copilot-apm-skill-discovery.mdworkflow_dispatchcreate-issueMinimal test prompt sketch
Pre-install a minimal skill definition under
.agents/skills/<skill-name>/in the test repo. Trigger a workflow that asks the Copilot agent to invoke that skill (e.g., a skill that returns a known string). The agent creates an issue containing the skill's response, confirming discovery and invocation succeeded.New fixtures or secrets needed
New fixtures required: A minimal APM-compatible skill definition must be committed to
githubnext/gh-aw-testunder.agents/skills/. The skill needs to be structurally valid for the Copilot SDK's APM loader. The exact schema should be confirmed against the APM skill format before adding the fixture.No new secrets needed — the test uses the standard
copilotengine credentials already configured in the repo.Notes
claude/codexvariants needed.trials/(scratch, ignored by tests) or at the real.agents/skills/path required for discovery.