You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Add focused iOS Simulator and Android Emulator skills for agent-device, and link them from AI Agent Setup.
Keep the new source-distributed skills out of the npm tarball by limiting the package allowlist to the existing packaged skills.
Validation
pnpm check:affected --run in a clean temporary worktree (all runnable checks passed).
npm pack --dry-run --json --ignore-scripts confirmed only skills/agent-device and skills/dogfood are packaged.
The normal worktree contains unrelated local .claude/worktrees fixtures with intentionally invalid YAML, so its full formatter cannot be used as validation for this docs/packaging-only change.
Exact-head review at 607becee9: not ready. The source-distributed skill/package scope is coherent, documented command shapes match the shipped CLI/help contract, and no device evidence is required for this skill/docs/metadata-only change. P2 validation gap: both new files add command-planning guidance, but there is no required help-conformance case or structural skill-contract regression for either one; the existing help-conformance test is hard-wired only to skills/agent-device/SKILL.md. Add focused iOS/Android cases that prove the skill selects the requested platform, starts a known app with foreground snapshot composition, grounds actions in current refs/selectors, verifies, and closes, and demonstrate the gate fails when that key guidance is removed or corrupted. Completed checks are green; Android/iOS smokes are still pending. No ready label applied.
Exact-head re-review at 1487f873: the updated iOS/Android skill wording accurately matches the CLI contract, all checks are green, and removing the unused OpenAI metadata is fine. The prior P2 remains: this delta adds no help-conformance or structural skill-contract coverage. The existing harness is hard-wired to skills/agent-device/SKILL.md, so either new simulator skill can lose/corrupt its platform selection, foreground-open/snapshot, current-ref/selector, settle/type, verify, or close guidance without a gate failing.
Add focused iOS and Android conformance cases and a planted-red proof for each required skill contract. No device evidence is needed for this docs/skill-only change; no ready label applied.
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Summary
Add focused iOS Simulator and Android Emulator skills for agent-device, and link them from AI Agent Setup.
Keep the new source-distributed skills out of the npm tarball by limiting the package allowlist to the existing packaged skills.
Validation
pnpm check:affected --runin a clean temporary worktree (all runnable checks passed).npm pack --dry-run --json --ignore-scriptsconfirmed onlyskills/agent-deviceandskills/dogfoodare packaged.The normal worktree contains unrelated local
.claude/worktreesfixtures with intentionally invalid YAML, so its full formatter cannot be used as validation for this docs/packaging-only change.