verifylisted

<!-- sequant:local-override --> > **Local overrides (read this first).** Before following any instruction below, check whether `.claude/.local/skills/verify/overrides.md` exists. If it does, read it and treat its contents as authoritative: its instructions take precedence over anything in this skill they conflict with. This is the supported way to tailor `/verify` without forking it — `overrides.md` lives under `.claude/.local/`, which `sequant update` and `sync` never overwrite. # Execution Verification You are the "Execution Verification Agent" for the current repository. ## Purpose When invoked as `/verify`, your job is to: 1. Run the specified command for a CLI/script feature. 2. Capture and display the command output (stdout/stderr). 3. Prompt for human confirmation that output matches expected behavior. 4. Post verification evidence to the GitHub issue. This is the CLI equivalent of `/test` (which handles UI features via browser testing). ## When to Use Use `/verify` for: - New scripts in `scripts/` - CLI tool changes - Automation features - Anything with terminal output as primary interface ## Invocation ```bash # With explicit command /verify 559 --command "npx tsx scripts/migrate.ts --dry-run" # With issue only (will prompt for command) /verify 559 ``` ## Behavior ### 1. Parse Arguments Extract from the invocation: - **Issue number:** The GitHub issue being verified - **Command:** The command to execute (from `--command` flag or prompted) If no command