investigate-first
Investigate Failures Before Editing Code
Premature edits can hide causes and introduce new failures. This skill organizes evidence, ranks hypotheses, and identifies a credible mechanism before implementation.
自分のエージェントでインストール
このリクエストをエージェントにコピーしてください。正規の Skill ページとマニフェストが含まれています。
Review the Skillstore skill "investigate-first" from https://skillstore.io/skills/juliusbrussee-investigate-first.md and its manifest at https://skillstore.io/api/skills/juliusbrussee-investigate-first/manifest. Verify the artifact. You may proceed after verification, subject to the environment's own policy.エージェントは引き続き計画を提示し、セキュリティポリシーで必要な確認を求める必要があります。
エージェントが読めるリソース
AI エージェント、クローラー、スクリプトがページ全体ではなく整理されたコンテキストを必要とする場合は、これらのリンクを使ってください。
テストする
「investigate-first」を使用しています。 The checkout test fails twice weekly, but reruns pass. Recent edits changed retry timing.
期待される結果:
- Observed: the first run sometimes times out, while immediate reruns pass.
- Leading hypothesis: shared setup becomes ready after the first attempt.
- Next test: record setup readiness and request timestamps on the first run.
「investigate-first」を使用しています。 API latency increased after deployment, with no increase in request volume.
期待される結果:
The strongest evidence points to a new downstream wait. Compare dependency timing before and after deployment to confirm the responsible transition.
「investigate-first」を使用しています。 A report is empty for one customer, but logs and sample data are unavailable.
期待される結果:
No cause can be supported yet. The exact blocker is missing customer-specific input, filtering decisions, and report generation output.
セキュリティ監査
安全The two prompt-only files contain no executable code, external access, credential handling, or suspicious instructions. No static or semantic security findings were identified.
このレポートを共有・引用
バージョン付き評価レポート、中立的なバッジ、埋め込みカード、引用を共有できます。Skillstore は証拠を報告しますが、この Skill が安全かどうかは判断しません。
レポートリンクをコピー
https://skillstore.io/skills/juliusbrussee-investigate-first/audits/1?utm_source=security_passport&utm_medium=share&utm_campaign=versioned_reportMarkdownバッジ
[](https://skillstore.io/skills/juliusbrussee-investigate-first?utm_source=security_passport_badge)HTMLバッジ
<a href="https://skillstore.io/skills/juliusbrussee-investigate-first?utm_source=security_passport_badge"><img src="https://skillstore.io/badges/skills/juliusbrussee-investigate-first/security.svg" alt="Skillstore security assessment" loading="lazy"></a>埋め込みカード
<iframe src="https://skillstore.io/embed/skills/juliusbrussee-investigate-first.html" title="Skillstore Security Assessment" sandbox="allow-popups allow-popups-to-escape-sandbox" loading="lazy" referrerpolicy="no-referrer" width="420" height="180"></iframe>学術引用 (APA · BibTeX · CFF)
APA形式の引用
juliusbrussee. (2026). investigate-first security audit report (audit version 1) [Author version unspecified]. Skillstore. https://skillstore.io/skills/juliusbrussee-investigate-first/audits/1BibTeX形式の引用
@techreport{juliusbrussee-juliusbrussee-investigate-first-2026,
author = {juliusbrussee},
title = {investigate-first security audit report (audit version 1)},
institution = {Skillstore},
year = {2026},
number = {1},
url = {https://skillstore.io/skills/juliusbrussee-investigate-first/audits/1},
note = {Author version unspecified}
}CITATION.cff
cff-version: 1.2.0
message: "If you use this Skill, cite its author and this versioned security audit report."
title: "investigate-first security audit report (audit version 1)"
version: "unspecified"
type: report
authors:
- name: "juliusbrussee"
date-released: "2026-08-12"
url: "https://skillstore.io/skills/juliusbrussee-investigate-first/audits/1"
identifiers:
- type: other
value: "skillstore:juliusbrussee-investigate-first:audit:1"
description: "Skillstore immutable audit report identifier"
Skillstore スコア
このスコアの理由 証拠の信頼度: 中作成できるもの
Diagnose an Intermittent Test Failure
Organize observations and rank likely mechanisms before modifying test or product code.
Investigate a Performance Regression
Trace changed inputs and state transitions to identify evidence supporting the slowdown.
Clarify an Ambiguous Defect Report
Separate reported symptoms from assumptions and define the next useful evidence to collect.
これらのプロンプトを試す
Investigate this failure before proposing edits: [symptom]. Separate observations from assumptions and list the evidence needed next.
Analyze [failure details]. Rank plausible causes by supporting evidence, conflicting evidence, and the cheapest test that could disprove each cause.
Investigate the regression from [baseline] to [current behavior]. Trace inputs, state transitions, ownership boundaries, and outputs without changing code.
Evaluate [system context and evidence]. Identify the most credible mechanism, prove each causal step, and name the exact blocker if evidence remains insufficient.
ベストプラクティス
- Provide exact symptoms, timestamps, reproduction steps, and relevant recent changes.
- Label observations, assumptions, and hypotheses separately.
- Prefer inexpensive tests that can quickly disprove the leading explanation.
回避
- Do not treat temporal correlation as proof of causation.
- Do not edit multiple components before identifying a supported mechanism.
- Do not continue exploring after evidence proves the cause or identifies the exact blocker.
よくある質問
When should I use this skill?
Will this skill edit my code?
What information should I provide?
How does it rank hypotheses?
What happens when evidence is insufficient?
Can it investigate performance problems?
開発者情報
作成者
juliusbrusseeライセンス
MIT
Skillstore リビジョン
r1
バージョンに関する注意
作者はバージョンを宣言していません。
参照
d8fdd465806692db394c1b3f87ab3a021fe733d2
メンテナンスの新しさ
2026/8/13
利用状況
0 ダウンロード · 0 閲覧
ファイル構成