Agent Skills › QuixiAI/Hexis › github-issues

github-issues

GitHub

通过 GitHub MCP 服务器搜索、读取、创建和评论 GitHub Issue。强调先搜索避免重复，创建前需确认，并引用具体证据。

skills/installed/github-issues/SKILL.md QuixiAI/Hexis

Trigger Scenarios

用户请求查询或管理 GitHub Issue 需要创建新的 Bug 报告或功能请求

Install

npx skills add QuixiAI/Hexis --skill github-issues -g -y

More Options

Non-standard path

npx skills add https://github.com/QuixiAI/Hexis/tree/main/skills/installed/github-issues -g -y

Use without installing

npx skills use QuixiAI/Hexis@github-issues

指定 Agent (Claude Code)

npx skills add QuixiAI/Hexis --skill github-issues -a claude-code -g -y

安装 repo 全部 skill

npx skills add QuixiAI/Hexis --all -g -y

预览 repo 内 skill

npx skills add QuixiAI/Hexis --list

SKILL.md

Frontmatter

{
    "mcp": {
        "args": [
            "-y",
            "@modelcontextprotocol\/server-github"
        ],
        "server": "github",
        "command": "npx",
        "env_requires": [
            "GITHUB_PERSONAL_ACCESS_TOKEN"
        ]
    },
    "name": "github-issues",
    "category": "productivity",
    "contexts": [
        "heartbeat",
        "chat"
    ],
    "bound_tools": [
        "mcp_github_search_issues",
        "mcp_github_list_issues",
        "mcp_github_get_issue",
        "mcp_github_create_issue",
        "mcp_github_add_issue_comment",
        "mcp_github_update_issue"
    ],
    "description": "Search, read, create, and comment on GitHub issues through the GitHub MCP server."
}

GitHub Issues

Work with GitHub issues on repositories the configured token can reach. This skill binds the GitHub MCP server: activating it starts the server (first use only) and unlocks the bound tools for this turn.

Workflow

Search before creating. Use mcp_github_search_issues to check whether the issue already exists; duplicate issues waste maintainer attention. Comment on the existing issue instead when appropriate.
Creating an issue is an outward-facing action. Confirm with the user before filing unless they explicitly asked you to file it. Show the title and body you intend to submit.
Reference concrete evidence (file paths, line numbers, reproduction steps) that you actually verified this turn.
After creating, report the issue URL from the tool result — never invent one.

If activation reports needs_setup

Relay the exact next_step to the user (usually: set GITHUB_PERSONAL_ACCESS_TOKEN in the service environment). Do not claim GitHub capability is missing — it is installed and one step away.