test-coverage-improver

Run pnpm test:coverage, analyze coverage gaps, and propose high-impact tests.

Updated Aug 27, 2026
One-click install
npx skills add https://github.com/redacharf/fin-punk --skill test-coverage-improver-redacharf
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: test-coverage-improver
Source: https://github.com/redacharf/fin-punk/tree/main/.agents/skills/test-coverage-improver
Command: npx skills add https://github.com/redacharf/fin-punk --skill test-coverage-improver-redacharf

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

The OpenAI Agents JS monorepo often exhibits gaps in test coverage. This Skill streamlines the process of evaluating coverage, identifying weak areas, and coordinating with teammates to add high-impact tests.

Core Features & Use Cases

  • Automated coverage analysis: Run the coverage suite and summarize overall and per-file gaps.
  • Targeted test proposals: Highlight low-coverage files and branches and propose high-impact tests.
  • Change validation with user consent: Present a proposed test plan and pause for user approval before implementing tests.

Quick Start

Run the coverage workflow at the repo root and review the resulting summary before proposing tests.

Frequently Asked Questions about test-coverage-improver

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I identify test coverage gaps in a monorepo?

To identify test coverage gaps in a monorepo, run an automated test suite like pnpm test:coverage and analyze the resulting lcov reports and coverage-summary.json to detect untested files and branches.

How can I automatically generate tests to improve code coverage?

You can improve code coverage by analyzing coverage artifacts to pinpoint weak areas, then proposing targeted high-impact tests for those specific branches before pausing for user approval to implement them.

Does this test coverage analysis work with pnpm automated test suites?

Yes, this test coverage analysis works with pnpm automated test suites by running pnpm test:coverage and collecting artifacts like coverage-summary.json and lcov reports to evaluate per-file gaps in large codebases.

What is the best way to fix CI failures caused by low test coverage?

The best way to fix CI failures from low test coverage is to run coverage analysis, summarize per-file gaps, and propose high-impact tests that target the specific untested branches causing the threshold failure.

Can I review proposed tests before they are added to my codebase?

Yes, the workflow presents a proposed test plan targeting low-coverage files and pauses for explicit user approval before implementing any tests, ensuring you maintain control over codebase changes.