terminal-ops

To safely run local shell commands, you can use a workspace-scoped terminal operation skill that executes explicit Bash or PowerShell syntax. It targets filesystem mutations with guardrails to prevent unsafe deletions while inspecting or changing project files.

The best way to search for specific text strings within a local repository is using a read-first workflow with guided shell operations. This approach applies safe search rules via explicit Bash or PowerShell commands before making any filesystem changes.

Yes, you can manage background services using terminal operations that start long-running commands. The skill supports checking status and logs, and stopping these background commands through companion tools for controlled lifecycle management.

Yes, this terminal operations approach supports both Bash and PowerShell environments. You must explicitly choose your shell and provide narrow, single-command syntax per step to ensure workspace-safe execution for your local development workflow.

Limitations of workspace-scoped shell commands include the exclusion of domain expertise tasks, browser browsing, binary parsing, validation, and desktop GUI control. Mutations are strictly workspace-scoped, and you must provide exact syntax without subagent delegation.