How do I install the Restassured Documentation Coverage Gap Report skill?

Run npx skillmds@latest add jovd83/restassured-documentation-coverage-gap-report in your terminal (requires Node.js), paste this page's agent-chat prompt into Claude, Cursor, or any MCP-connected agent, or download the SKILL.md file and copy it into your agent's skills directory.

Is Restassured Documentation Coverage Gap Report safe to use?

This skill has not completed SkillMD's automated safety review yet. SkillMD never runs a skill's scripts for you; review the SKILL.md before installing.

Which AI agents work with Restassured Documentation Coverage Gap Report?

This skill is tagged as working with Claude Code, Claude.ai, OpenAI Codex. SKILL.md is an open format, so most agents that read a skills directory can load it too.

Is Restassured Documentation Coverage Gap Report free to use?

Yes. Installing skills from SkillMD is free, and the skill stays under its author's original license.

Who published Restassured Documentation Coverage Gap Report?

jovd83 (@jovd83) published this skill. Their other Agent Skills are listed on their SkillMD profile.

Restassured Documentation Coverage Gap Report by jovd83

Name: Restassured Documentation Coverage Gap Report
Author: jovd83

Restassured Documentation Coverage Gap Report

Use when Codex needs to highlight uncovered, partial, drift-only, or weakly covered API areas so humans can prioritize the next Rest Assured work instead of reading the full traceability report.

jovd83 a0ae5e8 4 files · 14.3 KB Updated Sep 17, 2026

File contents

Build Coverage Gap Report

1. Gather Inputs

Require the current docs/testing/test-mapping-report.md.
Require docs/testing/contract-mismatches.md when it exists.
Require the active coverage matrices when they contain gaps not yet reflected in traceability.

2. Choose The Files

Prefer docs/testing/coverage-gap-report.md.
When the user wants human-friendly navigation, also generate docs/testing/html/coverage-gap-report.html.

3. Build The Report

Treat Not covered, Partial, and Contract drift operations as primary gaps.
Include explicit gap bullets from the traceability report.
Separate the report into summary, operation gaps, and planning recommendations.
Keep one operation row per endpoint and method in markdown.
In HTML, group the operation gaps by resource and make the next action obvious.

4. Output Shape

Start from coverage-gap-report-template.md.
Keep the exact section headings so the generator can update the file deterministically.
Run python scripts/generate_coverage_gap_report.py --mapping <mapping-md> --output-md <gap-md> --output-html <gap-html>.

5. Keep It Actionable

Explain why each gap matters.
Recommend the next slice to implement.
Update the session-state artifact after generating or changing the report.

6. Examples

Input: Show me the biggest API coverage gaps. Output: Create docs/testing/coverage-gap-report.md and the paired HTML report.
Input: Which endpoints are only covered through drift assertions? Output: Produce a gap report that isolates Contract drift operations and suggests next actions.

7. Troubleshooting

Problem: The traceability report says everything is covered. Fix: Still surface Contract drift rows and explicit gap bullets because those are planning gaps.
Problem: The markdown and HTML disagree. Fix: Regenerate the HTML from the canonical markdown inputs and do not hand-edit the HTML.

---name: restassured-documentation-coverage-gap-reportdescription: Use when Codex needs to highlight uncovered, partial, drift-only, or weakly covered API areas so humans can prioritize the next Rest Assured work instead of reading the full traceability report.---# Build Coverage Gap Report## 1. Gather Inputs1. Require the current `docs/testing/test-mapping-report.md`.2. Require `docs/testing/contract-mismatches.md` when it exists.3. Require the active coverage matrices when they contain gaps not yet reflected in traceability.## 2. Choose The Files1. Prefer `docs/testing/coverage-gap-report.md`.2. When the user wants human-friendly navigation, also generate `docs/testing/html/coverage-gap-report.html`.## 3. Build The Report1. Treat `Not covered`, `Partial`, and `Contract drift` operations as primary gaps.2. Include explicit gap bullets from the traceability report.3. Separate the report into summary, operation gaps, and planning recommendations.4. Keep one operation row per endpoint and method in markdown.5. In HTML, group the operation gaps by resource and make the next action obvious.## 4. Output Shape1. Start from [coverage-gap-report-template.md](assets/coverage-gap-report-template.md).2. Keep the exact section headings so the generator can update the file deterministically.3. Run `python scripts/generate_coverage_gap_report.py --mapping <mapping-md> --output-md <gap-md> --output-html <gap-html>`.## 5. Keep It Actionable1. Explain why each gap matters.2. Recommend the next slice to implement.3. Update the session-state artifact after generating or changing the report.## 6. Examples1. Input: `Show me the biggest API coverage gaps.` Output: Create `docs/testing/coverage-gap-report.md` and the paired HTML report.2. Input: `Which endpoints are only covered through drift assertions?` Output: Produce a gap report that isolates `Contract drift` operations and suggests next actions.## 7. Troubleshooting1. Problem: The traceability report says everything is covered. Fix: Still surface `Contract drift` rows and explicit gap bullets because those are planning gaps.2. Problem: The markdown and HTML disagree. Fix: Regenerate the HTML from the canonical markdown inputs and do not hand-edit the HTML.

Frequently asked questions