# Test Coverage > Testing expectations for AIRBot reviewers Use when this capability is needed. - Skill: `tomevault-io/test-coverage` (Agent Skill, multi-file: 2 files) - Install (CLI): `npx skillmds@latest add tomevault-io/test-coverage` - Raw SKILL.md: https://api.skillmd.com/api/skills/tomevault-io/test-coverage/raw - Safety review: pending (external: skill-scanner PASS, skillspector PASS) - Works with: Claude Code, Claude.ai, OpenAI Codex - Category: Coding & Dev Tools - Author: tomevault-io (https://skillmd.com/u/tomevault-io) - Updated: 2026-09-17 - Page: https://skillmd.com/skills/tomevault-io/test-coverage --- ## Mission - Ensure pull requests maintain or improve automated test coverage and reliability. - Highlight missing regression tests, flaky patterns, or gaps in the review workflow. ## When to Block - Production code changes without corresponding tests or documented rationale. - Failing or removed tests without replacement coverage. - Async logic, parsers, or critical flows introduced with no deterministic assertions. ## Checklist - Identify impacted modules via diff; confirm matching updates under `tests/` or a justified explanation. - Require Bun test fixtures close to their source modules; suggest new files under `tests/`. - Encourage fast, deterministic tests: avoid sleeping, network calls, or reliance on local environment state. - Verify mocks and stubs cover both success and failure paths, especially around GitHub and Claude SDK interactions. - Promote table-driven tests for parsing, dedupe, and formatting utilities. - Ask for regression coverage when fixing a bug; tests should fail before the fix and pass after. ## Tooling Tips - `Read` edited test files to confirm assertions exercise new code. - `Glob` for `*.test.ts` near touched modules to gauge existing coverage. - `Grep` for TODOs or `skip` calls that might hide missing coverage. --- > Converted and distributed by [TomeVault](https://tomevault.io/claim/sids) — claim your Tome and manage your conversions.