device-lane-proof

Use when a change touches device or Appium behaviour (driver, gestures, locators, ios/adb helpers, runner) and the Definition of Done requires running the focused device lane, or when a PR needs on-device screenshot proof. Explains how to run a real spec on a booted simulator/emulator and where the evidence lands.

Ir para a instalação

Repositório: BenSheridanEdwards/NativeProof
Última atividade na origem: 7 de julho de 2026 às 12:43
Idioma detectado do SKILL.md: inglês
Estrelas: 1
Forks: 2

Opções de instalação

Por padrão, está selecionado o prompt que primeiro revisa a origem. Você pode mudar para um comando direto ou baixar uma cópia local.

Instalar com Codex ou Claude Copie este prompt, cole no Codex, Claude ou outro assistente e deixe que ele revise a página da skill e instale para você.

Um comando direto ignora o prompt de revisão. Verifique a origem antes de executá-lo.

npx skills add https://github.com/BenSheridanEdwards/NativeProof --skill device-lane-proof

O comando permanece em uma só linha. Role horizontalmente para revisá-lo antes de copiar.

Prefere uma cópia local? Baixe os arquivos disponíveis atualmente no SkillsMP.

Revise os arquivos de origem

Leia o SKILL.md e os arquivos complementares exibidos pelo SkillsMP antes de decidir se vai instalar.

SKILL.md

Instruções da origem · Visualização somente leitura

Voltar à pesquisa Voltar à instalação

release-changelog

Use when cutting a NativeProof release, bumping the package version, or writing a CHANGELOG entry. Covers the Keep a Changelog entry format and the GitHub-Release-driven npm publish flow.

2026-07-07

verify-generated-project

Use when a change touches the CLI, init/onboard scaffolding, or the generated project surface (src/cli.ts, templates, runner-config) and the Definition of Done requires proof that the generated project still works. Produces that proof from the packed tarball, not from the repo checkout.

2026-07-07

pr-inline-screenshot-proof

Use when opening or updating a GitHub pull request that needs screenshots, videos, or proof artifacts rendered inline in the PR description instead of shown as plain links.

2026-07-01

Ver todas deste repositório

Device Lane Proof

Unit tests fake the driver; they cannot prove that a gesture lands on a real screen. The Definition of Done requires the focused device lane for device/Appium behaviour changes — a real spec, on a real booted target, exercising exactly the changed behaviour. "Focused" means one small spec that hits the change, not the whole suite.

Required Pattern

Confirm a booted target exists:

xcrun simctl list devices booted   # iOS: expect at least one Booted device
adb devices                        # Android: expect a device/emulator line

No booted target and no way to boot one? Stop and write the exact reason in the PR ("Full device coverage not run: ..."). Do not fake the lane.

Get a runnable project pointed at a real app artifact. Either reuse an existing local E2E project, or scaffold one from the packed tarball (see .agents/skills/verify-generated-project/SKILL.md) and run nativeproof onboard <path-to-.app|.apk|ios-repo>.

Write or adapt one focused spec that exercises the changed behaviour using direct native.* calls and plain expect, then run it:

npx nativeproof --ios     # or --android

Collect evidence. NativeProof writes a screenshot + redacted page-source pair for every meaningful step into .e2e-artifacts/ (or the configured artifacts.dir). Pick the screenshots that show the changed behaviour.

Commit the chosen screenshots under docs/proof/<short-scope>/ on the PR branch and embed them inline per .agents/skills/pr-inline-screenshot-proof/SKILL.md. Include the exact command run and its pass/fail output in the PR proof section.

Hard Failures

Proof screenshots taken from a fake/mock driver run — the lane exists precisely because mocks cannot prove device behaviour.

Running the lane against an app or spec that never exercises the changed code path.

Silently skipping the lane. Skipping is allowed; hiding the skip is not — the PR must state why it was not run.

Verification

The spec run exits 0 (or the failure is the point and is explained), .e2e-artifacts/ contains the step screenshots, and the PR body embeds the relevant ones inline with ![alt](...png?raw=1).