integration

Catalog integration tests, models, and entry points in jre-vidget.

Updated May 3, 2026
One-click install
npx skills add https://github.com/jreakin/jre-vidget --skill integration-jreakin
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: integration
Source: https://github.com/jreakin/jre-vidget/tree/main/.claude/skills/generated/integration
Command: npx skills add https://github.com/jreakin/jre-vidget --skill integration-jreakin

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

The Integration skill captures and communicates the scope of integration tests in the jre-vidget project, mapping tests, models, and entry points to a concise reference.

Core Features & Use Cases

  • Documentation of test surfaces: lists key tests like test_app_config_roundtrip, test_url_construction, and test_youtube_cli integration to guide developers.
  • Easy navigation: highlights core files, symbols, and entry points to accelerate onboarding and debugging.
  • Use Case: When adding new integration tests, this skill helps locate related models and test flows to ensure coverage remains comprehensive.

Quick Start

Run the integration test suite to validate configuration round-trip and publish workflows.

Frequently Asked Questions about integration

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

FAQPage Schema
How do I document integration test coverage for a Python project?

Documenting integration test coverage involves cataloging test names, models, and entry points to map execution flows. This skill summarizes the integration test surface by listing key tests like test_app_config_roundtrip to guide developers on test scope and dependencies.

How do I map integration test entry points and key symbols?

Mapping integration test entry points requires highlighting core files and symbols to accelerate onboarding. It catalogs tests like test_url_construction and test_youtube_cli, providing a consistent schema to document test scope and execution flows for developer orientation.

What is the best way to orient on existing integration tests before adding new ones?

Orienting on existing integration tests helps locate related models and test flows to ensure comprehensive coverage. By cataloging tests and entry points in a concise reference, developers can quickly navigate test surfaces and verify dependencies before adding new integration tests.

Does this integration testing documentation approach work for configuration round-trip workflows?

This integration testing documentation approach works for configuration round-trip workflows by validating and documenting test execution flows. It captures the scope of integration tests, ensuring configuration round-trip and publish workflows are mapped to a consistent reference schema.

When do I need to catalog integration test surfaces in software engineering?

You need to catalog integration test surfaces when a developer requires quick orientation on test entry points and key symbols. It satisfies software-engineering requirements to document test scope, dependencies, and execution flows consistently when adding or modifying integration tests.