Skip to content

feat: add allowed_commands to skill definitions for bash permissions#9

Open
buger wants to merge 1 commit intomasterfrom
feat/skill-bash-permissions
Open

feat: add allowed_commands to skill definitions for bash permissions#9
buger wants to merge 1 commit intomasterfrom
feat/skill-bash-permissions

Conversation

@buger
Copy link
Copy Markdown
Contributor

@buger buger commented Feb 12, 2026

Summary

  • Adds allowed_commands fields to the github, github-actions, engineer, and assistant-debugging skill definitions in config/skills.yaml.
  • These fields declare which bash commands each skill is permitted to run (e.g., gh *, git *, npm *, curl *, jq *).
  • The allowed_commands lists are consumed by visor-ee's build-config step to dynamically configure bash command permissions based on the active skills for a given session.

Changed skills

Skill Allowed commands
github gh *
github-actions gh *
engineer git *, npm *, npx *, ls -F
assistant-debugging curl *, jq *

Test plan

  • Verify config/skills.yaml parses correctly (valid YAML)
  • Confirm visor-ee build-config reads the new allowed_commands fields and applies them to bash permissions
  • Validate that skills without allowed_commands are unaffected

🤖 Generated with Claude Code

Add bash command permission fields to skills that need CLI access:
- github: gh *
- github-actions: gh *
- engineer: git *, npm *, npx *, ls -F
- assistant-debugging: curl *, jq *

These are consumed by visor-ee's build-config step to dynamically
configure bash permissions based on active skills.

Co-Authored-By: Claude Opus 4.6 <noreply@anthropic.com>
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant