Codex Choose Meeting Transcriber UI and Release Harness Checks
Select Python, browser UI, or harness verification for a Meeting Transcriber change and make results auditable.
中文Install in Codex
Use a local Meeting Transcriber checkout, development dependencies, and relevant test fixtures.
- Copy the pinned `.codex/skills/meeting-transcriber-release-harness/` directory into `.agents/skills/meeting-transcriber-release-harness/` in the project.
- Read `docs/STATUS.md`, `harness/README.md`, and the touched source and tests in Codex.
Example task
For a fictional empty-state copy change, choose the existing `pytest -m ui` test covering that view and report what actually passed.What to check
The report identifies the behavior, relevant test, and result. Release-level checks have their own status.
Original SKILL.md on GitHub · Updated
Frequently asked question
When should I use `pytest -m harness -q`?
Run the current project harness gate when the change affects release evidence or the harness itself, and record the result.