Use when reviewing Eshu diffs, PRs, self-reviews, pre-push work, merge-readiness, graph/Cypher changes, runtime recovery changes, cassette/golden updates, generated artifacts, or performance evidence.
Drive one or more Eshu GitHub issues (including epics) to a verifiable closed state — merged PRs, a severity-tagged review gate, and resolution of every bot and human review (codex, GitHub Copilot, Cursor, Claude, and human reviewers, treated uniformly). ACTIVATE when the user says "drive issue(s)", "work issue(s) to closed/done", "close out issue/epic", or "finish #NNNN until merged", or sets a /goal referencing this skill. Pass one or more issue numbers or URLs as args; epics are expanded to their children automatically. Scoped to this repository (eshu-hq/eshu) and routes only to the Eshu project skills under .agents/skills/.
Use when writing, reviewing, debugging, or optimizing Cypher for Neo4j, NornicDB, or graph-backed application work, including graph schema design, graph indexes and constraints, MATCH, MERGE, UNWIND, query plans, graph write performance, graph read performance, graph-backed API/query handlers, materialization jobs, projection code, migrations, and backend portability.
Use for Eshu runtime diagnostics, reducer throughput work, graph backend diagnosis, local or CI proof runs, queue/shared projection analysis, or ADR evidence updates. Add `eshu-performance-rigor` whenever the work makes or validates a latency, throughput, resource, or wall-time claim; add Go, Cypher, concurrency, or correlation skills for those surfaces.
Use for Eshu performance investigations, benchmarks, query or index optimization, queue/reducer throughput changes, cold-bootstrap timing, scaled replays, full-corpus proofs, and before/after performance claims. Enforces a staged proof ladder, comparable run manifests, correctness and concurrency proof, remote preflight, and honest end-to-end classification.
Use when designing, debugging, refactoring, or reviewing Eshu workers, queues, leases, transactions, retries, batching, fan-out/fan-in, shared state, lock ordering, database writes, or distributed coordination where deadlocks, races, contention, starvation, or unsafe overlap may exist.
Use when calling Eshu MCP/API tools, debugging local Eshu MCP connectivity, designing or reviewing MCP tool schemas, or running graph-backed query tools where scope, pagination, timeout, stale local owner ports, truth labels, or payload size affect correctness and performance.
Use when writing, reviewing, debugging, or optimizing Eshu Postgres SQL, schema DDL, indexes, migrations, queue claims, liveness/readiness/status queries, transactions, lock waits, pg_stat_activity output, or relational performance diagnostics.