A data pipeline often needs more than one test to work perfectly. This skill guides you through a step by step cycle. You run the pipeline, check for errors, and fix them. Then you start over until it passes.
The idea is to run first and debug later. Do not waste time on checks before the test. Just start the run and see what happens. If it fails, then look at the logs and fix the code.
Use a single command like af runs trigger-wait to test the pipeline. It shows whether the run passed or failed. If it failed, you can find the problem and try again. This makes testing and fixing fast and simple.
Global
mkdir -p ~/.claude/skills/testing-dagsProject
mkdir -p .claude/skills/testing-dagsSource Repository
Grill Memattpocock/skills
Stress-test your plan with relentless questions until we both understand
Tddmattpocock/skills
Write one test at a time then code to make it pass
Test Driven Developmentobra/superpowers
Write a failing test first then code just enough to pass
Qamattpocock/skills
Turn bug reports into GitHub issues through natural conversation without technical fuss
Migrate To Shoehornmattpocock/skills
Replace unsafe as assertions with type-safe partial test data easily
Webapp Testinganthropics/skills
Test your local web apps quickly with Playwright automation and screenshots
Playwright Best Practicescurrents-dev/playwright-best-practices-skill
Master Playwright testing with best practices for reliable and fast tests
Google Agents Cli Evalgoogle/agents-cli
Run evaluations on your AI agent, find failures, and improve its quality step by step