一键在 Manus 中运行任何 Skill

bug-triage

星标131

分支14

更新时间2025年12月19日 14:25

Reproduce, isolate, and fix a bug (or failing build/test), then summarize root cause, fix, and verification steps. Use when the user reports a bug, regression, or failing build/test and wants a fix.

安装

用 Codex 或 Claude 帮你安装复制这段 Prompt，粘贴到 Codex、Claude 或其他助手里，让它检查 Skill 页面并帮你完成安装。

在 Manus 中运行

来源

jMerta

jMerta/codex-skills

打开 GitHub 仓库查看创作者相关仓库

下载

在 Manus 中运行

Bug triage

Goal

Turn an ambiguous bug report into:

a reliable repro (or a clear “cannot reproduce yet” with next info to collect)
a root-cause explanation
a minimal, reviewed fix
verification steps (commands + manual checks)

First checks

Read any repo-specific guidance (AGENTS.md, CONTRIBUTING.md, README).
Clarify impact: severity, who is affected, and whether it’s a regression.

If info is missing, ask for it

Exact steps to reproduce (starting state + inputs).
Expected vs actual behavior.
Error text / stack trace / logs (full, unedited if possible).
Environment: OS, runtime versions (Node/Bun), browser, commit hash/tag.
Frequency: always / sometimes / only certain data.
“Last known good” version or approximate date when it started.

Workflow (checklist)

Reproduce locally
- Prefer the simplest, fastest repro.
- If it’s flaky, try to reduce nondeterminism (seed, fixed time, retries).
Localize the failure
- Narrow to a file/function/component/config.
- Use rg to find relevant code paths and error strings.
Identify root cause
- Form a hypothesis, confirm with logs/breakpoints, then refine.
- If it’s a regression and git history exists, consider git bisect.
Implement the minimal fix
- Fix the cause, not the symptom.
- Avoid drive-by refactors and formatting churn.
Verify
- Run the project’s standard checks (lint/tests/build).
- Re-run the repro steps and confirm the fix.

Repo-aware command hints

Use what the repo actually uses:

If bun.lock exists: prefer bun ... (e.g. bun lint, bun build, bun dev).
Otherwise: use the project’s documented commands (npm, pnpm, yarn, etc.).
If bun.lock exists but bun is not available, tell the user and ask whether to install bun or use the repo’s alternative package manager.

Deliverable (paste this in the chat / PR / issue)

Use this format:

Summary: ...
Repro: ...
Root cause: ...
Fix: ...
Verification: ...
Risk/notes: ...

If you need a bug-report structure to ask the user for, use references/bug-report-template.md.

同仓库更多 Skills

同仓库

create-cli

jMerta/codex-skills

Design command-line interface parameters and UX: arguments, flags, subcommands, help text, output formats, error messages, exit codes, prompts, config/env precedence, and safe/dry-run behavior. Use when designing a CLI spec (before implementation) or refactoring an existing CLI's surface area for consistency, composability, and discoverability.

2026-02-06131

ui-ux-pro-max

jMerta/codex-skills

Use when designing, building, or refining frontend UI/UX: layouts, components, visual systems, typography, color, and UX patterns for websites, landing pages, dashboards, and product interfaces. Provides searchable styles, palettes, font pairings, charts, and stack best practices (React, Next.js, Vue, Svelte, SwiftUI, React Native, Flutter, Tailwind).

2026-01-03131

plan-work

jMerta/codex-skills

Plan work before coding: do repo research, analyze options/risks, and ask clarifying questions before proposing an implementation plan. Use when the user asks for a plan, design/approach, scope breakdown, or implementation steps.

2026-01-02131

commit-work

jMerta/codex-skills

Create high-quality git commits: review/stage intended changes, split into logical commits, and write clear commit messages (including Conventional Commits). Use when the user asks to commit, craft a commit message, stage changes, or split work into multiple commits.

2026-01-01131

video-transcript-downloader

jMerta/codex-skills

Download videos, audio, subtitles, and clean paragraph-style transcripts from YouTube and any other yt-dlp supported site. Use when asked to “download this video”, “save this clip”, “rip audio”, “get subtitles”, “get transcript”, or to troubleshoot yt-dlp/ffmpeg and formats/playlists.

2026-01-01131

sessions-to-blog

jMerta/codex-skills

Generate MDX blog posts or recaps from session logs in `sessions/articles`. Use when the user asks to turn daily session notes into publishable blog posts, define writing style or linking rules for those posts, or produce MDX drafts that follow the project's standards and file location.

2025-12-29131

name	bug-triage
description	Reproduce, isolate, and fix a bug (or failing build/test), then summarize root cause, fix, and verification steps. Use when the user reports a bug, regression, or failing build/test and wants a fix.

Bug triage

Goal

Turn an ambiguous bug report into:

a reliable repro (or a clear “cannot reproduce yet” with next info to collect)
a root-cause explanation
a minimal, reviewed fix
verification steps (commands + manual checks)

First checks

Read any repo-specific guidance (AGENTS.md, CONTRIBUTING.md, README).
Clarify impact: severity, who is affected, and whether it’s a regression.

If info is missing, ask for it

Exact steps to reproduce (starting state + inputs).
Expected vs actual behavior.
Error text / stack trace / logs (full, unedited if possible).
Environment: OS, runtime versions (Node/Bun), browser, commit hash/tag.
Frequency: always / sometimes / only certain data.
“Last known good” version or approximate date when it started.

Workflow (checklist)

Reproduce locally
- Prefer the simplest, fastest repro.
- If it’s flaky, try to reduce nondeterminism (seed, fixed time, retries).
Localize the failure
- Narrow to a file/function/component/config.
- Use rg to find relevant code paths and error strings.
Identify root cause
- Form a hypothesis, confirm with logs/breakpoints, then refine.
- If it’s a regression and git history exists, consider git bisect.
Implement the minimal fix
- Fix the cause, not the symptom.
- Avoid drive-by refactors and formatting churn.
Verify
- Run the project’s standard checks (lint/tests/build).
- Re-run the repro steps and confirm the fix.

Repo-aware command hints

Use what the repo actually uses:

If bun.lock exists: prefer bun ... (e.g. bun lint, bun build, bun dev).
Otherwise: use the project’s documented commands (npm, pnpm, yarn, etc.).
If bun.lock exists but bun is not available, tell the user and ask whether to install bun or use the repo’s alternative package manager.

Deliverable (paste this in the chat / PR / issue)

Use this format:

Summary: ...
Repro: ...
Root cause: ...
Fix: ...
Verification: ...
Risk/notes: ...

If you need a bug-report structure to ask the user for, use references/bug-report-template.md.