How do I install the Restassured CI skill?

Run npx skillmds@latest add jovd83/restassured-ci 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 CI 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 CI?

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 CI free to use?

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

Who published Restassured CI?

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

Restassured CI by jovd83 — Agent Skill

Name: Restassured CI
Author: jovd83

File contents

Rest Assured CI

1. Choose The Pipeline Shape

Detect the CI system first.
Run smoke tags before full regression when pipeline time matters.
Use containers or disposable services for integration tests.

2. Configure Execution

Use provider guidance from github-actions.md, gitlab.md, or other-ci.md.
Use junit5-tagging-and-suites.md for JUnit 5 selection.
Use docker-and-containers.md for containerized execution.
Use parallelization.md for sharding or split-by-tag execution.
Use reporting-and-artifacts.md for JUnit XML and logs.
Use quality-gates.md when the pipeline must fail on coverage, drift, or weak-assertion thresholds.
Use python scripts/evaluate_quality_gates.py when the quality-gate evaluation must be deterministic and reusable across CI jobs.

3. Add Quality Gates

Fail the pipeline on contract-enforcement regressions only when the repo has explicitly opted into strict gates.
Use the coverage-gap report to enforce no uncovered operations or no unreviewed drift-only operations when the team wants coverage hardening.
Use the assertion-strength report to enforce thresholds such as no weak tests or max transport-only tests.
Keep quality gates separate for runtime-aligned suites and contract-enforcement suites when both exist.
Regenerate the reporting bundle before applying report-based gates.
Prefer python scripts/evaluate_quality_gates.py --coverage-gap <gap-md> --assertion-strength <strength-md> --contract-mismatches <mismatch-md> instead of rewriting threshold logic inline in CI YAML.

4. Troubleshooting

Problem: CI cannot reach the service under test. Fix: Verify network, startup ordering, and environment variables before changing the tests.
Problem: Tag-based selection runs zero tests. Fix: Verify JUnit 5 tag configuration and test task flags.
Problem: The pipeline fails because report-based gates are stale. Fix: Regenerate the bundle reports before evaluating gate thresholds.
Problem: CI duplicates threshold logic in multiple jobs. Fix: Move the evaluation into scripts/evaluate_quality_gates.py.

---name: restassured-cidescription: Use when Codex needs to configure or troubleshoot Rest Assured API tests in CI pipelines, including JUnit 5 execution, tags, Docker, containers, artifacts, quality gates, and provider-specific pipeline examples.---# Rest Assured CI## 1. Choose The Pipeline Shape1. Detect the CI system first.2. Run smoke tags before full regression when pipeline time matters.3. Use containers or disposable services for integration tests.## 2. Configure Execution1. Use provider guidance from [github-actions.md](references/github-actions.md), [gitlab.md](references/gitlab.md), or [other-ci.md](references/other-ci.md).2. Use [junit5-tagging-and-suites.md](references/junit5-tagging-and-suites.md) for JUnit 5 selection.3. Use [docker-and-containers.md](references/docker-and-containers.md) for containerized execution.4. Use [parallelization.md](references/parallelization.md) for sharding or split-by-tag execution.5. Use [reporting-and-artifacts.md](references/reporting-and-artifacts.md) for JUnit XML and logs.6. Use [quality-gates.md](references/quality-gates.md) when the pipeline must fail on coverage, drift, or weak-assertion thresholds.7. Use `python scripts/evaluate_quality_gates.py` when the quality-gate evaluation must be deterministic and reusable across CI jobs.## 3. Add Quality Gates1. Fail the pipeline on contract-enforcement regressions only when the repo has explicitly opted into strict gates.2. Use the coverage-gap report to enforce `no uncovered operations` or `no unreviewed drift-only operations` when the team wants coverage hardening.3. Use the assertion-strength report to enforce thresholds such as `no weak tests` or `max transport-only tests`.4. Keep quality gates separate for runtime-aligned suites and contract-enforcement suites when both exist.5. Regenerate the reporting bundle before applying report-based gates.6. Prefer `python scripts/evaluate_quality_gates.py --coverage-gap <gap-md> --assertion-strength <strength-md> --contract-mismatches <mismatch-md>` instead of rewriting threshold logic inline in CI YAML.## 4. Troubleshooting1. Problem: CI cannot reach the service under test. Fix: Verify network, startup ordering, and environment variables before changing the tests.2. Problem: Tag-based selection runs zero tests. Fix: Verify JUnit 5 tag configuration and test task flags.3. Problem: The pipeline fails because report-based gates are stale. Fix: Regenerate the bundle reports before evaluating gate thresholds.4. Problem: CI duplicates threshold logic in multiple jobs. Fix: Move the evaluation into `scripts/evaluate_quality_gates.py`.

Frequently asked questions

Restassured CI