{"id":18653,"plugin_id":"plugins_6a8b1dfa2b948191be588a88bafb158e","kind":"skill","collection_source":null,"comparison_source":null,"observed_at":"2026-09-30T23:14:52.764Z","digest":"cff7381508878e08602b7b9221c94071ed43c469ed69c8889dc3b40b30483ffd","against":null,"payload":{"description":"Use when the user asks why CompText Guard blocked or warned on a repository action, or whether a planned shell action falls inside the current local policy.","included_files":[{"relative_path":"agents/openai.yaml","size_in_bytes":256}],"name":"check-guard","skill_md_contents":"---\nname: check-guard\ndescription: Use when the user asks why CompText Guard blocked or warned on a repository action, or whether a planned shell action falls inside the current local policy.\n---\n\n# Check CompText Guard\n\nExplain the active local hook policy; do not bypass it.\n\nThe default v0.1 policy blocks direct secret/environment reads, unscoped Git history-changing operations, GitHub PR/issue/release writes, and common deploy/release commands. It warns when protected repository-control paths are mentioned.\n\nRead-only Git operations such as `git status`, `git diff`, and `git log` remain allowed.\n\nIf the user explicitly authorizes a release or remote-write scope, report that the default hook still blocks it until the policy profile itself is changed; do not silently disable or edit the hook.\n\nTreat hook output as policy evidence, not proof that an action is otherwise safe."},"changes":[],"summary":"First saved snapshot. No earlier version is available for comparison.","summary_kind":"deterministic","summary_metadata":{}}