Menu
Use when creating, listing, or viewing GitHub issues via CLI - triggers on issue management tasks, bug reporting, or feature requests
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
Thorough, critical code review focused on correctness, business logic, implementation, tests, and documentation. Use when reviewing code changes, pull requests, or implementations. Only invoke when user explicitly asks for code review.
Use when the user asks to create or render a Mermaid or Merman chart, mentions merman-cli, or wants an ASCII terminal diagram. Render it with `merman-cli`.
Defensive security review and hardening of application code, configuration, dependencies, and tests using current OWASP guidance. Use only when the user explicitly asks for a security review, security audit, vulnerability review, or security hardening. Do not use for general code review.
Expert guidance for using the GitLab CLI (glab) to manage GitLab issues, merge requests, CI/CD pipelines, repositories, and other GitLab operations from the command line. Use this skill when the user needs to interact with GitLab resources or perform GitLab workflows. Assumes the user is already authenticated.
Use when editing, modifying, or transforming existing image files with AI using the local Gemini image-edit CLI. Trigger this for style changes, object removal, background edits, text/layout fixes, color tweaks, or when the user says to use image-edit from the terminal. This skill runs the global `image-edit` executable from any repo.
Use when generating image files from text prompts with the local Gemini image CLI. Trigger this when the user asks to create, generate, or render an AI image, artwork, ad image, book cover, mockup, visual asset, or says to use image-gen from the terminal. This skill runs the global `image-gen` executable from any repo.
| name | gh-issues |
| description | Use when creating, listing, or viewing GitHub issues via CLI - triggers on issue management tasks, bug reporting, or feature requests |
Create, list, or view GitHub issues using the gh CLI.
digraph {
rankdir=TB
"User invokes gh-issues" -> "Ask: Create, List, or View?"
"Ask: Create, List, or View?" -> "Create" [label="new issue"]
"Ask: Create, List, or View?" -> "List" [label="browse"]
"Ask: Create, List, or View?" -> "View" [label="specific #"]
"Create" -> "Get title (5-10 words)"
"Get title (5-10 words)" -> "Get type + description"
"Get type + description" -> "Bug?" [shape=diamond]
"Bug?" -> "Ask repro steps + expected/actual" [label="yes"]
"Bug?" -> "Optional labels" [label="no"]
"Ask repro steps + expected/actual" -> "Optional labels"
"Optional labels" -> "gh issue create"
"List" -> "Ask filter (all/assigned/author/label)"
"Ask filter (all/assigned/author/label)" -> "gh issue list"
"View" -> "Ask issue number"
"Ask issue number" -> "gh issue view"
}
| Action | Command |
|---|---|
| Create | gh issue create --title "..." --body "$(cat <<'EOF'...EOF``)" |
| List all | gh issue list |
| List mine | gh issue list --assignee @me |
| List by author | gh issue list --author @me |
| List by label | gh issue list --label "bug" |
| View | gh issue view 123 |
| Auth check | gh auth status |
Use AskUserQuestion with options: Create new issue, List issues, View issue
gh issue create --title "Title" --body "$(cat <<'EOF'
## Description
[description]
## Steps to Reproduce # (bugs only)
[steps]
## Expected / Actual # (bugs only)
[behavior]
EOF
)"
Ask filter preference, then run appropriate command from Quick Reference table.
Ask issue number, run gh issue view [number].
| Mistake | Fix |
|---|---|
| Title too long | Move details to body. Titles are scannable headers, not summaries. |
| Not authenticated | Run gh auth login first |
| Not in repo | Must be in git repo with GitHub remote |
| Body formatting lost | Always use HEREDOC syntax to preserve newlines |
If gh fails: check gh auth status, verify GitHub remote exists, report specific error.