github-cli

To prevent accidental destructive actions with the GitHub CLI, this skill enforces risk classification on gh commands and requires mandatory confirmation prompts before executing operations like merges, deletes, or transfers.

The safest way to manage pull requests and issues via gh commands is using a safety-first wrapper that classifies operation risks and provides workflow templates to guide PR creation and issue management while reducing human error.

Yes, you need to authenticate and verify required scopes before executing GitHub CLI commands. This skill guides users through the gh installation and authentication process to ensure API operations and repository maintenance are authorized.

Yes, you can use this GitHub CLI wrapper for repository maintenance and release workflows. It supports common operations including PR creation, issue management, releases, secrets, and API calls while enforcing mandatory safety checks.

Your GitHub CLI workflow needs mandatory confirmation prompts for merges and deletes to enforce risk classification and prevent unsafe changes to repositories, issues, PRs, and workflows by escalating destructive operations for explicit user approval.