本文へ移動
cccskills
無料GitHub で公開

diagnose

Investigate unexpected behavior and mysterious bugs. Use when the cause of a problem is unknown and the user needs to understand WHY something is happening — symptoms like: sudden unexplained changes in metrics or behavior, works locally but not in staging/production, inconsistent or intermittent failures, correct code producing wrong results, operations succeeding but having no effect, environment-specific failures, duplicate executions, stale data, or any "why did this change?" or "why is this happening?" situation. Covers infrastructure anomalies (cache hit rates dropping, latency spikes, queue behavior shifts) as well as code bugs. The key signal is confusion about root cause, not a request to implement a known fix. Do NOT use for feature requests, known fixes, planning, or documentation tasks.

avibebuilder/claude-prime
インストール方法を見る

含まれるファイル（5）

  • SKILL.md4.6 KB
  • references/runtime-debugging.md4.3 KB
  • scripts/__tests__/diagnose-server.test.js8.3 KB
  • scripts/diagnose-server.js2.0 KB
  • scripts/package.json175 B

SKILL.md（原文）

インストールする前に、エージェントに与えられる指示の中身を確認できます。

Think harder.

Process

Check conversation context and skip completed steps.

1. Understand the symptom

  • Read the bug report, errors, logs, and surrounding code carefully
  • Clarify reproduction steps, expected behavior, and environment when they are unclear
  • Separate confirmed facts from working assumptions. List them explicitly:
    • Fact (confirmed): the server returns 200
    • Assumption (unconfirmed): the client receives the full HTML body Misidentifying an assumption as a fact is the most common source of wasted investigation.

2. Build hypotheses

  • Form 2-4 plausible root-cause hypotheses that are mechanistically distinct — different failure layers (e.g., server render vs. client hydration vs. network layer), not variations of the same idea

  • Rank them by likelihood

  • For each hypothesis, state both sides:

    • Confirm if: [what observation would prove this is the cause]
    • Eliminate if: [what observation would rule this out]

    A hypothesis you can't falsify in both directions is too vague to test.

3. Choose the lightest evidence method

Start with the cheapest source of truth that can kill hypotheses:

  • existing logs, traces, stack traces, metrics, and error output
  • static code inspection around the suspected path
  • config, environment, deploy, cache, queue, and permissions state that could explain the symptom
  • targeted reproduction in the relevant environment

Only add new instrumentation when existing evidence is insufficient.

  • If you need runtime probes, read diagnose/references/runtime-debugging.md
  • Use #region agent log / #endregion markers for any instrumentation you add
  • Tag each log point with the relevant hypothesisId
  • Log only the minimum fields needed to discriminate between hypotheses; never log secrets, tokens, passwords, cookies, or full sensitive payloads
  • If runtime probes require starting the local debug server, ask the user before launching it
  • For browser/UI bugs, combine with the agent-browser skill when reproduction or inspection needs it

4. Gather evidence and iterate

  • Use existing logs, traces, failing tests, or artifacts before asking for a fresh reproduction
  • When reproduction is needed, ask the user to trigger the bug — tie each request to the hypothesis it tests
  • Correlate each finding with the hypothesis it supports or eliminates; narrow based on evidence, not confidence
  • If ambiguity remains, refine hypotheses and add narrower probes — but stop and report when another round is unlikely to produce new discriminating evidence

5. Report the diagnosis

Output structured diagnosis:

## Diagnosis: [Issue Title]

### Symptoms
- [What was observed]

### Evidence
- [Finding] — `file:line` or runtime source — hypothesis X
- ...

### Root Cause
[Confirmed or most likely cause, with evidence]

### Hypotheses Tested
| # | Hypothesis | Confirm if | Eliminate if | Result |
|---|-----------|-----------|-------------|--------|
| A | ... | [what observation would prove this] | [what observation would rule this out] | Confirmed/Eliminated/Inconclusive |

### Recommended Next Steps
- [What to do next — usually hand off to `/fix` with this diagnosis]

### Active Instrumentation
- [List files with `#region agent log` blocks still in place, or `None`]

Constraints

  • NO fixing — investigation and diagnosis only. "Recommended Next Steps" hands off to /fix with the diagnosis; it does not prescribe specific parameter values, code snippets, or step-by-step implementation instructions.
  • Evidence over assumptions — if the code looks wrong but runtime evidence says otherwise, trust the runtime
  • If you add #region agent log blocks, leave them in place for /fix to verify the repair and call them out in the final report

Bug

<bug>$ARGUMENTS</bug>

レビュー

まだレビューはありません。使ってみた感想をお寄せください。

ログインしてレビューを書く

同じリポジトリのスキル

概要と使いどころ

agent-browser

無料

Browser automation CLI for AI agents. Use when the user needs to interact with websites, including navigating pages, filling forms, clicking buttons, taking screenshots, extracting data, testing web apps, or automating any browser task. Triggers include requests to "open a website", "fill out a form", "click a button", "take a screenshot", "scrape data from a page", "test this web app", "login to a site", "automate browser actions", or any task requiring programmatic web interaction.

日本語の概要は準備中です。原文の説明を表示しています。

avibebuilder/claude-prime1202026年5月17日 更新

ask

無料

Answer questions about code, architecture, and technical decisions — no implementation. Trigger on questions asking 'why', 'what does this do', 'what is the purpose of', 'explain', 'what's the difference', 'compare', or 'what are the tradeoffs' — even when referencing specific files, code snippets, or inline code. The key signal is the user wants to UNDERSTAND something, not change it. Do NOT trigger for requests to build, fix, plan, review, research, or add/modify code.

日本語の概要は準備中です。原文の説明を表示しています。

avibebuilder/claude-prime1202026年5月17日 更新

backend-fastapi-python

無料

Use this skill for any Python backend work in this project: building FastAPI endpoints, writing service functions, defining Pydantic/SQLModel schemas, running Alembic migrations, or debugging 422 errors. Essential for authentication and authorization patterns — setting up get_current_user, is_superuser checks, admin-only guards, role-based access, and dependency injection chains like Depends(). Also covers middleware, background tasks, async SQLAlchemy sessions, ORM relationship loading, and request/response design. Activate whenever the question involves Python API code, FastAPI patterns, or backend architecture in this codebase. Not for frontend, Docker, CI/CD, or infrastructure.

日本語の概要は準備中です。原文の説明を表示しています。

avibebuilder/claude-prime1202026年5月17日 更新

cook

無料

Implement, build, create, or add any feature, endpoint, page, component, or functionality. Use this skill whenever the user asks you to write new code or make code changes — whether it's adding an API endpoint, building a UI page, creating an export feature, wiring up a webhook, implementing a search/filter, or any other hands-on coding task. This is the default skill for all 'build this', 'add this', 'create this', 'wire up', 'implement' requests. Covers the full cycle: clarify requirements, plan if needed, write code, verify, and review. Do NOT use for pure research, debugging, documentation, or explanation — only when the user wants working code delivered.

日本語の概要は準備中です。原文の説明を表示しています。

avibebuilder/claude-prime1202026年5月17日 更新

create-doc

無料

Use when the user wants to save knowledge as a file so others don't have to rediscover it — "turn this into a doc", "write this up", "document how X works", "we figured this out and want to capture it", "nobody should have to figure this out again". Covers any request to create or update durable written artifacts: onboarding guides, runbooks, ADRs, API docs, architecture notes, postmortems, changelogs, setup guides. The trigger: user wants knowledge captured in a file for future reference, not just a conversation. Do NOT use when still making decisions (→ give-plan), just asking for explanation without a file (→ ask), or writing code (→ cook).

日本語の概要は準備中です。原文の説明を表示しています。

avibebuilder/claude-prime1202026年5月17日 更新

discuss

無料

Brainstorms and debates approaches, then drives toward an actionable decision. Use whenever someone needs a thinking partner for a decision they're facing: 'discuss', 'debate', 'brainstorm', 'weigh options', 'tradeoffs', 'should I do X or Y', 'help me decide', 'I'm torn between', 'sanity check my thinking', or 'what do you think about'. The user must be asking for help reasoning through a choice — not asking to build, fix, evaluate, plan, or modify something (even if the topic involves this skill itself). Picks the right decision lens, surfaces tradeoffs and blind spots, pushes back when reasoning is genuinely weak, and never implements.

日本語の概要は準備中です。原文の説明を表示しています。

avibebuilder/claude-prime1202026年5月17日 更新

avibebuilder のスキルをすべて見る

このスキルの問題を報告する