Write integration tests for key workflows
SkillDev toolsintegration-testing is a skill for AI agents that helps review whether key workflow integration tests exist and run automatically in CI. It is used when examining CI coverage, automated checks, or test strategy, with a focus on whether rules are continuously verified rather than just documented.
Use Write integration tests for key workflows in Claude, ChatGPT or Ahel Desktop
Free. Sign in, add Write integration tests for key workflows and connect your AI. About a minute.
Also: Claude Code · Cursor · Codex
Then ask your AI: use the Write integration tests for key workflows skill
Details
Instructions available. Your AI can read the instructions. Execution depends on the setup they require.
Account requirements not reviewed. Check the skill instructions before use; ahel provides instructions and does not run this skill.
No other account needed.
Have an AI agent that can load skills.
What your AI can do with it
- Review CI coverage for key workflow integration tests
- Check whether automated checks run integration tests in CI
- Assess test strategy for key workflows
- Evaluate whether rules are continuously verified, not just documented
Getting started
- Have an AI agent that can load skills.
- Add the integration-testing skill to the agent's available skills.
- Ask the agent to review CI coverage, automated checks, or test strategy for key workflows.
- Use the skill when the goal is to write integration tests for key workflows.
What this skill tells your AI
The instructions your AI receives, as published by thedaviddias/front-end-checklist in skills/integration-testing/SKILL.md and read by ahel’s review.
Unit tests verify individual functions in isolation, but they can't catch the bugs that occur when those functions interact — a perfectly correct validation function and a correct database function can still fail when wired together incorrectly. Integration tests catch these wiring bugs before they reach production, where they're expensive to diagnose.
Quick Reference
- Integration tests verify that multiple units work correctly together
- Test at the boundary where different parts of your system meet
- Use a real database in tests (test DB or in-memory) rather than mocking everything
- Test happy paths and the most critical error paths
Check
Identify the key integration points in this codebase — where API routes call services, where services interact with the database, and where components interact with state management. Are these tested?
Fix
Write integration tests for the identified critical paths, testing the interactions between components rather than each in isolation.
Explain
Explain integration testing, how it differs from unit and E2E testing, and what tools to use for API and component integration tests.
Code Review
Review tests, CI workflows, and enforcement points related to Write integration tests for key workflows. Flag exact gaps where the rule is not automatically verified or where failures do not block regressions.
For full implementation details, code examples, and framework-specific guidance,
see references/rule.md.
Rule page: https://frontendchecklist.io/en/rules/testing/integration-testing
Signals
- GitHub stars
- 74k
- Forks
- 7k
- Last commit
- Oct 2026
Questions
- When should this skill be used?
- Use it when reviewing CI coverage, automated checks, or test strategy related to writing integration tests for key workflows.
- What does the skill focus on?
- It focuses on whether the rule is continuously verified, not just documented, that is, whether integration tests for key workflows actually exist and run automatically in CI.
- Does the skill run tests itself?
- The item only describes reviewing whether integration tests exist and run automatically in CI; it does not say the skill runs tests.
Advanced
- Item type
- skill
- Key
integration-testing-thedaviddias- Source
- github.com/thedaviddias/front-end-checklist
github.com/thedaviddias/front-end-checklist