github-issue-searchlisted
Install: claude install-skill SebastienDegodez/skraft-plugin
# GitHub Issue Search
## Existing issue content is read-only
Never change the `title` or `body` of an existing issue, through MCP, CLI or any
other transport, even when the installed tool exposes those fields. Omit both
fields from issue-update payloads; do not resend their current values.
Put refinements, acceptance criteria and proposed wording in a comment or a local
artefact. A comment's `body` is distinct from the issue's `body`.
## Route by intent
- **Write a comment or labels** on an existing issue: load
[issue write routes](references/issue-write-routes.md) and follow it.
- **Discover issues**: continue below. Before a search or triage MCP call, load
[MCP tool patterns](references/mcp-tool-patterns.md) for host schema binding,
parameters, responses and errors. For qualifiers or query recipes beyond this page,
load [search syntax](references/github-search-syntax.md). When extracting domain terms
from changed files, load [artifact-driven heuristics](references/artifact-driven-heuristics.md).
## Overview
Structured protocol for discovering GitHub issues via three modes. Core principle: **build precise queries to surface signal, not noise**. A well-formed query with 3–5 qualifiers outperforms broad queries with post-hoc filtering.
Three modes address different discovery intents:
- **User-assigned** — "what is mine to work on right now"
- **Artifact-driven** — "what is related to what I am currently changing"
- **Search-based** — "explore a theme or milest