Agent skill

bug-triage

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.

View SKILL.md on GitHub Repository
Stars 123
Forks 12

Install this agent skill to your Project

npx add-skill https://github.com/jMerta/codex-skills/tree/main/bug-triage

SKILL.md

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

  1. Read any repo-specific guidance (AGENTS.md, CONTRIBUTING.md, README).
  2. 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)

  1. Reproduce locally
    • Prefer the simplest, fastest repro.
    • If it’s flaky, try to reduce nondeterminism (seed, fixed time, retries).
  2. Localize the failure
    • Narrow to a file/function/component/config.
    • Use rg to find relevant code paths and error strings.
  3. Identify root cause
    • Form a hypothesis, confirm with logs/breakpoints, then refine.
    • If it’s a regression and git history exists, consider git bisect.
  4. Implement the minimal fix
    • Fix the cause, not the symptom.
    • Avoid drive-by refactors and formatting churn.
  5. 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.

Recommended Agent Skills

Expand your agent's capabilities with these related and highly-rated skills.

jMerta/codex-skills

vps-checkup

SSH into an Ubuntu VPS (Docker) for a read-only health/security/update report (UFW + fail2ban) and propose fixes; apply updates/restarts only with explicit confirmation. Use when the user wants a read-only VPS health/security check.

123 12
Explore
jMerta/codex-skills

ci-fix

Fix GitHub Actions CI failures using GitHub CLI (gh): inspect runs/logs, identify root cause, patch workflows/code, rerun jobs, and summarize verification. Use when GitHub Actions CI is failing or needs diagnosis.

123 12
Explore
jMerta/codex-skills

dependency-upgrader

Upgrade dependencies for Java/Kotlin (Gradle/Maven) and TypeScript/Node projects with minimal risk: plan the bump, apply changes incrementally, run tests/builds, and document breaking changes. Use when the user asks to bump deps, update frameworks, or address CVEs.

123 12
Explore
jMerta/codex-skills

plan-work

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.

123 12
Explore
jMerta/codex-skills

coding-guidelines-gen

Generate nested AGENTS.md coding guidelines per module (monorepo-aware), detect languages/tooling, ask architecture preferences, and set up missing formatters/linters (Spotless for JVM). Use when the user wants module-scoped AGENTS.md coding guidelines or to set up missing formatters/linters.

123 12
Explore
jMerta/codex-skills

ui-ux-pro-max

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).

123 12
Explore

Didn't find tool you were looking for?

Be as detailed as possible for better results