update-integration-tests

Detects codebase changes and updates integration tests until the full suite passes.

Updated Jan 4, 2026
One-click install
npx skills add https://github.com/threadedstack/threadedstack --skill update-integration-tests-threadedstack
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: update-integration-tests
Source: https://github.com/threadedstack/threadedstack/tree/main/.claude/skills/update-integration-tests
Command: npx skills add https://github.com/threadedstack/threadedstack --skill update-integration-tests-threadedstack

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve? Keeping integration tests synchronized with ongoing code changes across a monorepo is tedious and error-prone, and failing tests often go uninvestigated. This Skill automates the entire loop: detecting changes, updating or creating tests, running the full suite, and fixing every failure. ## Core Features & Use Cases - Change Detection: Uses git diff commands to identify changed source files across sub-repos and maps them to existing test coverage. - Test Authoring: Updates outdated assertions or writes new Tier 1 (API contract) and Tier 3 (live infrastructure) tests following existing conventions. - Failure Resolution Loop: Runs the full vitest suite, diagnoses failures with proven root causes, fixes tests or application code, and iterates up to 5 cycles. - Use Case: After implementing a new API endpoint in the backend repo, invoke this Skill to generate integration tests for it, run the whole suite, and get a report of passing tests with any application bugs fixed along the way. ## Quick Start Ask the AI to update the integration tests to cover your recent code changes and run the full suite until everything passes.

Frequently Asked Questions about update-integration-tests

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

FAQPage Schema
How do I update integration tests after changing API code?▼

Run this Skill after modifying source files. It detects changed files via git diff, maps them to existing test coverage, updates outdated assertions or writes new tests, then runs the full suite and fixes every failure until all tests pass.

How to run vitest integration tests for a monorepo?▼

Use pnpm test in the integration repo for tier1 and tier3 tests, or pnpm test:all when admin or backend changed to include tier2 Playwright tests. Individual files can be re-run with npx vitest run and the config path.

What is the difference between Tier 1 and Tier 3 integration tests?▼

Tier 1 tests cover API contracts like CRUD operations, auth checks, and validation without live infrastructure. Tier 3 tests exercise live infrastructure such as sandbox pod lifecycle, SSH tunneling, WebSocket connections, and K8s exec.

Why do integration tests fail after refactoring application code?▼

Tests fail when assertions reference renamed properties, changed response shapes, or updated validation rules. The Skill reads the failing test and current code, proves the root cause, then updates the test or fixes the application bug.

Can integration tests use fake API keys for testing?▼

No. Tests must use real keys loaded from environment variables via loadEnvs(), such as TDSK_IT_API_KEY and TDSK_IT_ORG_ID. Fake keys are explicitly prohibited because tests run against live services.

What happens if tests still fail after multiple fix attempts?▼

The Skill iterates a maximum of 5 full-suite cycles. If failures remain, it stops and reports each remaining failure with full diagnostics including file, test name, error message, and what was attempted.