{"id":79583,"plugin_id":"plugins_6ab427b8c6908191a438adb4b6f315d4","kind":"skill","collection_source":"plugin_package","comparison_source":null,"observed_at":"2026-11-04T00:11:26.429Z","digest":"bf37a139eb18d4c38fe52ede8b661c907dcae98085272378b6d449e2e094aa7e","against":null,"payload":{"description":"Review existing shell scripts for logic defects, portability, security, robustness and minimal safe corrections.","included_files":[],"name":"review-shell-script","skill_md_contents":"---\nname: review-shell-script\ndescription: Review existing shell scripts for logic defects, portability, security, robustness and minimal safe corrections.\n---\n\n# Review shell scripts\n\n## Scope and execution truth\nThis is a skills-only assistant workflow. Do not claim to execute system commands, inspect the user's host, install packages, or complete side effects without actual authorized tools and observed results. User-pasted output is evidence, not a machine connection.\n\n## Procedure\n1. Read the actual script, environment assumptions and desired behavior before recommending a rewrite.\n2. Inspect word splitting, globbing, regex, command substitution, temporary files, IFS handling, `set -e`, pipeline errors and trap behavior.\n3. Inspect destructive commands, privilege escalation, injection risk, secrets, path handling, and shell-specific syntax.\n4. Classify issues by severity and provide affected lines and evidence; avoid hypothetical findings presented as established facts.\n5. Propose a minimal patch with regression tests. If ShellCheck is available, use it as supporting static evidence, not proof of safety.\n\n## Relevant references\n- Read `../../references/shell-debugging.md` for domain-specific guidance.\n- Read `../../references/shell-quoting.md` for domain-specific guidance.\n- Read `../../references/security-and-secrets.md` for domain-specific guidance.\n\n## Completion checks\n- Existing semantics preserved\n- Prioritized actionable findings\n- Testable changes, not speculative rewrite\n\n## Deliverable\nUse the minimum format that makes the answer actionable: the actual command or patch, platform assumptions, a preview before risky changes, and a reproducible validation step. Clearly label proposed actions versus observed execution.\n"},"changes":[],"summary":"First saved snapshot. No earlier version is available for comparison.","summary_kind":"deterministic","summary_metadata":{}}