Menu
Perform common GitHub operations using the gh CLI. USE WHEN the user wants to file an issue or create a gist.
Install with Codex or Claude Copy this prompt, paste it into Codex, Claude, or another assistant, and let it review the skill page and install it for you.
Based on SOC occupation classification
| name | GitHub |
| description | Perform common GitHub operations using the gh CLI. USE WHEN the user wants to file an issue or create a gist. |
| argument-hint | ["action"] |
You perform common GitHub operations using the gh CLI based on the user's request.
Read References: You MUST read the gh CLI reference completely before proceeding: @./reference/gh-commands.md
Gather Context: Run claude-GitHub-repo-info to get current repository context
Determine Intent: Analyze the user's request to identify:
Select Workflow: Route to the appropriate workflow based on the user's intent:
Execute Workflow: Report to the user "Running using the GitHub skill..." You MUST read the workflow document completely before proceeding, then follow the workflow's process completely: ./workflows/<WorkflowName>.md
Report Results: Summarize what was accomplished and suggest next steps
| Workflow | Trigger Words | When to Use |
|---|---|---|
| FileIssue | "file", "issue", "bug", "report" | User wants to create a GitHub issue |
| CreateGist | "gist", "snippet", "share", "paste" | User wants to create a GitHub gist |
Test NixOS configuration changes using the feedback ladder — from instant syntax checks to full system builds. USE WHEN the user wants to verify, test, or check NixOS changes before deploying.
Review and fix documentation surprises discovered by the surprise hook. USE WHEN the user wants to fix documentation issues, review surprises, or address items in .claude/surprises/.
Query systemd journal logs, check service status, diagnose failed units, and analyze boot performance. USE WHEN investigating system issues, service failures, checking logs, or when the user asks about systemd services or journal entries.
Browser automation for development testing, web scraping, and UI verification. USE WHEN you need to interact with web pages, verify UI changes, take screenshots, or extract data from websites.
Systematically explore and test a web application to find bugs, UX issues, and other problems. USE WHEN the user wants to quality-test a web app, find issues, dogfood a product, or produce a structured bug report with reproduction evidence.
Automate Electron desktop apps (VS Code, Slack, Discord, Figma, Notion, Spotify, etc.) via Chrome DevTools Protocol. USE WHEN the user needs to interact with an Electron desktop app, automate a native app, connect to a running Electron app, or test an Electron application.
