القائمة
Resource lifecycle patterns: files, DB connections, sockets, locks. RAII, defer/finally, pooling, graceful shutdown, leak prevention.
التثبيت باستخدام Codex أو Claude انسخ هذا Prompt والصقه في Codex أو Claude أو مساعد آخر ليراجع صفحة Skill ويثبّتها لك.
استنادا إلى تصنيف SOC المهني
Session bootstrap + workflows for Pathfinder semantic navigation tools. Covers: discovery protocol, tool chaining patterns (explore, impact, audit, debug), search optimization, LSP degraded mode, and error recovery.
Playwright browser automation via MCP. Covers E2E testing, UI review, web scraping, screenshot capture, and general browser interaction. MCP-first — CLI is fallback only.
Safe command execution: input sanitization, timeout handling, output capture, error propagation. For spawning processes, shell commands, system calls.
Git conventions: conventional commits, branch naming, PR hygiene, release tagging.
Structured incident workflow: severity classification, triage, diagnosis, mitigation, postmortem, and prevention. Template-driven with blameless review.
Constructs, validates, and traverses a Directed Acyclic Graph (DAG) from scope cards for safe level-based parallel dispatch. Determines execution order via topological sort. Detects cycles and invalid dependencies.
| name | resources-and-memory-management |
| description | Resource lifecycle patterns: files, DB connections, sockets, locks. RAII, defer/finally, pooling, graceful shutdown, leak prevention. |
| user-invocable | false |
Resources: files, connections, locks, semaphores, memory, OS handles, GPU.
Clean up in ALL paths: success, error, early return.
Language patterns: Go=defer, Rust=Drop(RAII), Python=with, TS=try/finally, Java=try-with-resources.
Pool config: min 5 (warm), max 20-50, idle timeout 5-10 min, validate before use, monitor utilization/wait/timeout.
Leak = acquire + never release → exhaust system resources. Detect: monitor fd/connection/memory over time, long-duration tests, leak tools (valgrind, ASan, heap profilers). Prevent: use language cleanup patterns, never rely on manual alone.
Problem: producer > consumer → unbounded queue → OOM.
Solutions: bounded queues, rate limiting, flow control, circuit breakers, drop/reject (fail fast > crash).
GC'd (Go, Java, Python, JS): auto-freed, still must release non-memory resources, GC pauses in latency-sensitive, profile for retained refs.
Manual (C/C++): malloc/free, RAII in C++, prefer smart pointers.
Ownership (Rust): compiler-enforced safety, no GC, no manual mgmt. Arc/Rc for shared ownership.
