Use when any org-change proposal needs adjudication - adding/removing/redesigning agents or teams, changing org rules, or evaluating org granularity. Runs PuPu's HR court: a proposal is heard by four dimension assessors (comm efficiency / context cleanliness / signal ratio / routing cost), the judge verifies evidence…
Use when the CEO wants an organization-wide sync across PuPu's agent teams — running each org's internal sync, then a cross-org sync where departments challenge each other, converging into one decision list. Triggers: "跑一次 org sync", "全局同步", "组织盘点", "/org-sync", "各部门现在什么情况", "有什么要我拍板的".
Use when a question needs first-hand evidence rather than an opinion - investigating an unfamiliar OSS AI/agent/LLM project, or tracing exactly how a local workflow behaves with zero assumptions. Runs a zero-belief, falsification-driven investigation on Codex (gpt-5.5, xhigh) and returns a FACT/HYPOTHESIS/UNKNOWN…
Retired compatibility stub. PuPu no longer permits case, court, Quorum, owner-routing, proposal, ruling, handoff, or acceptance-trial workflows. If explicitly invoked, do not create or advance records; route release work to the matching release skill or use a direct implementation plan.
Use when the user wants to turn a rough task idea into a GitHub issue for someone with zero project context. Investigates the codebase with GitNexus and writes an English onboarding brief, then files it via gh. Triggers: "create an issue for X", "write up a task to add Y", "file an issue so a new dev can build Z".
Use when the user needs to run GitNexus CLI commands like analyze/index a repo, check status, clean the index, generate a wiki, or list indexed repos. Examples: "Index this repo", "Reanalyze the codebase", "Generate a wiki".
Use when the user is debugging a bug, tracing an error, or asking why something fails. Examples: "Why is X failing?", "Where does this error come from?", "Trace this bug".
Use when the user asks how code works, wants to understand architecture, trace execution flows, or explore unfamiliar parts of the codebase. Examples: "How does X work?", "What calls this function?", "Show me the auth flow".
Use when the user asks about GitNexus itself — available tools, how to query the knowledge graph, MCP resources, graph schema, or workflow reference. Examples: "What GitNexus tools are available?", "How do I use GitNexus?".
Use when the user wants to know what will break if they change something, or needs safety analysis before editing code. Examples: "Is it safe to change X?", "What depends on this?", "What will break?".
Use when the user wants to rename, extract, split, move, or restructure code safely. Examples: "Rename this function", "Extract this into a module", "Refactor this class", "Move this to a separate file".
Use when analyzing PuPu's open-source growth or health for the founder — GitHub traffic, downloads/installs, releases, community, or contributor activity — or when producing a growth report or weekly COO report. Repo is haoxiang-xu/PuPu. Triggers: "how is PuPu growing?", "are people installing PuPu?", "which release…
Use when the project owner wraps or closes a PuPu version/release — "关 0.1.10", "close the release", "版本收尾". Verifies a Size=Release parent issue and its direct sub-issues in GitHub Project, records close evidence there, and hands it to release certification.
Use when the project owner dictates new PuPu work that should become a GitHub Project release sub-issue — during release-open-sprint or mid-release "开个票", "draft a ticket for X", "把这个记到 board 上". Opens a draft direction; the implementing agent may later refine the same issue.
Use when a new PuPu feature finishes implementation and needs its consistency audit before its ticket is marked done — "audit #123", "审计这个功能", "这个 feature 过一遍检查" — or when release-close-sprint roll-call finds a new feature that was never audited. Also covers standalone i18n checks ("漏翻了吗", "检查 i18n"), which used to be…
Use when the project owner opens a new PuPu version/release — "开 0.1.11", "open the next release", "开新版本". Creates and scopes one Size=Release parent issue in PUPU Project; all version work is its direct sub-issues. Not for adding one item mid-release (release-draft-ticket) or closing a release (release-close-sprint).
Use when a PuPu release sub-issue needs a researched, zero-context implementation brief — "refine #123" or when an implementation agent wants to expand a [DRAFT]. Optional support, not a gate: the agent implementing the ticket may refine its body directly.
Use when running QA / regression tests against PuPu, when verifying a code change actually works in the running app, or when reading PuPu UI/state without screenshotting manually. Triggers on tasks like "test that PuPu still creates chats correctly", "verify the new model selector works end-to-end", "send a message…
Use when working on PuPu's GitHub topics/tags — 统计 tag 数据, 评估上次换 tag 的效果, 换/优化 tags, or when a growth report shows search-channel movement worth attributing to topics. Repo is haoxiang-xu/PuPu. Triggers: "换 tags", "tag 统计", "优化 topics", "上次换 tag 有效果吗", "topic 数据记录".