gh-searchlisted

# gh-search When `gh-status` is too coarse and the user has a specific question, `gh-search` runs the targeted query. ## When to use - "Show me all open features in `svc:bridge` with severity:high" - "Which issues are blocked by something that's still open" - "List bugs filed by @alice in the last 30 days" - Anything that needs a one-shot ad-hoc filter, not a recurring view ## Inputs ``` gh-search "<natural language or raw github-search-syntax>" [--json] [--limit <n>] ``` | Flag | Default | Effect | |---|---|---| | `<query>` | required | Either natural language ("high-severity bridge bugs") or raw syntax (`is:open type:bug svc:bridge severity:high`). The skill detects which by checking for syntax markers (`is:`, `label:`, `:`). | | `--json` | off | Emit one line of JSON per issue for piping. | | `--limit` | 50 | Max results. | ## What it does ### Step 1 — Translate natural language to GH search syntax Heuristics (deterministic): | Phrase | Adds | |---|---| | "open" / "still open" | `is:open` | | "closed" / "completed" / "done" | `is:closed` | | "high-severity" / "severity high" / "p1" | `severity:high` | | "bug" / "bugs" / "broken" | `type:bug` | | "feature" / "features" | `type:feature` | | "request" / "requests" / "deferred" | `type:request` | | "in <service>" / "<service> issues" | `svc:<service>` (where `<service>` matches a known svc label) | | "by @<user>" | `author:<user>` | | "assigned to @<user>" | `assignee:<user>` | | "last <n> days" | `created:>YYYY-MM-D