菜单
Close stale GitHub issues and PRs that have had no activity for 60+ days. Comment before closing to explain why. Use whenever the user says "clean up stale issues", "close old issues", "handle stale PRs", "prune inactive issues", or asks to close issues with no recent activity.
用 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-stale |
| description | Close stale GitHub issues and PRs that have had no activity for 60+ days. Comment before closing to explain why. Use whenever the user says "clean up stale issues", "close old issues", "handle stale PRs", "prune inactive issues", or asks to close issues with no recent activity. |
Find open issues and PRs with no activity in 60+ days, comment explaining the closure, and close them.
Stale threshold: 60 days of no activity (no comments, no label changes, no commits on a PR branch).
date -v-60d +%Y-%m-%d # macOS
# or
date -d "60 days ago" +%Y-%m-%d # Linux
gh issue list --state open --search "updated:<CUTOFF_DATE" --json number,title,updatedAt,labels,url --limit 200
Skip issues that are already labeled stale — they were already warned (close them, see Step 4).
gh pr list --state open --search "updated:<CUTOFF_DATE" --json number,title,updatedAt,author,url --limit 200
Skip draft PRs unless they're more than 90 days old — drafts are often long-lived WIPs.
For each stale issue, post a comment and close it in one command:
gh issue close <number> --comment "Closing due to 60 days of inactivity. If this is still relevant, please open a new issue with updated details — we're happy to revisit it."
For each stale PR, post a comment explaining the closure, then close:
gh pr close <number> --comment "Closing this PR due to 60 days of inactivity. If you'd like to continue the work, feel free to reopen or open a new PR — we'd be glad to review it."
If a PR has an associated branch that was created specifically for it (not main/master/develop), offer to delete the branch too, but don't do it automatically.
Closed N stale items:
- X issues (last activity: oldest to newest dates)
- X PRs (last activity: oldest to newest dates)
List each item with its number, title, and last-activity date so the user can spot anything that should have been kept open.