keel-coverage

Compute test coverage deltas for pull requests and create issues for low-coverage hot spots.

4|Updated May 23, 2026

Search Tags:#test automation #pull request #coverage #issue creation #hot spot

Ready to run

npx skills add https://github.com/berkayturanci/keel --skill keel-coverage

💬 Prompt for ChatGPT / Claude Chat▼

Please help me install this Agent Skill.
Skill: keel-coverage
Source: https://github.com/berkayturanci/keel/tree/main/.agents/skills/keel-coverage
Command: npx skills add https://github.com/berkayturanci/keel --skill keel-coverage

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes scripts (resource) components.

What problem does it solve?

This Skill computes and posts the test coverage delta for pull requests, flags low-coverage hot spots, and opens issues to close gaps.

Core Features & Use Cases

Coverage Delta: Calculates the difference in test coverage between the base branch and the pull request head.
Hot Spot Flagging: Identifies files with low coverage and high risk, flagging them for attention.
Issue Creation: Automatically creates issues for hot spots, routing them to the appropriate workflow.

Quick Start

Run the keel coverage command to compute and post the coverage delta for the current pull request.

Frequently Asked Questions about keel-coverage

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

FAQPage Schema

How do I calculate test coverage delta for a pull request?▼

To calculate test coverage delta for a pull request, you run the `keel coverage` command to compute the difference in test coverage between the base branch and the PR head. It evaluates the codebase and project configuration to determine the exact percentage change.

What is a test coverage hot spot and how is it flagged?▼

A test coverage hot spot is a file with low coverage and high risk. The Skill flags these hot spots by analyzing the pull request codebase to identify areas lacking sufficient test coverage, ensuring they receive immediate attention before merging.

Can I automatically create issues for low coverage files in my pull request?▼

Yes, you can automatically create issues for low coverage files. The Skill identifies hot spots in the pull request and opens issues for them, routing the low coverage gaps directly into your project's workflow for resolution.

Do I need project configuration access to post PR test coverage results?▼

Yes, you need access to the PR's codebase and project configuration to post PR test coverage results. This access allows the Skill to accurately compute the coverage delta between the base branch and the pull request head.

What's the best way to track test automation gaps on new pull requests?▼

The best way to track test automation gaps on new pull requests is by computing the coverage delta and automatically flagging hot spots. This approach identifies files with low coverage and creates issues to close the testing gaps before integration.