Loading...
Loading...
Found 295 Skills
Use when creating or editing any prompt (commands, hooks, skills, subagent instructions) to verify it produces desired behavior - applies RED-GREEN-REFACTOR cycle to prompt engineering using subagents for isolated testing
Run git-workspace-review first to understand which tests need updates. Use when updating existing tests, generating new tests for features, enhancing test quality, ensuring detailed coverage, pre-commit validation. Do not use when auditing test suites - use pensive:test-review. DO NOT use when: writing production code - focus on implementation first.
Structured implementation planning for multi-step development tasks. Use when you have a spec or requirements and need to break work into executable steps.
Root cause analysis for debugging. Use when bugs, test failures, or unexpected behavior have non-obvious causes, or after multiple fix attempts have failed.
Red-green-refactor development methodology requiring verified test coverage. Use for feature implementation, bugfixes, refactoring, or any behavior changes where tests must prove correctness.
Document capabilities and skills comprehensively. Creates skill documentation with examples, specifications, and usage patterns.
Develop software with validation requirements first. Emphasizes writing tests before implementation to guide design decisions.
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
Use this before touching code when you have a requirement for a specification or multi-step task
Delegate implementation work to the coder agent. Provide requirements or feature file path.
This skill should be used when the user asks to "write unit tests", "follow unit testing best practices", "improve test quality", "structure test cases", or needs guidance on unit testing concepts, patterns, and principles.
Use when you have a spec or requirements for a multi-step task, before writing implementation code. Helps break down complex features into bite-sized, verifiable tasks.