code-path-discovery

What problem does it solve? Manually identifying all behavioral paths in a codebase for test planning is slow and error-prone. This Skill automates static analysis of TypeScript/JavaScript code to surface candidate scenarios across nominal, alternative, exception, edge, corner, and negative test categories. ## Core Features & Use Cases - Pattern-Based Scanning: Detects route definitions, conditional branches, error handlers, guard clauses, and validation logic using targeted code patterns. - Six-Category Output: Maps detected patterns to the 6-category path format (nominal, alternative, exception, edge cases, corner cases, negative tests) used by the /paths workflow. - Scope Control: Warns on broad scopes over 50 files and caps processing at 100 files with prioritized ordering. - Use Case: When starting test planning for a new feature, run this against your source directory to get candidate scenarios like "POST /login validates credentials" or "JWT middleware rejects malformed tokens" for collaborative review. ## Quick Start Invoke /paths --from-code with a source directory path and issue title to scan the code and receive categorized behavioral path candidates.