What is a safety pattern in this context?

A safety pattern is a specific regex-based rule used to identify and block potentially dangerous shell commands before they are executed by the Caro CLI.

Can I use this for non-Rust projects?

While the specific implementation examples are tailored for the Caro Rust repository, the threat identification and TDD methodology can be adapted for any security-focused project.

How are risk levels determined?

Risk levels are categorized as Critical (data loss/system destruction), High (dangerous but reversible with backups), and Medium (harmful but limited in scope).

Why does this skill enforce a TDD workflow?

Test-Driven Development ensures that every safety rule is validated against specific threat scenarios before implementation, preventing both security gaps and false positives.

Safety Pattern Developer

Name: Safety Pattern Developer
Author: wildcard

bywildcard

•

Security & Testing

Guides developers through a rigorous Test-Driven Development workflow for creating and implementing safety patterns in command-line tools.

About

The Safety Pattern Developer skill facilitates the systematic addition of security rules to the Caro repository by enforcing a strict 6-phase TDD cycle. It assists developers in identifying potential system threats, writing failing test cases, implementing robust regex-based blocking patterns, and verifying them against regressions. This skill is essential for security-conscious developers looking to prevent accidental data loss or system destruction from dangerous shell commands like recursive deletions or disk wipes.

Key Features

Strict 6-phase TDD workflow (Red-Green-Refactor) enforcement
Standardized commit message generation for security updates
Automated regression testing and gap analysis integration
Comprehensive threat identification and documentation templates
23 GitHub stars
Regex-based safety pattern design and optimization guidance

Use Cases

Closing security gaps identified by static analyzers in CLI environments
Implementing custom safety rules for specific organizational CLI policies
Preventing accidental data loss by blocking dangerous patterns like recursive parent directory deletion

About

Key Features

Strict 6-phase TDD workflow (Red-Green-Refactor) enforcement
Standardized commit message generation for security updates
Automated regression testing and gap analysis integration
Comprehensive threat identification and documentation templates
23 GitHub stars
Regex-based safety pattern design and optimization guidance

Use Cases

Closing security gaps identified by static analyzers in CLI environments
Implementing custom safety rules for specific organizational CLI policies
Preventing accidental data loss by blocking dangerous patterns like recursive parent directory deletion