Loading...
Loading...
Found 326 Skills
Use when creating or editing skills, before deployment, to verify they work under pressure and resist rationalization - applies RED-GREEN-REFACTOR cycle to process documentation by running baseline without skill, writing to address failures, iterating to close loopholes
Test-driven development for Laravel with PHPUnit and Pest, factories, database testing, fakes, and coverage targets.
Test-driven development for Spring Boot using JUnit 5, Mockito, MockMvc, Testcontainers, and JaCoCo. Use when adding features, fixing bugs, or refactoring.
End-to-end implementation orchestrator. Use when the user says "orchestrate", "implement this end to end", "build this", or wants a full feature/fix implemented through a team of agents with planning, implementation, review, and QA phases.
Meta-skill workflow orchestrator for bug investigation and resolution. Routes to debug, implement, test, and commit based on scope.
Create work-order with minimal context for isolated subagent execution, optionally linked to GitHub issue
Use after brainstorming/design phase to create detailed implementation plans. Creates step-by-step plans clear enough for execution by any developer.
Fetch ALL unresolved PR conversations — review threads, review body comments, and regular PR comments — then output a strict /tdd plan with atomic commits that fixes and replies to every one. Use this skill whenever the user wants to resolve, address, or fix PR review feedback, comments, threads, nitpicks, or suggestions from any reviewer (human or bot like CodeRabbit, Copilot, etc.). Triggers on phrases like "resolve PR threads", "fix PR comments", "address review feedback", "resolve conversations".
Structured implementation planning for multi-step development tasks. Use when you have a spec or requirements and need to break work into executable steps.
Use when writing RSpec tests for service objects, API clients, orchestrators, or business logic in spec/services/. Covers instance_double, FactoryBot hash factories, shared_examples, subject/let blocks, context/describe structure, aggregate_failures, change matchers, travel_to, and error scenario testing.
Test-Driven Development specifically for Laravel applications using Pest PHP. Use when implementing any Laravel feature or bugfix - write the test first, watch it fail, write minimal code to pass.
Implements user stories, writes clean tested code, follows best practices. Trigger keywords implement story, dev story, code, implement, build feature, fix bug, write tests, code review, refactor