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

- Skill: `rivie13/bug-report` (Agent Skill)
- Install (CLI): `npx skillmds@latest add rivie13/bug-report`
- Raw SKILL.md: https://api.skillmd.com/api/skills/rivie13/bug-report/raw
- Safety review: pending (external: skill-scanner PASS, skillspector PASS)
- Works with: Claude Code, Claude.ai, OpenAI Codex
- Category: Docs & Writing
- Author: rivie13 (https://skillmd.com/u/rivie13)
- Updated: 2026-09-10
- Page: https://skillmd.com/skills/rivie13/bug-report

---


# Bug report — Phoenix Agentic Website Frontend

## 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

1. 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-Website-Frontend", 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

- Website Backend: `rivie13/Phoenix-Agentic-Website-Backend`

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