laravel-tdd
From the author
Test-driven development for Laravel with PHPUnit and Pest, factories, database testing, fakes, and coverage targets.
Install
npx skills add hashgraph-online/awesome-codex-plugins --skill laravel-tdd -a claude-code
Installs to .claude/skills/laravel-tdd/ · Each command fetches the skill straight from GitHub with the open skills CLI.
Download .zip
Byte-identical to the scanned commit, with the repository’s licence and a SOURCE.txt.
Want your agent to suggest skills while you type? See how to use skills from your IDE.
Safety checks on SKILL.md
No warnings.
Why 88
Security100
Provenance78
Maintenance100
Licence100
Adoption51
aiqbench computes the trust score from public signals. It is not a security audit, so read a skill before you install it.
Similar skills
Closest to this one by what they do and when they are used.
- django-tddhashgraph-online/awesome-codex-pluginsDjango testing strategies with pytest-django, TDD methodology, factory_boy, mocking, coverage, and testing Django REST Framework APIs.Testing★ 1.4K
- tddsickn33/agentic-awesome-skillsTest-driven development. Use when the user wants to build features or fix bugs test-first, mentions "red-green-refactor", or wants integration tests.Testing★ 48.3K
- tdd-workflowhashgraph-online/awesome-codex-pluginsUse this skill when writing new features, fixing bugs, or refactoring code. Enforces test-driven development with 80%+ coverage including unit, integration, and E2E tests.Testing★ 1.4K
- perl-testinghashgraph-online/awesome-codex-pluginsPerl testing patterns using Test2::V0, Test::More, prove runner, mocking, coverage with Devel::Cover, and TDD methodology.Testing★ 1.4K
- tdd-guideforyourhealth111-pixel/Vibe-SkillsTest-first development route for TDD, writing failing tests first, RED -> GREEN -> REFACTOR, and behavior-changing feature/bug/refactor work. Do not use for already-failing test root-cause debugging, test-report packaging, or final completion evidence.Testing★ 3.8K
- agentic-tddreticlehq/reticleTest-driven development for behaviour a unit test cannot reach, by writing the expectation against the running app before writing the code. Declare the consequence first, watch it fail, implement, watch it pass. Use when building a user-facing feature, when the user asks for TDD on UI or full-stack work, when a unit test cannot express the outcome that matters, or when you want a red-green loop that runs against the real app instead of mocks.Testing★ 1.3K
Ratings & reviews
—
no reviews
Tried this skill? Rate it to help others. Sign in
Discussion
Join the discussion. Sign in