test-coverage-improver Skill
Improve test coverage in the OpenAI Agents JS monorepo: run pnpm test:coverage, inspect coverage artifacts, identify low-coverage files and branches, propose high-impact tests, and confirm with the user before writing tests. Published by openai in openai-agents-js.
Decision snapshot
Is this a fit?
Testing, Writing, Includes SKILL.md, Reusable instructions
Compatibility not yet detected.
Permission behavior not yet detected.
Copy skill directory
20 days ago · MIT license
No specific cautions were detected. Review the source and requested permissions before installing.
What is test-coverage-improver Skill?
Improve test coverage in the OpenAI Agents JS monorepo: run pnpm test:coverage, inspect coverage artifacts, identify low-coverage files and branches, propose high-impact tests, and confirm with the user before writing tests. Published by openai in openai-agents-js. This profile combines repository metadata with install, compatibility, and usage signals so developers can quickly decide whether it fits their agent workflow before opening the source repository.
Automated repository signals based on public metadata such as recency, license, installation evidence, and adoption. These are not a security audit or endorsement. See how SkillIndex evaluates profiles.
Key capabilities
- Includes SKILL.md support
- Reusable instructions support
- Testing
- Writing
- Testing use cases
- Writing use cases
Declared skill metadata
- Source file: .agents/skills/test-coverage-improver/SKILL.md
These fields retain source and confidence evidence from the indexed SKILL.md.
Compatibility and setup
- Install or run with Copy skill directory
When to use test-coverage-improver Skill
- Use it for testing.
- Use it for writing.
Built with
Editorial notes
Source
- Creator: openai
- Repository: openai/openai-agents-js
- Skill file: .agents/skills/test-coverage-improver/SKILL.md
What it does
Improve test coverage in the OpenAI Agents JS monorepo: run pnpm test:coverage, inspect coverage artifacts, identify low-coverage files and branches, propose high-impact tests, and confirm with the user before writing tests.
Skill instructions
Test Coverage Improver Overview Use this skill whenever coverage needs assessment or improvement (coverage regressions, failing thresholds, or user requests for stronger tests). It runs the coverage suite, analyzes results, highlights the biggest gaps, and prepares test additions while confirming with the user before changing code. Quick Start 1. From the repo root run pnpm test:coverage to regenerate coverage/. 2. Collect artifacts: coverage/coverage-summary.json (preferred) or coverage/coverage-final.json, plus coverage/lcov.info and coverage/lcov-report/index.html for drill-downs. 3. Summarize coverage: total percentages, lowest files, branches under 80%, and uncovered lines/paths. 4. Draft test ideas per file: scenario, behavior under test, expected outcome, and likely coverage gain. 5. Ask the user for approval to implement the proposed tests; pause until they agree. 6. After approval, write the tests in the relevant package, rerun pnpm test:coverage, and then run $code-change-ver
Verified compatibility and discovery
Frequently asked questions
What is test-coverage-improver?
test-coverage-improver is a open-source AI agent skill with Copy skill directory. Improve test coverage in the OpenAI Agents JS monorepo: run pnpm test:coverage, inspect coverage artifacts, identify low-coverage files and branches, propose high-impact tests, and confirm with.
Who is test-coverage-improver best for?
test-coverage-improver is best for reusing agent instructions, scripts, and references, testing workflows, writing workflows.
How do I install test-coverage-improver?
Install or run test-coverage-improver using Copy skill directory. Check test-coverage-improver for the latest setup command.
Is test-coverage-improver actively maintained?
test-coverage-improver may need a closer maintenance check before production use.
Project health auto-fetched from the source repository.
Maintain this resource?
Review this source-backed profile, send a correction with evidence, or link to it from your documentation. Claims verify your relationship to the project; profile facts still require source evidence and editorial review.
