Run any Skill in Manus with one click

issue-triage-and-repro

Stars31

Forks9

UpdatedMarch 14, 2026 at 18:20

Triage bug reports and reproduce extension issues consistently in this repository. Use when analyzing user-reported failures, validating reproduction steps, collecting debug evidence, and preparing actionable fix notes.

Installation

Install with Codex or Claude Copy this prompt, paste it into Codex, Claude, or another assistant, and let it review the skill page and install it for you.

Run Skill in Manus

Source

jgkme

jgkme/Add-Remote-Torrent

View GitHub Repository View Creator Repositories

Download

Run Skill in Manus

Related occupationsSOC

Based on SOC occupation classification

Software DevelopersComputer and Mathematical Occupations·SOC 15-1252

SKILL.md

readonly

name	issue-triage-and-repro
description	Triage bug reports and reproduce extension issues consistently in this repository. Use when analyzing user-reported failures, validating reproduction steps, collecting debug evidence, and preparing actionable fix notes.

Issue Triage And Reproduction

Triage Workflow

Capture environment details: extension version, browser version, client type/version.
Classify impact: data loss, broken core flow, degraded UX, or cosmetic.
Identify scope: one client handler, one page, or cross-cutting behavior.
Reproduce with minimal steps and deterministic inputs.

Reproduction Checklist

Confirm relevant settings in options (server profile, auth, rules).
Reproduce on one known-good site/link and one failing case.
Record exact user-visible error message from popup/dashboard.
Collect console logs from affected surface (options/popup/background).
Note whether issue is stable, intermittent, or race-dependent.

Investigation Notes Format

Use short sections:

Observed: What happened.
Expected: What should happen.
Likely Area: File/module candidates.
Evidence: Error text, logs, response snippets.
Next Step: Smallest safe code/test change.

Done Criteria

Reproduction steps are clear and repeatable.
Evidence is sufficient for another developer to implement a fix.
Priority and user impact are explicitly stated.

More from this repository

same repository

release-packaging-checklist

jgkme/Add-Remote-Torrent

Create and verify release artifacts for this extension using the existing build pipeline. Use when bumping versions, generating zip/crx files, computing checksums, and checking release consistency.

2026-05-2131

version-bump-and-changelog

jgkme/Add-Remote-Torrent

Perform safe extension version bumps and changelog updates for this repository. Use when preparing a release, synchronizing version metadata, updating changelog entries, and validating generated artifacts.

2026-05-2131

chrome-extension-mv3-workflow

jgkme/Add-Remote-Torrent

Build, debug, and validate Chrome Extension Manifest V3 changes in this repository. Use when editing background service worker logic, content scripts, popup/options pages, permissions, or extension messaging.

2026-03-1431

torrent-client-handler-patterns

jgkme/Add-Remote-Torrent

Implement and review torrent client API handlers consistently across this repository. Use when adding or fixing files in api_handlers, authentication flow, request formatting, or post-add operations like labels, categories, and directories.

2026-03-1431

name	issue-triage-and-repro
description	Triage bug reports and reproduce extension issues consistently in this repository. Use when analyzing user-reported failures, validating reproduction steps, collecting debug evidence, and preparing actionable fix notes.

Issue Triage And Reproduction

Triage Workflow

Capture environment details: extension version, browser version, client type/version.
Classify impact: data loss, broken core flow, degraded UX, or cosmetic.
Identify scope: one client handler, one page, or cross-cutting behavior.
Reproduce with minimal steps and deterministic inputs.

Reproduction Checklist

Confirm relevant settings in options (server profile, auth, rules).
Reproduce on one known-good site/link and one failing case.
Record exact user-visible error message from popup/dashboard.
Collect console logs from affected surface (options/popup/background).
Note whether issue is stable, intermittent, or race-dependent.

Investigation Notes Format

Use short sections:

Observed: What happened.
Expected: What should happen.
Likely Area: File/module candidates.
Evidence: Error text, logs, response snippets.
Next Step: Smallest safe code/test change.

Done Criteria

Reproduction steps are clear and repeatable.
Evidence is sufficient for another developer to implement a fix.
Priority and user impact are explicitly stated.