tests-new
New Tests for Recent Work
Review recent changes and add missing test coverage where it matters.
Instructions
Step 1: Identify Recent Changes
Run git diff HEAD~1 (or git diff main...HEAD if on a branch) to find what changed. If no git changes, ask the user which files to cover.
Focus on:
- New functions, methods, or components
- Changed behavior in existing code
- New API endpoints or routes
- Modified business logic
Step 2: Audit Existing Coverage
For each changed file, check if corresponding tests exist:
More from skinnyandbald/fish-skills
simplify-parallel
Run code simplification across entire codebase using parallel agents with automatic segmentation and coordination
38critic-review
Unified plan review — stack detection, Context7 staleness scan, multi-model counselors dispatch, and prioritized triage. Three modes: full pipeline (default), --dry-run (copyable prompt), --feedback (analyze external input).
36pr-resolution
Resolve PR review comments. Use when asked to fix PR feedback, given a PR URL, or on '/pr-resolution'.
34ceo-briefing
Research any topic and produce a structured executive briefing optimized for rapid CEO decision-making.
32counselors
Fan out a prompt to multiple AI coding agents in parallel and synthesize their responses.
32capture-learning
Capture comprehensive problem-solving narratives from work sessions, documenting the journey of discovery
32