Debug Failing Tests
Use when Pest, PHPUnit, Livewire, browser, or package tests fail and need systematic diagnosis.
— No reviews yet
0 installs
0 views
— view→install
Install
$ agentstack add skill-alizharb-agent-skills-debug-failing-tests ✓ scanned · ✓ verified — works with Claude Code, Cursor, and more.
Security review
✓ PassedNo issues found. Passed automated security review. · v0.1.0 How review works →
- ✓ Prompt-injection patterns
- ✓ Secret / credential exfiltration
- ✓ Dangerous shell & filesystem operations
- ✓ Untrusted network calls
- ✓ Known-malicious package signatures
What it can access
- ✓ Network access No
- ✓ Filesystem access No
- ✓ Shell / process execution No
- ✓ Environment & secrets No
- ✓ Dynamic code execution No
From automated source analysis of v0.1.0. “Used” means the capability is present in the source — more access means more to trust, not that it’s unsafe.
Are you the author of Debug Failing Tests? Claim this listing to set pricing, connect Stripe payouts, and keep 70% of every sale.
Sign up to claimAbout
Debug Failing Tests
Workflow
- Run the smallest failing test first.
- Read the failure message, stack trace, and assertion intent.
- Determine whether the test, fixture, environment, or product code is wrong.
- Fix the root cause instead of weakening assertions.
- Add a regression test when the failure exposed an untested behavior.
- Re-run the targeted test and then the relevant suite.
Verification
- Targeted test passes.
- Relevant suite passes.
Common Mistakes
- Re-running the full suite repeatedly before isolating the failure.
- Deleting assertions that describe real behavior.
Source & license
This open-source skill is cataloged on AgentStack and links to its original source — we do not rehost the code.
- Author: AlizHarb
- Source: AlizHarb/agent-skills
- License: MIT
Install and usage instructions live in the source repository linked above.
Reviews
No reviews yet — be the first.
Write a review
Versions
- v0.1.0 Imported from the upstream source.