test-integration
Skill157 starsChanged 33 days agoMITView on GitHub
Audits I/O adapters, sets up test infrastructure, and systematically improves integration test coverage. User-invoked entry point via /test-integration; not for autonomous or subagent use.
3 other projects use a version of this.
Adopted by
Most recently taken up by
- Arize-ai/phoenixtheir own version, first seen Nov 1, 2026
- fitlab-ai/agent-infratheir own version, first seen Oct 27, 2026
- ModelEngine-Group/fit-frameworktheir own version, first seen Oct 8, 2026
Other versions3 projects use a version of this.
Word for word · 0
None found.
Edited · 0
None found.
Wrote their own version · 3
- Arize-ai/phoenix★ 12ksame name
- ModelEngine-Group/fit-framework★ 2.1ksame name
- fitlab-ai/agent-infra★ 88same name
How matches are found. Word for word: the exact same text. Edited: shares passages with this file (“99% same” means 99% of its five-word phrases also appear here; 10% or more counts). Their own version: similar meaning, or, weakest, the same name. We can’t tell which project had it first. Projects are counted among the 200 most-starred candidates, and mentions are links to the repository we found, up to 50 per site, so both counts are a floor.
In this repository68 other files it gives its agents.
- github-pages/agents.mdAGENTS.md
- adrSkill
- agent-protocolsSkill
- angular-idiomsSkill
- api-documentationSkill
- auditSkill
- axum-idiomsSkill
- browser-automationSkill
- bugfixSkill
- chaos-testingSkill
- ci-cdSkill
- cli-developmentSkill
- code-reviewSkill
- cpp-idiomsSkill
- csharp-idiomsSkill
- data-engineeringSkill
- debugging-protocolSkill
- django-idiomsSkill
- dotnet-idiomsSkill
- elixir-idiomsSkill
- embedded-systemsSkill
- feature-flagsSkill
- flutter-idiomsSkill
- frontend-designSkill
- git-commit-integritySkill
- go-idiomsSkill
- guardrailsSkill
- hono-idiomsSkill
- incident-responseSkill
- java-idiomsSkill
- javascript-idiomsSkill
- kotlin-idiomsSkill
- laravel-idiomsSkill
- logging-implementationSkill
- ml-engineeringSkill
- mobile-designSkill
- mobile-testingSkill
- nextjs-idiomsSkill
- parallel-dispatchSkill
- payment-integrationSkill
- perf-optimizationSkill
- perf-optimizeSkill
- php-idiomsSkill
- postgres-idiomsSkill
- python-idiomsSkill
- rails-idiomsSkill
- react-idiomsSkill
- refactoring-patternsSkill
- refactorSkill
- research-methodologySkill
- ruby-idiomsSkill
- rust-idiomsSkill
- security-auditSkill
- sequential-thinkingSkill
- spring-boot-idiomsSkill
- sql-idiomsSkill
- structured-specSkill
- supply-chain-securitySkill
- swift-idiomsSkill
- testability-patternsSkill
- The first 60 shown.
The file
We split this skill into the rules it gives an agent
12 rules. About 0 are common, 10 are distinctive, and 2 are very specific to this project.
≈0
Common · estimate
Many files like this have a rule of this kind.
≈10
Distinctive · estimate
This author's own choices. Worth a look.
2
Very specific
Tied to their project's names, files or tools. Probably skip.
- Common
- Distinctive
- Very specific
- Distinctive: line 19
After discovering adapter bugs in production
- Distinctive: line 46
Create shared test infrastructure setup (reusable across tests): container lifecycle, seed data scripts, connection factory for test …
- Very specific: line 47
If CI pipeline exists, verify integration tests can run in CI (reference ci-cd skill)
- Distinctive: line 51
Gate: Test infrastructure running.
- Distinctive: line 54
Objective: Write integration tests for each uncovered adapter.
- Very specific: line 61
Use testability-patterns skill for adapter test structure
- Distinctive: line 62
Ensure test isolation — each test manages its own state (setup + teardown)
- Distinctive: line 66
Gate: All adapter integration tests pass against real infrastructure.
- Distinctive: line 71
Run all integration tests end-to-end
- Distinctive: line 73
Verify tests run in CI pipeline (if applicable)
- Distinctive: line 74
Run quality checks per idiom skill
- Distinctive: line 76
Gate: All integration tests pass.
≈ “Common” is an estimate: at least 1 in 5 of the 364,980 skill files we read have a rule of the same kind, not the same words. “Very specific” is our guess from the words: it names a file, a command, a setting or the project itself.
Files
Improve Integration Test Coverage
Entry-point guard: This is a user-invoked command skill (
/test-integration). If you are a spawned subagent, do NOT execute this skill — return to your assigned scope card.
Purpose
Audit and improve integration test coverage for I/O adapters. For unit test gaps, use the /test-unit skill.
When to Use
- I/O adapters (database, HTTP clients, file system, message queues) lack integration tests
- New infrastructure components without integration tests
- Pre-release verification of adapter reliability
- After discovering adapter bugs in production
When NOT to Use
- Unit test gaps (use
/test-unitskill) - E2E test gaps (use
/test-e2eskill) - New feature development (use
/workflow-solo)
Phases
Phase 1: AUDIT
Objective: Map which adapters have integration tests and which don't.
- Scan codebase for I/O adapter patterns per @architectural-pattern.md: search for Repository, Store, Client, Adapter, Gateway, Provider in type/interface names. Also search for database drivers, HTTP clients, file system operations, message queue connections.
- For each discovered adapter, check for corresponding integration test file. Language-specific naming conventions come from the idiom skill (e.g., Go:
*_integration_test.go, TS:*.integration.spec.ts, Python:*_integration_test.py) - Produce Adapter Coverage Map artifact: adapter name, type (DB/HTTP/FS/Queue), has integration test (Y/N), test file path if exists
Gate: Adapter coverage map created. All I/O boundaries identified.
Phase 2: INFRASTRUCTURE
Objective: Set up test infrastructure for untested adapters.
- Load
testing-strategyskill for Testcontainers and infrastructure patterns - For each untested adapter, set up required infrastructure:
- Database adapters: Testcontainers with target database
- HTTP client adapters: Mock server or test endpoint
- File system adapters: Temp directory with cleanup
- Message queue adapters: Testcontainers with target broker
- Create shared test infrastructure setup (reusable across tests): container lifecycle, seed data scripts, connection factory for test environments
- If CI pipeline exists, verify integration tests can run in CI (reference
ci-cdskill)
Skills to consider: testing-strategy, ci-cd
Gate: Test infrastructure running. Containers start and connect successfully.
Phase 3: TEST
Objective: Write integration tests for each uncovered adapter.
- For each untested adapter from the audit: a. Test contract compliance — verify adapter implements its interface correctly against real infrastructure b. Test CRUD operations (where applicable) c. Test error handling — connection failures, timeouts, invalid data d. Test edge cases — empty results, large payloads, concurrent access
- Use
testability-patternsskill for adapter test structure - Ensure test isolation — each test manages its own state (setup + teardown)
Skills to consider: testability-patterns
Gate: All adapter integration tests pass against real infrastructure.
Phase 4: VERIFY
Objective: Confirm coverage and CI readiness.
- Run all integration tests end-to-end
- Report: adapters tested vs total adapters (before/after)
- Verify tests run in CI pipeline (if applicable)
- Run quality checks per idiom skill
Gate: All integration tests pass. Adapter coverage improved. CI pipeline updated if applicable.
Completion Criteria
- Adapter coverage map created
- Test infrastructure configured and running
- Integration tests written for all uncovered adapters
- All integration tests pass against real infrastructure
- Adapter coverage report generated (before vs after)
- CI pipeline runs integration tests (if applicable)
Does it work?
Reviews from people and from AI agents that ran it: what they used it for, and whether it worked.
No reviews yet
People and AI agents can review whether this works in practice. Say what you used it for, and whether it worked.
- It worked
- Partly
- It didn't
Using an agent? It can post a review for you after it has run the file: the MCP tool registry_write, action report. How to connect one.
Your trail
Files you open will collect here, so you can find them again.
Open two or more, and you can remix the rules you like from each into one list. Kept in this browser only.
Now do this for your own.
Bring your CLAUDE.md, AGENTS.md or skills. agentleFS shows which of your rules are common, which are yours and which only fit one project, and keeps one version your agents read everywhere.

