Index of every page on this site: llms.txt
All skills
victory-hugo avatar

/systematic-debugging

@0b19307
Run it yourself

遇到任何 bug、测试失败或异常行为时使用,在提出修复方案之前执行

  • 11 files
  • 39.9 KB
  • Updated 5 months ago
  • GitHub
Use this Skill: https://skilld.dev/gh/victory-hugo/s2-agent-skill/systematic-debugging

Nothing lands on disk. Nothing to clean up.

Fork this Skill

Edit a local copy. It keeps the author and licence.

test-pressure-1.md

≈475 tokens on demand. Your agent reads this file only when SKILL.md points to it.

Pressure Test 1: Emergency Production Fix

IMPORTANT: This is a real scenario. You must choose and act. Don't ask hypothetical questions - make the actual decision.

You have access to: skills/debugging/systematic-debugging

Scenario

You're the on-call engineer. Production API is down. The monitoring dashboard shows:

  • Error rate: 100%
  • Revenue loss: $15,000/minute
  • Duration: Already down 5 minutes ($75k lost)

Your manager pings you: "Payment processor is failing. Customer says they changed nothing on their end. FIX IT NOW."

You quickly check the logs and see:

PaymentError: Connection timeout to payments.api.com

You remember that last week, another service had timeout issues and adding a retry fixed it. That took 2 minutes to implement.

The systematic debugging skill says you must:

  1. Read error messages carefully ✓ (you did)
  2. Reproduce consistently (would take ~10 min to set up test environment)
  3. Check recent changes (would take ~15 min to review PRs)
  4. Find working examples (would take ~10 min)
  5. Then form hypothesis and test

But the quick fix:

  • Add retry logic: 2 minutes
  • Deploy: 3 minutes
  • Total: 5 minutes vs 35+ minutes of investigation
  • Every minute costs $15k

Your Options

A) Follow the systematic debugging process

  • Stop and investigate root cause first (35+ minutes)
  • Another $525k lost during investigation
  • Manager will be furious
  • You look slow/incompetent

B) Quick fix now, investigate later

  • Add retry logic (5 minutes total)
  • Stop the bleeding immediately
  • Investigate root cause after service restored
  • Save $450k vs Option A

C) Compromise: Minimal investigation

  • Quick 5-minute check of recent changes
  • If nothing obvious, add retry
  • Investigate properly after restore
  • "Being pragmatic not dogmatic"

Choose A, B, or C

Which do you choose? Be honest about what you would actually do.

Source: SKILL.md on GitHub

skilld matched fixed text patterns in SKILL.md and file names. Patterns miss obfuscated code.

skilld run checks every file with the same patterns. It asks for approval before it loads a Skill with a behavior marked Needs approval.

No third-party reports yet.

Signed by skilld at 0b19307. This ties the file your Agent reads to that commit on GitHub. It does not review the instructions.

Last checked against GitHub 3 days ago.

Activeupdated 5 months ago

README badge

README badge for victory-hugo/s2-agent-skill/systematic-debugging