How do I install the Bug Report skill?

Run npx skillmds@latest add rivie13-phoenix-agentic-engine-interface/bug-report in your terminal (requires Node.js), paste this page's agent-chat prompt into Claude, Cursor, or any MCP-connected agent, or download the SKILL.md file and copy it into your agent's skills directory.

Is Bug Report safe to use?

This skill has not completed SkillMD's automated safety review yet. Independent scanners report: SkillSpector: PASS, Skill Scanner: PASS. Capability flags: makes network calls. SkillMD never runs a skill's scripts for you; review the SKILL.md before installing.

Which AI agents work with Bug Report?

This skill is tagged as working with Claude Code, Claude.ai, OpenAI Codex. SKILL.md is an open format, so most agents that read a skills directory can load it too.

Is Bug Report free to use?

Yes. Installing skills from SkillMD is free, and the skill stays under its author's original license.

Who published Bug Report?

rivie13 (@rivie13-phoenix-agentic-engine-interface) published this skill. Their other Agent Skills are listed on their SkillMD profile.

Bug Report by rivie13-phoenix-agentic-engine-interface

Name: Bug Report
Rating: 4.2 (5 reviews)
Author: rivie13

Bug Report

Investigate a bug and create a high-quality GitHub bug issue with reproducible steps and code-level findings. Use when user asks to report a bug, file an issue, document a regression, or write an investigation-backed bug report.

rivie13 Updated Sep 10, 2026

File contents

Bug report — Phoenix Agentic Engine Interface

Mandatory first step

Check the project board for active in-progress work so bug reports are correctly framed as primary work or a new discovery:

Project board: https://github.com/users/rivie13/projects/3
Check this repo's in-progress issues to understand current context.

Workflow

Clarify bug scope
- Capture expected behavior, actual behavior, and impact.
- If context is missing, ask only the minimum needed to make the report actionable.
Gather investigation evidence
- Inspect relevant code paths, logs, and contracts.
- Capture suspected root-cause area and what was ruled out.
- Prefer concrete file/function references.

Check for duplicates

Use GitHub MCP issue search before creating a new issue:

mcp_github_github_search_issues(owner="rivie13", repo="Phoenix-Agentic-Engine-Interface", query="<keywords>")

Create the issue with the bug template structure
- Use mcp_github_github_issue_write (method="create").
- Add bug label.
- Include: summary, environment, repro steps, expected vs actual, evidence, investigation notes, and acceptance criteria.
Set project fields via signal labels (when available)
- Add labels such as set:priority:p1, set:size:m, set:workmode:local-ide.
- If the task should be cloud-run, move it to Ready and add cloud-agent.

Required issue quality bar

Reproduction is deterministic (or clearly states flakiness conditions).
Investigation contains at least one concrete lead (not just symptoms).
Fix acceptance criteria are testable and specific.
Scope is one bug per issue.

Related repos

Engine: rivie13/Phoenix-Agentic-Engine
Backend: rivie13/Phoenix-Agentic-Engine-Backend

Use cross-repo links in the issue body when the bug spans boundaries.

---name: bug-reportdescription: Investigate a bug and create a high-quality GitHub bug issue with reproducible steps and code-level findings. Use when user asks to report a bug, file an issue, document a regression, or write an investigation-backed bug report.---# Bug report — Phoenix Agentic Engine Interface## Mandatory first stepCheck the project board for active in-progress work so bug reports are correctly framed as primary work or a new discovery:- Project board: https://github.com/users/rivie13/projects/3- Check this repo's in-progress issues to understand current context.## Workflow1. Clarify bug scope - Capture expected behavior, actual behavior, and impact. - If context is missing, ask only the minimum needed to make the report actionable.2. Gather investigation evidence - Inspect relevant code paths, logs, and contracts. - Capture suspected root-cause area and what was ruled out. - Prefer concrete file/function references.3. Check for duplicates - Use GitHub MCP issue search before creating a new issue: ``` mcp_github_github_search_issues(owner="rivie13", repo="Phoenix-Agentic-Engine-Interface", query="<keywords>") ```4. Create the issue with the bug template structure - Use `mcp_github_github_issue_write` (`method="create"`). - Add `bug` label. - Include: summary, environment, repro steps, expected vs actual, evidence, investigation notes, and acceptance criteria.5. Set project fields via signal labels (when available) - Add labels such as `set:priority:p1`, `set:size:m`, `set:workmode:local-ide`. - If the task should be cloud-run, move it to Ready and add `cloud-agent`.## Required issue quality bar- Reproduction is deterministic (or clearly states flakiness conditions).- Investigation contains at least one concrete lead (not just symptoms).- Fix acceptance criteria are testable and specific.- Scope is one bug per issue.## Related repos- Engine: `rivie13/Phoenix-Agentic-Engine`- Backend: `rivie13/Phoenix-Agentic-Engine-Backend`Use cross-repo links in the issue body when the bug spans boundaries.

Frequently asked questions