github-cli

Wrap GitHub CLI commands with risk classification and confirmation prompts.

27|9|Updated Jan 4, 2026

Search Tags:#automation #workflow #github #safety #pr #gh #risk-classification

Ready to run

npx skills add https://github.com/georgekhananaev/claude-skills-vault --skill github-cli-georgekhananaev

💬 Prompt for ChatGPT / Claude Chat▼

Please help me install this Agent Skill.
Skill: github-cli
Source: https://github.com/georgekhananaev/claude-skills-vault/tree/main/.claude/skills/github-cli
Command: npx skills add https://github.com/georgekhananaev/claude-skills-vault --skill github-cli-georgekhananaev

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes references (resource) components.

What problem does it solve?

This Skill wraps the GitHub CLI (gh) to enforce risk classification and mandatory confirmations for destructive or forbidden operations, preventing unsafe changes to repositories, issues, PRs, and workflows.

Core Features & Use Cases

Risk classification for gh commands and automatic escalation of unsafe operations.
Mandatory confirmation prompts for destructive actions (merge, delete, transfer, etc.) with clear decision options.
Guidance and templates for common workflows (PRs, issues, releases, secrets, API calls) to reduce human error.

Quick Start

Use the github-cli skill to perform a safe PR creation or issue management with risk checks, then confirm any destructive action when prompted.

Frequently Asked Questions about github-cli

High-intent search queries and answers about installing and using this skill.

FAQPage Schema

How do I prevent accidental destructive actions when using the 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.

What is the safest way to manage pull requests and issues via gh commands?▼

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.

Do I need to authenticate and verify scopes before executing GitHub CLI commands?▼

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.

Can I use this GitHub CLI wrapper for repository maintenance and release workflows?▼

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.

Why does my GitHub CLI workflow need mandatory confirmation prompts for merges and deletes?▼

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.