From regex-builder
Tests a regular expression against sample inputs and edge cases, producing a table of match results, captured groups, and performance metrics.
How this command is triggered — by the user, by Claude, or both
Slash command
/regex-builder:test-regexThe summary Claude sees in its command listing — used to decide when to auto-load this command
# /test-regex - Test Regular Expression Test a regular expression against sample inputs and edge cases. ## Steps 1. Take the regex pattern from the user or the most recently built pattern 2. Ask for test strings or generate common test cases based on the pattern 3. Run the regex against each test string and report: match (yes/no), matched text, groups 4. Test with edge cases: empty string, very long string, special characters 5. Test with strings that should NOT match to verify specificity 6. Show captured groups for each matching test case 7. Measure the regex execution time with long i...
Test a regular expression against sample inputs and edge cases.
6plugins reuse this command
First indexed Mar 30, 2026
npx claudepluginhub ais1m0n3/awesome-claude-code-toolkit --plugin regex-builder/test-regexTests a regular expression against sample inputs and edge cases, producing a table of match results, captured groups, and performance metrics.
/regex-testerRuns an interactive regex tester with pattern matching, capture group visualization, and explanation tools. Supports testing, debugging, and building regular expressions.
/test-batchStress-tests a prompt against 10–100 synthetic test cases covering happy path, edge cases, and adversarial inputs; produces a coverage and quality report.
/test-promptTests an AI prompt across multiple scenarios (happy path, edge, ambiguous, error), scores output quality, and suggests improvements.
/test-teamSpawns a competing agent team (Happy Path, Edge Case, Red Team) to paper-test code from multiple perspectives, producing a prioritized flaw report with optional JSON CI output.
/test-performance-analysisAnalyzes test suite execution times, identifies slow tests (>2s), and suggests concrete refactoring patterns like transaction wrapping, mock adoption, or setup optimization.