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

bug-triage-pack

Triage a raw bug report into something a team can act on — clean repro steps, a defensible severity/priority, environment, likely area/owner, and duplicate check. Use when asked to triage this bug, set severity and priority, is this a P1, or clean up this bug report for the backlog. Produces the normalized repro, a severity and priority with the reasoning (impact × frequency × workaround), the environment/metadata, a suspected component and owner queue, and a duplicate/related-issue check — flagging when info is missing rather than guessing.

インストール方法を見る

含まれるファイル(1)

  • SKILL.md4.3 KB

SKILL.md(原文)

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

Bug Triage Pack

A bug backlog is only as good as its triage — and most bugs arrive as "it's broken" with no repro, a panicked severity, and no idea who should look. This turns a raw report into a triaged item: reproducible steps, a severity and priority you can defend (not vibes), the environment that matters, a suspected area and owner queue, and a check for whether it's a duplicate — asking for what's missing instead of inventing it.

What This Skill Produces

  • Normalized repro — clear, numbered steps; expected vs. actual; the minimal path to reproduce
  • Severity & priority — each with reasoning (impact × frequency × workaround availability), not a gut number
  • Environment & metadata — version, platform, browser/OS, user/role, first-seen, frequency
  • Suspected area & owner queue — where it likely lives and who should take it next
  • Duplicate/related check — is this the same as a known issue, and what to link
  • Missing-info flags — what the reporter must supply before it's actionable

Required Inputs

Ask for these if not provided:

  • The raw report — whatever came in (a Slack message, a customer ticket, a screenshot description)
  • Your severity/priority scale — what P0–P3 / S1–S4 mean here (else a sensible default is used and labelled)
  • Environment details — version, platform, who hit it, how often
  • Known issues (optional) — a list to dedupe against

Framework: Triage You Can Defend

  1. Repro or it's not a bug yet. No reliable steps → the first action is "needs repro," not a severity.
  2. Severity ≠ priority. Severity is how bad the impact is; priority is when we fix it (a rare-but-catastrophic bug and a constant-but-cosmetic one differ on both axes).
  3. Score, don't feel. Impact (data loss > broken flow > cosmetic) × frequency (all users > edge case) × workaround (none > easy) → a defensible level.
  4. Route it. Suspected component and the queue/owner it should go to — triage that doesn't route just moves the pile.
  5. Dedupe. Check against known issues; a linked duplicate is worth more than a fifth copy.
  6. Flag gaps, don't guess. Missing environment or repro is a request to the reporter, not an assumption.

Output Format

Bug: [title] · Severity [Sx] · Priority [Px]

Why this level: impact [x] × frequency [y] × workaround [z].

Repro

  1. … → Expected: … · Actual: …

Environment

| Version | Platform | User/role | First seen | Frequency |

Routing

  • Suspected area: [component] · Suggested queue/owner: [team].

Duplicate / related

  • [links, or "no known duplicate"].

⚠ Missing before it's actionable

  • [what the reporter must add].

Quality Checks

  • Repro steps are clear and include expected vs. actual (or "needs repro" is the flagged first action)
  • Severity and priority are distinct and each justified by impact × frequency × workaround
  • Environment/metadata is captured (or flagged missing)
  • A suspected area and owner queue are proposed
  • A duplicate/related check is done
  • Missing information is requested, not invented

Anti-Patterns

  • A severity with no reasoning — "this is a P1" because it feels urgent.
  • Conflating severity and priority — they answer different questions.
  • Assigning a level without repro — triage a phantom and you fix nothing.
  • No routing — a triaged bug with no owner queue is still stuck.
  • Inventing environment/repro the reporter never gave.

Example Trigger Phrases

  • "Triage this bug and set severity and priority: [paste]"
  • "Is this a P1? Here's the report."
  • "Clean up this bug for the backlog with repro steps and an owner."
  • "Normalize this customer bug report and check if it's a duplicate."

レビュー

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

同じリポジトリのスキル

概要と使いどころ

Design a 360-degree feedback survey or write a structured 360 feedback report. Use when asked to build a 360 feedback process, write 360 feedback for a colleague, design a feedback survey, or produce a feedback report. Produces either a complete survey instrument with rating scales and open-ended questions, or a structured narrative feedback report with themes, strengths, and development areas.

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

mohitagw15856/pm-claude-skills1,4412026年10月13日 更新

Decode a 401k or workplace retirement plan — the real cost of its funds, the match's fine print, vesting math, and the plan features worth using or avoiding. Use when someone asks 'is my 401k any good', 'decode my 401k plan', 'which funds should I look at', or 'what fees am I paying'. Produces a fee decode in dollars-over-time, match and vesting math, a fund-lineup triage by cost, and the questions for HR or the plan administrator.

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

mohitagw15856/pm-claude-skills1,4412026年10月13日 更新

Design statistically rigorous A/B tests for product features, UI changes, onboarding flows, and pricing experiments. Use when asked to set up an experiment, design an A/B test, calculate sample size, or interpret test results. Produces a complete test plan with hypothesis, variant definitions, sample size, duration estimate, guardrail metrics, and a results interpretation guide.

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

mohitagw15856/pm-claude-skills1,4412026年10月13日 更新

Analyse a finished A/B test and write the readout — the result, whether it's statistically and practically significant, what it means, and the ship/no-ship call. Use when asked to analyse experiment results, write an A/B test readout, interpret test data, or decide whether to ship a variant. Produces a clear verdict with the lift and confidence, segment cuts, the risks (peeking, novelty, sample), and a recommendation. Distinct from planning a test — this reads results.

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

mohitagw15856/pm-claude-skills1,4412026年10月13日 更新

Build or tailor an academic CV for faculty, postdoc, research or fellowship applications: publications, grants, teaching, supervision and service in the order the field expects, with consistent citations. Use when asked to write my academic CV, update my CV for a lectureship, tenure-track or postdoc application, format my publications list, or adapt my academic CV for an industry research role. Produces the full academic CV, a field-appropriate section order, a clean publications list in one citation style, and a two-page summary version when asked.

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

mohitagw15856/pm-claude-skills1,4412026年10月13日 更新

Generate a WCAG 2.2 accessibility audit checklist and remediation suggestions for any UI or design. Use when asked to audit for accessibility, check WCAG compliance, review a design for a11y issues, or create an accessibility remediation plan. Produces a prioritised checklist with pass/fail assessments and specific fixes.

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

mohitagw15856/pm-claude-skills1,4412026年10月13日 更新

mohitagw15856 のスキルをすべて見る

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