單元測試

Apply systematic four-phase debugging methodology (root cause investigation, pattern analysis, hypothesis testing, implementation) that ensures thorough understanding before attempting solutions, preventing random fixes and reducing debugging time from hours to minutes. Use this skill when encountering any test failures in test suites (Jest, pytest, RSpec, JUnit, Go testing), when production bugs are reported or discovered, when code produces unexpected output or behavior different from requirements, when experiencing build failures or compilation errors, when integration tests fail due to component interaction issues, when performance problems or slowdowns are detected, when encountering race conditions, timing issues, or intermittent failures, when error messages or stack traces appear in logs or console output, when refactoring causes existing tests to fail, when you've already attempted one or more fixes that didn't resolve the issue, when deployment or CI/CD pipelines fail, when you're tempted to make a

Prevent common testing anti-patterns that undermine test effectiveness and code quality by ensuring tests verify real behavior rather than mock behavior, keeping production code free from test-only pollution, and enforcing thoughtful mocking strategies. Use this skill when writing or modifying any test files (.test.ts, .test.js, .spec.ts, _test.py, test_*.py, *_test.go, *_spec.rb), when adding mock objects, stubs, spies, or test doubles to test suites, when considering adding methods or properties to production classes that are only called from test code, when setting up complex test fixtures or test data, when tests are failing and you're tempted to adjust mocks to make them pass, when deciding how to isolate code under test from external dependencies, when implementing dependency injection or test seams, during code reviews when reviewing test implementation and mocking strategies, when refactoring tests that have become brittle or hard to maintain, when test setup code is becoming longer than the actual te

Use when encountering any bug, test failure, or unexpected behavior, before proposing fixes - four-phase framework (root cause investigation, pattern analysis, hypothesis testing, implementation) that ensures understanding before attempting solutions

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 skill to build features or debug anything that uses a webapp frontend.

Use this skill when faced with a difficult debugging task where you need to replicate some bug or behavior in order to see what is going wrong.

Use this when you have completed some feature implementation and have written passing tests, and you are ready to create a PR.

Use when implementing any feature or bugfix, before writing implementation code - write the test first, watch it fail, write minimal code to pass; ensures tests actually verify behavior by requiring failure first

Use when writing or changing tests, adding mocks, or tempted to add test-only methods to production code - prevents testing mock behaviour, production pollution with test-only methods, and mocking without understanding dependencies

Applies current Go testing best practices. Use when writing or modifying Go test files or advising on Go testing strategies.

Guide for testing and verifying code changes in this TUI application. Use this skill after making ANY code changes to main.go or main.md to verify they work correctly.

Instructs AI agents on documentation standards for design docs, folder READMEs, source code interfaces, and test cases

Designs comprehensive testing strategies for any codebase. Use when adding tests, improving coverage, setting up testing infrastructure, or when asked about testing approaches.

Create comprehensive implementation plans with detailed file-level changes and test strategies

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

Use when creating new skills, editing existing skills, or verifying skills work before deployment - applies TDD to process documentation by testing with subagents before writing, iterating until bulletproof against rationalization

Use when implementing any feature or bugfix, before writing implementation code - write the test first, watch it fail, write minimal code to pass; ensures tests actually verify behavior by requiring failure first

Test-Driven Development workflow with RED-GREEN-REFACTOR cycle. Use when writing new features or fixing bugs to ensure code quality and test coverage.

Use when tests have race conditions, timing dependencies, or inconsistent pass/fail behavior - replaces arbitrary timeouts with condition polling to wait for actual state changes, eliminating flaky tests from timing guesses

Testing patterns and best practices including unit tests, integration tests, mocking, and test organization. Use when writing tests or setting up testing infrastructure.