Add a maintainers script to safely promote high-confidence legacy risk labels from unknown to concrete values, cover it with tests, and regenerate the canonical skill artifacts and plugin copies. This reduces the legacy unknown backlog without forcing noisy classifications that still need manual review.
37 lines
1.1 KiB
Markdown
37 lines
1.1 KiB
Markdown
---
|
|
name: memory-safety-patterns
|
|
description: "Cross-language patterns for memory-safe programming including RAII, ownership, smart pointers, and resource management."
|
|
risk: safe
|
|
source: community
|
|
date_added: "2026-02-27"
|
|
---
|
|
|
|
# Memory Safety Patterns
|
|
|
|
Cross-language patterns for memory-safe programming including RAII, ownership, smart pointers, and resource management.
|
|
|
|
## Use this skill when
|
|
|
|
- Writing memory-safe systems code
|
|
- Managing resources (files, sockets, memory)
|
|
- Preventing use-after-free and leaks
|
|
- Implementing RAII patterns
|
|
- Choosing between languages for safety
|
|
- Debugging memory issues
|
|
|
|
## Do not use this skill when
|
|
|
|
- The task is unrelated to memory safety patterns
|
|
- You need a different domain or tool outside this scope
|
|
|
|
## Instructions
|
|
|
|
- Clarify goals, constraints, and required inputs.
|
|
- Apply relevant best practices and validate outcomes.
|
|
- Provide actionable steps and verification.
|
|
- If detailed examples are required, open `resources/implementation-playbook.md`.
|
|
|
|
## Resources
|
|
|
|
- `resources/implementation-playbook.md` for detailed patterns and examples.
|