hawkingrei

Use when a Team inbox, channel, thread, or human-visible message must be routed into a direct reply, thread reply, mailbox update, task note, or canonical Team task.

Use before editing Team system prompts, runtime prompt tails, prompt-linked skills, or prompt tests to keep prompts bounded, tool-neutral, and pointer-first.

ACP rendering fixes for Team web surfaces.

Backend-first diagnosis for stuck AgentHub agents.

Journal writing for rollout notes and validation evidence.

Canonical feature spec writing for stable contracts.

Focused AgentHub test planning for behavior changes.

Repository title convention for commits and PRs.

Fix software bugs with root-cause analysis, minimal diffs, regression tests, and a mandatory self-check loop. Use for general bugfix work that is not covered by a more specific domain skill.

Fix TiDB optimizer bugs with minimal diffs, hypothesis-driven validation, and regression tests. Use the bundled issue precedents only to avoid re-fixing already solved bugs or inspect suspect historical fixes.

Gather PR review context: all comments (including review suggestions), diff context, and CI status; download GitHub Actions logs on failures. Prefer GitHub MCP for reads, fall back to gh CLI when needed.

Use for projects, tasks, or code that involve context engineering and context management for AI agents: keep prompt prefixes stable for KV-cache, use append-only context, prefer tool masking over tool removal, offload large observations into filesystem memory, recite goals/todos to control attention, preserve errors for recovery, and avoid few-shot pattern lock-in. Use when building or debugging agent loops, prompt/context schemas, memory strategies, or tool-availability policies.

TiDB-specific documentation lookup guided by this repo's llms.txt hub: read llms.txt, pick the best linked source (tidb-dev-guide llms-full.txt, TiDB user guide llms.txt, or Uber Go style guide), fetch it, then search within it to answer with precise references. Use when asked to find docs, research, or provide doc-grounded answers about TiDB development or usage.

Expertise in adding new test cases for the TiDB plan replayer. Use when the user provides a plan replayer zip file and wants to create a new test.

Processes and analyzes TiDB profiler zip packages (CPU or heap) for components like TiDB, TiKV, PD, or TiFlash. It unzips, aggregates the profiler data, and uses `go tool pprof` to report on the most time-consuming functions (CPU) or highest memory allocations (heap).

Create a TiDB bug issue from Shiro report artifacts and add a short root-cause analysis. Use when a Shiro report directory (summary.json/case.sql/plan_replayer.zip) is available and you need a ready-to-file GitHub issue body.