メニュー
Triage open GitHub issues — auto-label by type, find and close duplicates with a comment linking the original. Use whenever the user says "triage issues", "go through open issues", "handle new issues", or asks you to label/close/organize GitHub issues.
Codex または Claude でインストール この Prompt をコピーして Codex、Claude、または他のアシスタントに貼り付けると、Skill ページを確認してインストールできます。
SOC 職業分類に基づく
Audit place resolution against a real database to find outliers — places that resolve to the wrong country, state, or sub-region. Use when investigating bad map pins, validating new gazetteers, or debugging "why did Richmond, Kalifornien USA land in Canada?". Pairs with the `gazetteers` skill (build/extend) — this skill is for *testing* placement on real data.
Use whenever dispatching subagents in this project — implementer, spec-reviewer, or code-quality-reviewer. Wraps the upstream `superpowers:subagent-driven-development` skill with project-local prompt templates that center user goals (not just spec compliance) and require the dispatcher to verify user-observable outcomes before marking work done.
Decide which Playwright tier to run, capture the right evidence for plan close-out, and route work into the right project. Use when finishing a plan (gate before archive), when adding an e2e test (which project gets the spec), when CI fails on `[boot]` / `[crud]` / `[panels]` / `[reactivity]` / `[imports]` and you need to know which user-goal it protects, or when the question is "is `npm run test:e2e` enough or do I need `:full`?".
Extend the Släktforskning MCP server — add new tools to createProdServer.ts / createDevServer.ts, wire window.api bindings in tauri-window-api.ts + static-api stubs, test via tests/unit/mcp.test.ts, debug agent-facing IPC. Also covers the dev MCP HTTP bridge (src-tauri/src/ui_server.rs) used by ui_screenshot / ui_click / ui_eval / chart_*. Use when modifying anything in src/mcp/, src/renderer/tauri-window-api.ts, or src-tauri/src/ui_server.rs. Distinct from `slaktforskning-mcp` (which is for an agent *using* the MCP tools to do genealogy work for the user).
Build, extend, and debug gazetteers for place resolution. Use when adding new country gazetteers, modifying build scripts, debugging place matching, or questions about the gazetteer system (types, resolver, normalization, data sources).
Use when actually doing genealogy research with the Släktforskning MCP — building real family trees end-to-end, exporting/round-tripping, attaching media + face tags, importing custom gazetteers for places not in the bundled set. Pairs with `slaktforskning-mcp` (which lists the tools). Distinct from `slaktforskning-mcp-dev` (extending the MCP server itself). Triggers on real research workflows, "research X family", "test the app end-to-end", "set up a Bernadotte-style demo".
| name | oss-triage |
| description | Triage open GitHub issues — auto-label by type, find and close duplicates with a comment linking the original. Use whenever the user says "triage issues", "go through open issues", "handle new issues", or asks you to label/close/organize GitHub issues. |
Triage all open, unlabeled GitHub issues: classify them and close clear duplicates.
gh issue list --state open --limit 200 --json number,title,body,labels,url
Focus on issues that have no labels (or only the stale label). Skip issues that already have a type label.
Search existing issues (open + closed) by the key noun phrases in the title:
gh issue list --state all --search "<keyword>" --json number,title,state,url --limit 20
A duplicate is likely when:
If it's a duplicate:
Closing as a duplicate of #NNN. Please follow that issue for updates.
gh issue close <number> --comment "Duplicate of #NNN."
When in doubt, don't close — just label it and move on.
Classify each issue from its title + body and apply one label. Use your judgment — the exact label name matters less than getting the category right.
| Signal | Label to apply |
|---|---|
| "crash", "error", "broken", "doesn't work", "exception", describes unexpected behavior | bug |
| "would be great if", "add support for", "feature request", "it would help to" | enhancement |
| "how do I", "is it possible", "does X support" | question |
| Missing version, no repro steps, vague description where you can't tell what's wrong | needs-info |
Apply the label:
gh issue edit <number> --add-label "<label>"
If the label doesn't exist yet, create it first:
gh label create "<label>" --color "#0075ca" --description "<short description>"
For issues labeled needs-info, leave a comment asking for what's missing. Keep it short and specific — ask only for what you actually need to reproduce or understand the issue.
Example:
Thanks for the report! Could you share:
- The app version
- Steps to reproduce
That will help us investigate faster.
After finishing, print a summary:
Triaged N issues:
- X closed as duplicates
- X labeled bug
- X labeled enhancement
- X labeled question
- X labeled needs-info