菜单
Triage stale GitHub PRs. Use when asked to review old, inactive, least-recently-updated, obsolete, or closeable pull requests, comment with a recommendation, and close PRs that are clearly no longer useful.
用 Codex 或 Claude 帮你安装 复制这段 Prompt，粘贴到 Codex、Claude 或其他助手里，让它检查 Skill 页面并帮你完成安装。
基于 SOC 职业分类
Comprehensive knowledge of Fedi's testing infrastructure for UI code (utilities, mock builders, conventions, and patterns) — use this when reading, writing or running unit/integration/e2e tests
Use when changing, adding, or consuming Fedi remote feature flags across the bridge runtime and web API. Covers crates/runtime/src/features.rs, ui/web/src/pages/api/features.ts, TypeScript bindings, local testing, and selector usage.
Pre-submit checklist for PRs that change Rust or bridge code (`crates/`) in the Fedi project. Use before opening or updating a Rust or bridge PR to run the right local checks and structure the description. Not for UI (`ui/`), docs, or config-only changes, which have their own conventions.
Review a UI pull request or diff in the `ui/` workspace (web, native, shared `common`) for regressions and scope creep, weighing each finding by cost and blocking only on a named cost. Use whenever asked to review a UI or frontend PR or diff, or to check a web or native change before merge, even if the user does not say "code review". Not for Rust, bridge, or infra changes.
Review Dependabot PRs updating GitHub Actions workflows/actions, with a security-focused upstream diff check before commenting.
Review Dependabot PRs updating Rust/Cargo crates with a security-focused crates.io tarball diff before commenting.
| name | github-stale-pr-triage |
| description | Triage stale GitHub PRs. Use when asked to review old, inactive, least-recently-updated, obsolete, or closeable pull requests, comment with a recommendation, and close PRs that are clearly no longer useful. |
Use this when asked to look through old open PRs and decide what should happen with them.
First identify the exact PRs under consideration. Usually this means open PRs filtered by the user's requested age cutoff, count, labels, author, or least-recently updated order.
For each PR, one by one:
Always write the analysis as a PR comment. Keep it polite and short. Say what you checked, what you concluded, and what the next step should be. If closing, say it can always be reopened if something was missed.
Close when the conclusion is clear and the PR is no longer useful to keep open.
Report back with a short table: PR, decision, action taken, rationale.
