generate-test-cases

# Generate Test Cases Skill You will analyze code and generate a list of test cases that should be written for a given method/class. This skill outputs test case descriptions only — it does NOT generate actual test code. **Target to analyze:** $ARGUMENTS ## Quality Standards - Take your time to analyze the code thoroughly before listing test cases. - Quality is more important than speed — read all relevant source files and rules carefully. - Do not skip reading the dependency classes. Understanding the full context produces better test cases. --- ## Instructions ### Step 1: Read Rules and Analyze Context 1. **Read the rules** from `./rules/general/` directory (see Rules Reference below) 2. **Read the target** source file/class/method specified above 3. **Read dependencies**: Follow imports to read DTOs, entities, enums, and other types referenced by the target (as specified in `code-context-analysis` rule) 4. **Check for existing tests**: Search for existing test classes covering this target (as specified in `existing-test-awareness` rule) — if found, read it fully and focus only on behaviors not yet covered ### Step 2: Generate Test Cases 1. Analyze ALL code branches, including: - Success paths - Error/exception paths - Validation logic - Private/protected methods called by the target - Security annotations (if present) 2. Apply the INCLUDE/EXCLUDE rules strictly 3. Output the list of test cases in the specified format 4. Do NOT generate actual test ...