claude: add /escalation skill for systematic escalation diagnosis#167470
Open
wenyihu6 wants to merge 1 commit intocockroachdb:masterfrom
Open
claude: add /escalation skill for systematic escalation diagnosis#167470wenyihu6 wants to merge 1 commit intocockroachdb:masterfrom
wenyihu6 wants to merge 1 commit intocockroachdb:masterfrom
Conversation
Contributor
|
Merging to
After your PR is submitted to the merge queue, this comment will be automatically updated with its status. If the PR fails, failure details will also be posted here |
Member
|
This change is |
wenyihu6
force-pushed
the
wenyihu/escalation-skill
branch
2 times, most recently
from
d24ee9f to
499cdc5
Compare
This skill generates proof-style diagnostic frameworks for customer
escalations. Given a set of symptoms (e.g. "throughput tanks periodically",
"replicate queue failures from snapshot reservation timeouts"), the skill
produces a structured document that allows an on-call engineer to
systematically determine root cause.
Usage:
/escalation <symptoms>
The skill produces the following output:
1. **The Question** — what the framework is trying to determine.
2. **How the System Works** — a pipeline or architecture diagram showing
where in the request path the symptom can originate.
3. **Metrics Grouped by What They Prove** — each group answers a specific
diagnostic question with metric tables, key ratios, and Datadog
queries.
4. **Noise Sources to Rule Out** — metrics that look like the symptom but
have a different root cause, with instructions on how to distinguish.
5. **Decision Procedure** — numbered, elimination-based steps that
proceed from purest signal (pgwire layer) to most contaminated.
6. **Key Equations** — named formulas for derived metrics.
7. **Complete Metric List** — every metric referenced, with type
(gauge/counter/histogram) and Datadog query syntax.
The skill includes a comprehensive reference of ~130 CockroachDB metrics
organized into 16 categories (client-side, SQL, DistSender, transactions,
contention, store, network, memory, CPU, Pebble, admission control,
replication, leases, background workload, disk I/O, SQL memory pools).
Each metric is annotated with its type to ensure correct Datadog query
construction.
The core methodology is noise elimination through cross-layer
triangulation: no single metric proves a root cause because each is
contaminated by at least one system effect. The framework requires
agreement across independent measurement points (pgwire vs gateway vs
leaseholder) to constitute proof.
Epic: none
Release note: None
Co-Authored-By: roachdev-claude <roachdev-claude-bot@cockroachlabs.com>
wenyihu6
force-pushed
the
wenyihu/escalation-skill
branch
from
499cdc5 to
59f5b48
Compare
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
2 participants
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Summary
/escalationClaude Code skill that generates proof-style diagnostic frameworks for customer escalationsUsage
Examples:
/escalation throughput tanks periodically/escalation replicate queue failures from snapshot reservation timeouts/escalation high p99 latency on SELECT queriesOutput
The skill produces a markdown framework with:
Epic: none