📦 deps(thirdparty): update snapshots

2026-06-06 16:01:57 +00:00
parent 0b1862e551
commit 772a1da63c
293 changed files with 25299 additions and 369 deletions
@@ -0,0 +1,54 @@
+---
+name: permission-manager
+version: 1.0.0
+description: "Manage opencode permissions: review always-allow lists, suggest safe read-only commands, configure permission patterns"
+risk: critical
+source: community
+source_type: community
+source_repo: mskadu/opencode-agent-skills
+license: MIT
+license_source: "https://github.com/mskadu/opencode-agent-skills/blob/main/LICENSE"
+date_added: "2026-06-05"
+---
+
+## What I do
+- Review and summarize currently always-allowed commands
+- Suggest safe read-only commands for auto-approval
+- Add or remove commands from the allow list in opencode.json
+- Configure skill-level permissions (allow/deny/ask) with wildcard patterns
+- Audit permission configs for security and usability
+
+## When to Use
+Use this when optimizing opencode's permission settings, reviewing allowed commands, or configuring skill access controls.
+
+## Workflow Steps
+
+1. **Read current config**: Load `~/.config/opencode/opencode.json` or project-level `opencode.json`
+2. **Summarize permissions**: Identify currently allowed commands and skill permissions
+3. **Suggest additions**: Propose safe read-only commands for auto-allow (see recommended list below)
+4. **Apply changes**: Edit the config to add/remove permission entries
+5. **Validate**: Ensure JSON is valid after changes
+
+Complements opencode's built-in allow/deny/ask permissions by auditing current config and recommending adjustments through conversation.
+
+## Key Rules
+- Never allow commands that modify files, commit, push, or change system state
+- Use wildcards appropriately (e.g., `git status*` not just `git status`)
+- Confirm with user before modifying permission config
+- Distinguish between bash command permissions and skill permissions
+- Keep config organized: group related commands together
+
+## Limitations
+
+- This skill is scoped to opencode permission configuration and should not modify other agent hosts' permission stores.
+- Treat all write-capable command permissions as high-risk; review them manually even when a pattern looks narrow.
+
+## How to trigger me
+
+Use the Task tool with the `permission-manager` subagent type:
+
+```
+/permissions
+```
+
+Or in natural language, ask opencode to "manage opencode permissions" or "review allowed commands".