skills.rest
robinxin
robinxinCOMMUNITY
Explore all skills by this author →
GitHub

add-test-coverage

Analyzes the latest commit and generates a test plan with implementation for missing coverage.

Updated Aug 23, 2026
Search Tags:#git#unit-tests#integration-tests#e2e-tests#test-coverage#test-planning#head-commit
One-click install
npx skills add https://github.com/robinxin/AIFlomo --skill add-test-coverage-robinxin
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: add-test-coverage
Source: https://github.com/robinxin/AIFlomo/tree/main/.claude/skills/add-test-coverage
Command: npx skills add https://github.com/robinxin/AIFlomo --skill add-test-coverage-robinxin

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Analyze the most recent commit (HEAD) and implement all required tests to achieve comprehensive coverage, reducing regression risk across features and fixes.

Core Features & Use Cases

  • Detects changes introduced in HEAD (added, modified, deleted) and maps them to target test types (unit, integration, E2E).
  • Proposes and generates a concrete test plan, prioritizing safety-critical paths and areas with low coverage.
  • Implements tests following the repository's language and framework conventions, with clear documentation and summaries.

Quick Start

Run this skill after a feature is completed to produce a full test-coverage plan and the corresponding test additions.

Frequently Asked Questions about add-test-coverage

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

FAQPage Schema
How do I generate test coverage for my latest git commit?▼

Generate test coverage for a git commit by detecting HEAD changes, mapping them to unit, integration, or E2E tests, and implementing those tests following your repository's existing conventions and frameworks.

How do I create a test plan for new code changes?▼

Create a test plan by analyzing added, modified, or deleted files in the HEAD commit, prioritizing safety-critical paths and low-coverage areas, then mapping them to appropriate unit, integration, and E2E test types.

Can I automatically add unit and integration tests based on recent code changes?▼

Yes, you can automatically add unit and integration tests by analyzing the latest commit to identify coverage gaps and implementing tests that adapt to the repository's detected languages and frameworks.

Does test coverage generation work with any programming language and framework?▼

Test coverage generation works across detected languages and frameworks by adapting to the repository's specific tech stack and following existing test conventions to produce appropriate unit, integration, and E2E tests.

What's the best way to ensure new features have proper E2E test coverage?▼

The best way to ensure E2E test coverage is to run a post-commit analysis that detects HEAD changes, maps feature modifications to end-to-end test types, and generates tests with run commands and a coverage summary.

When should I run automated test generation after making code changes?▼

Run automated test generation immediately after a feature or fix is completed and committed, so the HEAD commit changes can be analyzed to produce a full test-coverage plan and corresponding test additions.

Related Skills

Explore More Software Engineering Skills→
heikopanjasheikopanjas

commit-all

Stage all working tree changes and create a conventional commit.

Community
Basic
hidonguyenhidonguyen

ck:test

Execute unit, integration, e2e, and UI tests across JavaScript/TypeScript, Python, Go, Rust, and Flutter projects.

Community
Advanced
Cbanzaime23Cbanzaime23

bmad-testarch-ci

Generate platform-specific CI pipelines for lint, test, shard, and artifact collection.

Community
Advanced
u9401066u9401066

test-generator

Generate pytest, mypy, ruff, bandit, and Playwright test suites for Python codebases.

Community
Advanced