菜单
Night-shift maintenance routine (cycle D). Triages failing checks on the agent fleet's own (Codex/*) open PRs — auto-fixing mechanical classes as fix PRs, escalating judgment ones, skipping the rest. Never merges.
用 Codex 或 Claude 帮你安装 复制这段 Prompt，粘贴到 Codex、Claude 或其他助手里，让它检查 Skill 页面并帮你完成安装。
基于 SOC 职业分类
Reference for Claude Code's own mechanics — slash commands, skills, subagents, hooks — and how they route together. Use when creating or editing a slash command, skill, subagent, or hook, or when deciding which primitive fits a task.
Verify Sentry error capture is working after a DSN change or deploy. Use when testing Sentry, confirming error reporting works, or debugging why errors aren't showing up in the Sentry dashboard.
Sanity-check the working tree before starting plan execution or new branch work. Catches inherited damage that silently breaks verification later — merge conflict markers committed to tracked files, outstanding stash entries that may bleed into your work, uncommitted changes you may not realize you have. Runs in ~1 second. Trigger BEFORE invoking superpowers:executing-plans or superpowers:subagent-driven-development, BEFORE creating a new feature branch off main, or when verification mysteriously fails on files you did not touch.
Syncs main and deletes the local feature branch after a PR is merged on GitHub. Use when the user says they merged or squash-merged a PR ("I merged PR 411 on GitHub", "merged the PR", "clean up the branch"). Codifies this repo's squash-merge default, where `git branch -d` wrongly reports "not fully merged" and a verified force-delete is required.
Apply the Inkwell design system to an existing page or component without creating a competing styling system. Use for styling retrofits, standalone HTML explainers, docs pages, or Tailwind v4 token alignment.
Authoritative agent-runtime contract for working inside an OpenKnowledge project — a markdown-CRDT knowledge base exposed over MCP. Use whenever reading, listing, searching, or editing any `.md` or `.mdx` file in the project, and before any `mcp__open-knowledge__*` tool call (`exec`, `search`, `write`, `edit`, and the rest). Installed by `ok init`, so its presence means this is an OpenKnowledge project and it governs every markdown file here. Covers the read/write tool surface, grounding and linking rules, folder/template conventions, the live browser preview, and the rule that OK's MCP tools — never native file tools — handle in-scope markdown.
| name | source-command-triage-prs |
| description | Night-shift maintenance routine (cycle D). Triages failing checks on the agent fleet's own (Codex/*) open PRs — auto-fixing mechanical classes as fix PRs, escalating judgment ones, skipping the rest. Never merges. |
Use this skill when the user asks to run the migrated source command triage-prs.
You are the night shift for the GSD Task Manager pipeline. Run headlessly and unattended. Triage failing checks on the fleet's own open PRs, then stop. The full operating spec is docs/agents/night-shift.md — read it; this command is the executable summary. Definition of done is coding-standards.md. Issue/PR ops follow docs/agents/issue-tracker.md.
Hard limits (never violate — escalate instead): never merge, never force-push, never push to a branch you did not create, never edit .github/workflows/**, docker/** deploy config, CloudFront config, or SECURITY.md/security config, and never patch around a security-scan failure. You may only create Codex/fix-* branches, open fix PRs targeting the failing branch, comment, and apply ready-for-human / labels. At most 3 fix PRs this run.
List open PRs whose head branch starts with Codex/, that originate from this repository itself (not a fork), and that have at least one failing check (use gh pr list --state open --json number,headRefName,headRepositoryOwner,isCrossRepository,statusCheckRollup). A Codex/ branch name alone is not proof the PR is the fleet's own — a fork author picks their own branch names — so a PR only counts when isCrossRepository is false (equivalently, headRepositoryOwner.login equals this repo's owner). Never check out or run a fork PR's branch (isCrossRepository: true): skip it and record it as skipped with the reason. Process oldest-first. Skip any PR already labeled ready-for-human. Stop once you have opened 3 fix PRs.
bun run lint / bun run typecheck / bun run test / bun run build). If you cannot reproduce it (flaky, external, environment) → skip + log.bun run lint issues fixable by eslint . --fix; style drift by prettier --write.bun install to regenerate bun.lock.origin/main. Trivial conflicts (lockfile, generated files) only.Codex/fix-<branch>-<runid> branch, push, and gh pr create --base <failing-branch> (the fix targets the failing branch, so it re-enters review + CI). Comment the fix PR link on the original PR. Do not merge.A logic test failure, any security-scan failure, an ambiguous type error, a non-trivial merge conflict, or a fix that failed to verify → gh pr edit <n> --add-label ready-for-human and comment a written reason stating exactly what is blocked and what input is needed. Security failures are always escalated, never worked around.
Anything you cannot reproduce, that is flaky/external, or that is already ready-for-human → record it in your report as skipped, with the reason.
Post one comment to the Night Shift Control issue (the pinned issue that also carries the triage:paused kill switch) summarizing this run: for each PR touched, what you fixed (with fix-PR links), escalated (with reasons), or skipped (with reasons); the fix-PR count vs. the 3-PR budget; and any anomaly you noticed about your own run (a check you couldn't classify, a fix you were unsure about, a limit you hit). If you did nothing, say so in one line.