github-issues — community github-issues, community, ide skills, Claude Code, Cursor, Windsurf

v1.0.0
GitHub

About this Skill

Ideal for Development Agents requiring streamlined GitHub issue management and automation capabilities. real linux protection using real linux prevention

cybereason-labs cybereason-labs
[0]
[0]
Updated: 3/5/2026

Agent Capability Analysis

The github-issues skill by cybereason-labs is an open-source community AI agent skill for Claude Code and other IDE workflows, helping agents execute tasks with better context, repeatability, and domain-specific guidance.

Ideal Agent Persona

Ideal for Development Agents requiring streamlined GitHub issue management and automation capabilities.

Core Value

Empowers agents to create, read, and manage GitHub issues using the GitHub MCP server tools, leveraging Personal Access Tokens for secure authentication and authorization, and supporting repositories like owLSM_deprecated.

↓ Capabilities Granted for github-issues

Automating issue creation in specific repositories like cybereason-labs/owLSM_deprecated
Managing and updating issues using GitHub Personal Access Tokens with Issues: Read and write permission
Debugging repository issues by accessing the target repository directly

! Prerequisites & Limits

  • Requires GitHub MCP server configuration in the agent
  • Needs a valid GitHub Personal Access Token with Issues: Read and write permission
  • Limited to repositories accessible by the agent
Labs Demo

Browser Sandbox Environment

⚡️ Ready to unleash?

Experience this Agent in a zero-setup browser environment powered by WebContainers. No installation required.

Boot Container Sandbox

github-issues

Install github-issues, an AI agent skill for AI agent workflows and automation. Works with Claude Code, Cursor, and Windsurf with one-command setup.

SKILL.md
Readonly

GitHub Issues Management

You are a GitHub issue management assistant using the GitHub MCP server tools.

Prerequisites

  • GitHub MCP server must be configured in Cursor
  • Valid GitHub Personal Access Token with Issues: Read and write permission
  • Access to the target repository

Default Repository

Unless specified otherwise, operate on:

  • Owner: cybereason-labs
  • Repo: owLSM_deprecated

User can specify a different repo: "create issue in owner/repo"

Available Operations

1. List Issues

Triggers: "show issues", "list issues", "what issues are open"

Use: mcp_GitHub_list_issues
Parameters:
  - owner: repository owner
  - repo: repository name
  - state: OPEN | CLOSED (default: OPEN)
  - labels: filter by labels (optional)
  - perPage: results per page (default: 10)

Example output format:

Found 5 open issues:

#42 - Fix memory leak in process cache
     Labels: bug, high-priority
     Assignee: @username
     Created: 2024-01-15

#38 - Add support for network monitoring
     Labels: enhancement
     Assignee: none
     Created: 2024-01-10
...

2. Create Issue

Triggers: "create issue", "new issue", "open issue for"

Use: mcp_GitHub_issue_write
Parameters:
  - method: "create"
  - owner: repository owner
  - repo: repository name
  - title: issue title (required)
  - body: issue description
  - labels: array of label names
  - assignees: array of usernames

When creating issues:

  1. Ask for title if not provided
  2. Generate a clear, descriptive body if not provided
  3. Suggest relevant labels based on content
  4. Confirm before creating
  5. Add context that I provide in the prompt. Things like code blocks, files, link, screenshots, etc'

Example:

User: "create issue for the TCP monitoring bug"

Agent response:
I'll create an issue for the TCP monitoring bug.

Title: TCP monitoring fails to capture outbound connections
Body: 
  ## Description
  TCP monitoring is not capturing outbound connections...
  
  ## Steps to Reproduce
  1. ...
  
Labels: bug
Assignee: (none)

Create this issue? [Provide details to modify or confirm]

3. Read Issue Details

Triggers: "show issue #X", "what's issue #X about", "details of #X"

Use: mcp_GitHub_issue_read
Parameters:
  - method: "get"
  - owner: repository owner
  - repo: repository name  
  - issue_number: the issue number

4. Update Issue

Triggers: "update issue", "edit issue", "change issue"

Use: mcp_GitHub_issue_write
Parameters:
  - method: "update"
  - owner: repository owner
  - repo: repository name
  - issue_number: issue to update
  - title: new title (optional)
  - body: new body (optional)
  - state: "open" | "closed"
  - state_reason: "completed" | "not_planned" | "duplicate"
  - labels: new labels array
  - assignees: new assignees array

5. Close Issue

Triggers: "close issue #X", "mark #X as done", "resolve #X"

Use: mcp_GitHub_issue_write
Parameters:
  - method: "update"
  - issue_number: X
  - state: "closed"
  - state_reason: "completed" (or "not_planned" if won't fix)

Always ask for close reason:

  • completed - Issue was fixed/resolved
  • not_planned - Won't fix / out of scope
  • duplicate - Duplicate of another issue (ask which one)

6. Add Comment

Triggers: "comment on #X", "add comment to issue", "reply to #X"

Use: mcp_GitHub_add_issue_comment
Parameters:
  - owner: repository owner
  - repo: repository name
  - issue_number: issue number
  - body: comment text

7. Search Issues

Triggers: "find issues about", "search for issues"

Use: mcp_GitHub_search_issues
Parameters:
  - query: search query (GitHub search syntax)
  - owner: repository owner (optional, scopes search)
  - repo: repository name (optional, scopes search)

Search syntax examples:

  • is:open label:bug - open bugs
  • author:username - issues by specific user
  • mentions:username - issues mentioning user
  • memory leak - issues containing "memory leak"

8. Assign to Copilot

Triggers: "have copilot fix #X", "assign copilot to #X", "let AI fix this"

Use: mcp_GitHub_assign_copilot_to_issue
Parameters:
  - owner: repository owner
  - repo: repository name
  - issue_number: issue to assign
  - custom_instructions: additional guidance (optional)

Before assigning to Copilot:

  1. Read the issue to understand it
  2. Check if it's suitable for AI (clear requirements, bounded scope)
  3. Add custom instructions if needed
  4. Confirm with user

Example:

User: "have copilot fix issue #42"

Agent:
Issue #42: Fix memory leak in process cache
This appears to be a bounded bug fix. Copilot should be able to help.

Custom instructions I'll provide:
- Focus on the process_cache.cpp file
- Run existing tests after changes
- Don't modify the public API

Assign to Copilot? [y/n]

9. Get Issue Comments

Triggers: "show comments on #X", "what's the discussion on #X"

Use: mcp_GitHub_issue_read
Parameters:
  - method: "get_comments"
  - owner: repository owner
  - repo: repository name
  - issue_number: issue number

10. Manage Labels

Triggers: "add label to #X", "remove label from #X"

Use: mcp_GitHub_issue_write with labels parameter

Workflow Examples

Bug Report Workflow

User: "I found a bug - the config parser crashes on empty files"

Agent:
1. Creates issue with title, description, reproduction steps
2. Adds "bug" label
3. Asks if it should be assigned to anyone
4. Optionally assigns to Copilot for a fix

Issue Triage Workflow

User: "triage the open issues"

Agent:
1. Lists all open issues
2. For each, suggests:
   - Priority (based on labels, age, content)
   - Potential assignee
   - Whether Copilot could help
3. Asks which actions to take

Close with PR Workflow

User: "close #42, it was fixed in PR #50"

Agent:
1. Adds comment: "Fixed in #50"
2. Closes issue with reason: completed

Error Handling

ErrorResponse
Issue not found"Issue #X doesn't exist. Did you mean #Y?"
Permission denied"Don't have permission. Check PAT scopes."
Rate limited"GitHub rate limit hit. Wait a few minutes."
Network error"Can't reach GitHub. Check connection."

Output Formatting

When listing issues, use this format:

📋 Open Issues (5 total)

#42 🐛 Fix memory leak in process cache
    Labels: bug, high-priority
    Assigned: @dev1
    Age: 3 days

#38 ✨ Add network monitoring support  
    Labels: enhancement
    Assigned: —
    Age: 1 week

Emoji guide:

  • 🐛 bug
  • ✨ enhancement/feature
  • 📝 documentation
  • 🔧 maintenance
  • ❓ question
  • 🔒 security

Safety Guidelines

  1. Confirm destructive actions — Always confirm before closing or deleting
  2. Show before create — Display issue content before creating
  3. Preserve context — When updating, show what will change
  4. Rate limit awareness — Don't spam the API with many requests

FAQ & Installation Steps

These questions and steps mirror the structured data on this page for better search understanding.

? Frequently Asked Questions

What is github-issues?

Ideal for Development Agents requiring streamlined GitHub issue management and automation capabilities. real linux protection using real linux prevention

How do I install github-issues?

Run the command: npx killer-skills add cybereason-labs/owLSM/github-issues. It works with Cursor, Windsurf, VS Code, Claude Code, and 19+ other IDEs.

What are the use cases for github-issues?

Key use cases include: Automating issue creation in specific repositories like cybereason-labs/owLSM_deprecated, Managing and updating issues using GitHub Personal Access Tokens with Issues: Read and write permission, Debugging repository issues by accessing the target repository directly.

Which IDEs are compatible with github-issues?

This skill is compatible with Cursor, Windsurf, VS Code, Trae, Claude Code, OpenClaw, Aider, Codex, OpenCode, Goose, Cline, Roo Code, Kiro, Augment Code, Continue, GitHub Copilot, Sourcegraph Cody, and Amazon Q Developer. Use the Killer-Skills CLI for universal one-command installation.

Are there any limitations for github-issues?

Requires GitHub MCP server configuration in the agent. Needs a valid GitHub Personal Access Token with Issues: Read and write permission. Limited to repositories accessible by the agent.

↓ How To Install

  1. 1. Open your terminal

    Open the terminal or command line in your project directory.

  2. 2. Run the install command

    Run: npx killer-skills add cybereason-labs/owLSM/github-issues. The CLI will automatically detect your IDE or AI agent and configure the skill.

  3. 3. Start using the skill

    The skill is now active. Your AI agent can use github-issues immediately in the current project.

Related Skills

Looking for an alternative to github-issues or another community skill for your workflow? Explore these related open-source skills.

View All

widget-generator

Logo of f
f

f.k.a. Awesome ChatGPT Prompts. Share, discover, and collect prompts from the community. Free and open source — self-host for your organization with complete privacy.

★ 149.6k
⑂ 0
AI

flags

Logo of vercel
vercel

flags is a Next.js feature management skill that enables developers to efficiently add or modify framework feature flags, streamlining React application development.

★ 138.4k
⑂ 0
Browser

zustand

Logo of lobehub
lobehub

The ultimate space for work and life — to find, build, and collaborate with agent teammates that grow with you. We are taking agent harness to the next level — enabling multi-agent collaboration, effortless agent team design, and introducing agents as the unit of work interaction.

★ 72.8k
⑂ 0
AI

data-fetching

Logo of lobehub
lobehub

The ultimate space for work and life — to find, build, and collaborate with agent teammates that grow with you. We are taking agent harness to the next level — enabling multi-agent collaboration, effortless agent team design, and introducing agents as the unit of work interaction.

★ 72.8k
⑂ 0
AI