error-pattern-safety

Enforce safe regex error patterns to prevent infinite loops in Go and JavaScript.

Updated Aug 23, 2026
One-click install
npx skills add https://github.com/maxfraieho/garden-seedling --skill error-pattern-safety-maxfraieho
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: error-pattern-safety
Source: https://github.com/maxfraieho/garden-seedling/tree/main/gh-aw/skills/error-pattern-safety
Command: npx skills add https://github.com/maxfraieho/garden-seedling --skill error-pattern-safety-maxfraieho

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Error Pattern Safety guidelines help prevent infinite loops and unsafe regex usage in agentic engines by enforcing safe pattern construction, preflight checks, and cross-language pattern handling.

Core Features & Use Cases

  • Enforce safety rules for regex patterns used in error matching to avoid zero-width matches that can cause endless looping.
  • Provide standardized checks and quick remediation steps for both Go and JavaScript environments, with clear conversion guidelines.
  • Support comprehensive documentation and governance for adding new patterns, tests, and audits.

Quick Start

Identify unsafe patterns and apply built-in validators to ensure error matching remains safe and non-infinite.

Frequently Asked Questions about error-pattern-safety

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I prevent infinite loops caused by zero-width regex matches in error matching?

Prevent infinite loops in error matching by enforcing safe pattern construction with preflight checks that identify and block zero-width matches before runtime execution.

Can I apply the same error pattern safety rules across both Go and JavaScript environments?

Yes, error pattern safety rules apply across Go and JavaScript environments, providing standardized checks and clear conversion guidelines for cross-language pattern handling.

What is the best way to validate regex patterns for agentic engines to ensure they are safe?

The best way to validate regex patterns for agentic engines is to use built-in validators that enforce iteration guards and perform preflight checks for unsafe pattern construction.

Why does my error matching loop endlessly when using regex in my validation logic?

Error matching loops endlessly when regex patterns allow zero-width matches, which fail to advance the iteration cursor, causing the engine to repeatedly match the same empty string position.

How do I add new error patterns and tests while maintaining safety governance?

Add new error patterns and tests by following standardized governance documentation that requires built-in validators, iteration guards, and clear audit trails for pattern safety compliance.