Loading...
Loading...
Found 24 Skills
Guide for writing tests. Use when adding new functionality, fixing bugs, or when tests are needed. Emphasizes integration tests, real-world fixtures, and regression coverage.
Perform comprehensive code reviews with best practices, security checks, and constructive feedback. Use when reviewing pull requests, analyzing code quality, checking for security vulnerabilities, or providing code improvement suggestions.
Guidelines for writing effective tests in this project
Quick reference for n8n patterns. Full docs /AGENTS.md
Shared Go best practices for LlamaFarm CLI. Covers idiomatic patterns, error handling, and testing.
Development conventions and patterns for everything-claude-code. JavaScript project with conventional commits.
Use when symfony functional tests
Use when symfony tdd with phpunit
Defines ROI-based coverage targets with critical path identification, layer-specific targets, and explicit "don't test this" guidelines. Use for "test coverage", "coverage strategy", "test priorities", or "coverage targets".
Use when symfony e2e panther playwright
Checklists and anti-patterns for reviewing Go code. Covers API design, error handling, concurrency, interfaces, safety, performance, naming, testing, functional options, logging, and deterministic simulation testing.
Use when writing or changing tests, adding mocks, or tempted to add test-only methods to production code - prevents testing mock behavior, production pollution with test-only methods, and mocking without understanding dependencies