Every regex is written once and read a hundred times. Optimize for the readers.

Somewhere in a codebase you own there’s a regex that three people can write and nobody can read. Mine was a date-validation pattern — forty-some characters of punctuation and backreference syntax that I wrote in one sitting and then spent an hour decoding six months later when the edge case arrived. The edge case, of course, was one the regex never handled, because I had no reliable way to see what it actually did versus what I believed it did.

在你拥有的代码库中，总有那么一段正则表达式，能写出来的人寥寥无几，能读懂的人更是几乎没有。我曾写过一个日期验证模式——那是一串包含四十多个标点符号和反向引用语法的字符，我一气呵成写完，但六个月后当边缘情况出现时，我花了一个小时才将其解码。当然，那个边缘情况正是该正则表达式从未处理过的，因为我没有可靠的方法来验证它实际执行的功能与我预想的是否一致。

30-second takeaway: Every regex is written once and read ≥100 times — optimize for readers, not writers. Part-by-part explanation + edge case callout = regexes become team-readable. Language-aware: JS vs PCRE vs Java regex differences are not cosmetic (caught 3 prod bugs). One plain-English input → working regex + explanation + edge cases in 3 seconds.

30秒要点：每个正则表达式只写一次，但会被阅读100次以上——请为读者而非作者进行优化。逐部分解释加上边缘情况标注，能让正则表达式变得易于团队阅读。语言感知：JS、PCRE 和 Java 正则表达式之间的差异并非表面功夫（我曾因此捕获了3个生产环境的漏洞）。只需输入一段简单的英语描述，3秒内即可获得可用的正则表达式、详细解释及边缘情况分析。

The two problems with regexes, in order: Problem one: writing them. Problem two: knowing what you wrote. The second is worse, because regexes are write-once-read-many — and the “many” includes future you, who has no context, and a colleague who has less. A regex without an explanation isn’t done; it’s a liability with a test suite that may or may not cover the inputs you care about. Which points at the real quality bar: not “it works on my sample,” but “every part is explained and the edge cases are named.”

正则表达式的两个问题，按顺序排列如下：第一个问题是编写它们，第二个问题是了解你写了什么。后者更为严重，因为正则表达式是“一次编写，多次阅读”的——而“多次”包括了毫无背景信息的未来的你，以及背景信息更少的同事。没有解释的正则表达式是不完整的；它是一个隐患，其测试套件可能覆盖了你关心的输入，也可能没有。这指向了真正的质量标准：不是“它在我的样本上能运行”，而是“每一部分都有解释，且边缘情况已明确列出”。

RegexProof takes a plain-English description — “match US phone numbers with optional country code” — and produces a working regex in your language’s flavor, because a JavaScript regex and a PCRE regex are not the same animal and the differences bite. Then it does the part I care about more: a part-by-part explanation of the pattern, and the edge cases called out explicitly — what it will match that you might not intend, and what it won’t match that you might assume it does.

RegexProof 接收一段简单的英语描述（例如“匹配带有可选国家代码的美国电话号码”），并生成符合你所用语言风格的可运行正则表达式，因为 JavaScript 正则表达式和 PCRE 正则表达式并非同一种东西，这些差异往往会带来麻烦。接着，它会执行我更关心的部分：对模式进行逐部分解释，并明确指出边缘情况——即它会匹配到你可能未预期的内容，以及它不会匹配到你可能认为它会匹配的内容。

Where this fits a real workflow: The legacy regex in the codebase nobody understands: paste it in, get the explanation, decide if it’s even correct. (On my date pattern, it was not.) New validation rules: describe, generate, read the edge cases, then write tests for the named edge cases before merging. Cross-language porting: same intent, correct flavor syntax, no silent behavioral drift.

它在实际工作流中的应用：对于代码库中没人能看懂的遗留正则表达式，将其粘贴进去，获取解释，然后判断它是否正确。（在我那个日期模式的例子中，它是不正确的。）对于新的验证规则：描述、生成、阅读边缘情况，然后在合并前为这些已命名的边缘情况编写测试。对于跨语言移植：保持相同意图，使用正确的语法风格，避免出现静默的行为偏差。

What it is not: It won’t replace testing — a generated regex with zero tests is still a regex, and regexes fail in production, not in examples. Performance isn’t addressed: a correct pattern can still be a catastrophic-backtracking pattern on hostile input, and ReDoS is your threat model, not the generator’s. And ambiguity in your description produces ambiguity in the pattern; “match dates” is underspecified, so be specific about formats.

它不是什么：它不能取代测试——一个没有测试的生成式正则表达式依然是正则表达式，而正则表达式是在生产环境中失败的，而不是在示例中。它不解决性能问题：一个正确的模式在面对恶意输入时仍可能导致灾难性的回溯，ReDoS（正则表达式拒绝服务攻击）是你的威胁模型，而非生成器的。此外，描述中的歧义会导致模式中的歧义；“匹配日期”属于定义不清，因此请务必明确格式。

Take one regex from your codebase: The oldest one you can find. Paste it into RegexProof and read the explanation like you’ve never seen it before — because your newest teammate hasn’t. If the explanation reveals behavior you didn’t intend, congratulations, you found a bug before your users did. Free to try, no signup wall.

从你的代码库中找出一个正则表达式：找一个你能找到的最古老的。将其粘贴到 RegexProof 中，像第一次见到它一样阅读解释——因为你的新同事确实没见过。如果解释揭示了你未预期的行为，恭喜你，你在用户发现之前就找到了一个漏洞。免费试用，无需注册。