Best use case
issues is best used when you need a repeatable AI agent workflow instead of a one-off prompt.
List GitHub issues for the current repository
Teams using issues should expect a more consistent output, faster repeated execution, less prompt rewriting.
When to use this skill
- You want a reusable workflow that can be run more than once with consistent structure.
When not to use this skill
- You only need a quick one-off answer and do not need a reusable workflow.
- You cannot install or maintain the underlying files, dependencies, or repository context.
Installation
Claude Code / Cursor / Codex
Manual Installation
- Download SKILL.md from GitHub
- Place it in
.claude/skills/issues/SKILL.mdinside your project - Restart your AI agent — it will auto-discover the skill
How issues Compares
| Feature / Agent | issues | Standard Approach |
|---|---|---|
| Platform Support | Not specified | Limited / Varies |
| Context Awareness | High | Baseline |
| Installation Complexity | Unknown | N/A |
Frequently Asked Questions
What does this skill do?
List GitHub issues for the current repository
Where can I find the source code?
You can find the source code on GitHub using the link provided at the top of the page.
SKILL.md Source
# Issues - List GitHub Issues
Display GitHub issues for the current repository. **You execute this directly.**
## Step 1: Check GitHub Setup
```bash
"${CLAUDE_PLUGIN_ROOT}/scripts/check-gh-setup.sh"
```
Parse the JSON output and check `preferred_method`:
**If `preferred_method` is "none":**
Check the specific issue:
- If `gh_installed` is false:
```
GitHub CLI is not installed.
To install:
- macOS: brew install gh
- Windows: winget install GitHub.cli
- Linux: See https://github.com/cli/cli/blob/trunk/docs/install_linux.md
Alternatively, set a GITHUB_TOKEN environment variable to use the API directly.
```
- If `gh_installed` is true but `gh_authenticated` is false:
```
GitHub CLI is installed but not authenticated.
Run: gh auth login
This will guide you through authentication with your GitHub account.
```
Then exit - do not continue to Step 2.
**If `preferred_method` is "gh" or "curl":**
Continue to Step 2.
## Step 2: Parse Arguments
Parse `$ARGUMENTS` for filter options:
- `--state STATE` - Filter by state: open (default), closed, all
- `--label LABEL` - Filter by label (can appear multiple times)
- `--assignee USER` - Filter by assignee
Build the command arguments.
## Step 3: Fetch and Display Issues
```bash
"${CLAUDE_PLUGIN_ROOT}/scripts/list-issues.sh" [options from step 2]
```
Display the formatted output to the user.
**If no issues found:**
```
No issues found matching your criteria.
Try different filters:
- /devloop:issues --state all
- /devloop:issues --state closed
```
## Step 4: Offer Next Actions
```yaml
AskUserQuestion:
questions:
- question: "What would you like to do?"
header: "Action"
multiSelect: false
options:
- label: "Start work on an issue"
description: "Use /devloop:plan --from-issue <number>"
- label: "Filter differently"
description: "Search with different criteria"
- label: "Done"
description: "Exit issue list"
```
### If "Start work on an issue":
Ask which issue number, then run `/devloop:plan --from-issue <number>`
### If "Filter differently":
Ask for new filter criteria and re-run Step 3
### If "Done":
Exit
---
## Quick Reference
| Option | Description | Default |
|--------|-------------|---------|
| `--state` | Issue state: open, closed, all | open |
| `--label` | Filter by label | none |
| `--assignee` | Filter by assignee | none |
## Examples
```bash
# List open issues (default)
/devloop:issues
# List all issues
/devloop:issues --state all
# List bugs only
/devloop:issues --label bug
# List issues assigned to me
/devloop:issues --assignee @me
# Combined filters
/devloop:issues --state open --label enhancement
```
## Output Format
```
# Open Issues (12)
#42 [bug] Login fails on Safari @alice 2d ago
#38 [feature] Add dark mode @bob 5d ago
#35 [docs] Update README - 1w ago
```Related Skills
Example Skill
Brief description of what this skill does and the domain expertise it provides.
vulnerability-patterns
Index of vulnerability detection pattern skills. Routes to core patterns (universal) and language-specific patterns for security scanning.
vuln-patterns-languages
Language-specific vulnerability detection patterns for JavaScript/TypeScript, Python, Go, Java, Ruby, and PHP. Provides regex patterns and grep commands for common security vulnerabilities.
vuln-patterns-core
Universal vulnerability detection patterns applicable across all programming languages. Includes hardcoded secrets, SQL/command injection, path traversal, and configuration file patterns.
scan
Run a security assessment using deterministic static analysis tools with LLM-powered triage
results
View the most recent security scan results without re-running the scan
remediation-library
Index of security remediation skills. Routes to specialized skills for injection, cryptography, authentication, and configuration vulnerabilities.
remediation-injection
Security fix patterns for injection vulnerabilities (SQL, Command, XSS). Provides language-specific code examples showing vulnerable and secure implementations.
remediation-crypto
Security fix patterns for cryptographic vulnerabilities (weak algorithms, insecure randomness, TLS issues). Provides language-specific secure implementations.
remediation-config
Security fix patterns for configuration and deployment vulnerabilities (path traversal, debug mode, security headers). Provides language-specific secure implementations.
remediation-auth
Security fix patterns for authentication and authorization vulnerabilities (credentials, JWT, deserialization, access control). Provides language-specific secure implementations.
fix
Fix or guide remediation for a specific security finding from the latest scan report