setup
GitHub CLI Setup
Configure gh CLI for GitHub access.
Check Current Status
gh auth status
Report one of these states:
ghis not authenticated and needs loginghis authenticated, including the current username if available
Login Flow
If authentication is missing or broken, guide the user through:
gh auth login
Select: GitHub.com -> HTTPS -> Login with browser
Verify Authentication
gh auth status
gh api user --jq '.login'
Troubleshooting
If gh commands fail:
- Check authentication -
gh auth status - Re-login if needed -
gh auth login - Check scopes - Ensure the token has repo access
- Refresh auth -
gh auth refresh - Update gh -
brew upgrade ghor equivalent
More from fcakyon/claude-codex-settings
gcloud-usage
This skill should be used when user asks about "GCloud logs", "Cloud Logging queries", "Google Cloud metrics", "GCP observability", "trace analysis", or "debugging production issues on GCP".
62azure-usage
This skill should be used when user asks to "query Azure resources", "list storage accounts", "manage Key Vault secrets", "work with Cosmos DB", "check AKS clusters", "use Azure MCP", or interact with any Azure service.
48pr-workflow
This skill should be used when user asks to "create a PR", "make a pull request", "open PR for this branch", "submit changes as PR", "push and create PR", or runs /create-pr or /pr-creator commands.
47supabase-usage
This skill should be used when user asks to "query Supabase", "list Supabase tables", "get Supabase schema", "search Supabase records", "check Supabase database", "Supabase auth", "Supabase authentication", "RLS policy", "row level security", "Supabase foreign key", "table relationships", "Supabase join", "Supabase filter", "Supabase pagination", or needs guidance on Supabase database patterns, auth flows, RLS policies, or query best practices.
37linear-usage
This skill should be used when user asks about "Linear issues", "issue tracking best practices", "sprint planning", "Linear project management", or "creating Linear issues".
37plugin-structure
This skill should be used when the user asks to "create a plugin", "scaffold a plugin", "understand plugin structure", "organize plugin components", "set up plugin.json", "use ${CLAUDE_PLUGIN_ROOT}", "add commands/agents/skills/hooks", "configure auto-discovery", or needs guidance on plugin directory layout, manifest configuration, component organization, file naming conventions, or Claude Code plugin architecture best practices.
29