triage-issues

Estrelas10

Forks1

Atualizado24 de março de 2026 às 12:17

Guides bug report and pull request investigation and reproduction. Confirms reported behavior is wrong, reproduces issues locally, and checks for correct-by-design behavior before writing fixes. Use when given a bug report, issue, or error report to investigate.

Instalação

Instalar com Codex ou Claude Copie este prompt, cole no Codex, Claude ou outro assistente e deixe que ele revise a página da skill e instale para você.

Fonte

webpro

webpro/skills

Abrir repositório GitHub Ver repositórios do creator

Download

Ocupações relacionadasSOC

Baseado na classificação ocupacional SOC

Analistas de garantia de qualidade de software e testadoresInformática e Matemática·SOC 15-1253

SKILL.md

readonly

name	triage-issues
description	Guides bug report and pull request investigation and reproduction. Confirms reported behavior is wrong, reproduces issues locally, and checks for correct-by-design behavior before writing fixes. Use when given a bug report, issue, or error report to investigate.

When given a bug report or a link to issue or pull request, first confirm current behavior is actually wrong
Reproduce, then check if the reported behavior is correct-by-design before writing any fix
Find repositories/CodeSandbox/StackBlitz source files and local fixtures to actually reproduce the issue at hand
To fetch stackblitz.com reproduction url: pnpx stackblitz-zip https://stackblitz.com/edit/{name} {filename}.zip
If no reproduction provided, create a minimal one from the report
Trace the full code path end-to-end for full context and consider options — don't blindly apply a local fix
Look up relevant fixtures and tests to better understand scope and context
Check git blame/git log around the affected area for recent changes

Mais deste repositório

mesmo repositório

clean-git-repo

webpro/skills

Clean up a git repository: delete branches whose PRs merged (incl. squash-merges), remove their safely removable linked worktrees, list or delete local branches past a confirmed age threshold, prune stale remote-tracking refs and worktree metadata, and optionally prune local tags absent from the remote, run gc, or delete merged remote branches. Use when asked to clean up / prune / tidy git branches or worktrees, remove merged or stale branches, delete old branches, prune origin/* refs, or clear out a repo's branch/worktree list, including from a directory containing worktrees from one or more repositories. Reports first (dry run); never touches current/default/kept branches or main, dirty, ignored-content, locked, detached, unavailable, or submodule-containing worktrees.

2026-07-2310

optimize-javascript

webpro/skills

V8/Node.js performance patterns for hot paths, parsers, and core libraries in JavaScript/TypeScript. Use when writing or reviewing performance-sensitive JS/TS code.

2026-06-3010

configure-knip

webpro/skills

Set up and optimize Knip configuration to find unused files, dependencies, and exports. Use when configuring knip.json or cleaning up a JavaScript or TypeScript codebase.

2026-06-0210

suggest-pr-reviewers

webpro/skills

Find relevant PR reviewers based on code ownership and recency of contributions. Use when creating PRs or needing to identify who should review code changes.

2026-03-2410

name	triage-issues
description	Guides bug report and pull request investigation and reproduction. Confirms reported behavior is wrong, reproduces issues locally, and checks for correct-by-design behavior before writing fixes. Use when given a bug report, issue, or error report to investigate.

When given a bug report or a link to issue or pull request, first confirm current behavior is actually wrong
Reproduce, then check if the reported behavior is correct-by-design before writing any fix
Find repositories/CodeSandbox/StackBlitz source files and local fixtures to actually reproduce the issue at hand
To fetch stackblitz.com reproduction url: pnpx stackblitz-zip https://stackblitz.com/edit/{name} {filename}.zip
If no reproduction provided, create a minimal one from the report
Trace the full code path end-to-end for full context and consider options — don't blindly apply a local fix
Look up relevant fixtures and tests to better understand scope and context
Check git blame/git log around the affected area for recent changes