5889d3428b
- Added 44 external skills from obra/superpowers, ui-ux-pro-max-skill, claude-codex-settings - Added 8 autonomous agents (commit-creator, pr-creator, pr-reviewer, etc.) - Added 23 slash commands for Git/GitHub, setup, and plugin development - Added hooks for code formatting, notifications, and validation - Added MCP configurations for Azure, GCloud, Supabase, MongoDB, etc. - Added awesome-openclaw-skills registry (3,002 skills referenced) - Updated comprehensive README with full documentation Sources: - github.com/obra/superpowers (14 skills) - github.com/nextlevelbuilder/ui-ux-pro-max-skill (1 skill) - github.com/fcakyon/claude-codex-settings (29 skills, 8 agents, 23 commands) - github.com/VoltAgent/awesome-openclaw-skills (registry) - skills.sh (reference) - buildwithclaude.com (reference)
994 B
994 B
description
| description |
|---|
| Configure GitHub CLI authentication |
GitHub CLI Setup
Source: github/github-mcp-server
Configure gh CLI for GitHub access.
Step 1: Check Current Status
Run gh auth status to check authentication state.
Report status:
- "GitHub CLI is not authenticated - needs login"
- OR "GitHub CLI is authenticated as "
Step 2: If Not Authenticated
Guide the user:
To authenticate with GitHub CLI:
gh auth login
This will open a browser for GitHub OAuth login.
Select: GitHub.com → HTTPS → Login with browser
Step 3: Verify Setup
After login, verify with:
gh auth status
gh api user --jq '.login'
Troubleshooting
If gh commands fail:
Common fixes:
1. Check authentication - gh auth status
2. Re-login - gh auth login
3. Missing scopes - re-auth with required permissions
4. Update gh CLI - brew upgrade gh (or equivalent)
5. Token expired - gh auth refresh