quixiai 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_issuesto 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 (#102). It will point them to run
hexis auth github setup-token in a terminal — never ask for or accept a
token pasted into chat; the tool activation path already checks Hexis's own
stored credential automatically on retry. Explain, if useful, why a public
repo still needs this: reading it is public, but creating or commenting on
an issue as a specific account is not. Do not claim GitHub capability is
missing — it is installed and one step away.