first-tree-file-bug

# First Tree File Bug ## Purpose Turn a user's informal bug report about **First Tree itself** into a well-formed GitHub issue on `agent-team-foundation/first-tree`, filed with the user's authenticated `gh` CLI. The value is that the user only has to say "First Tree has a bug" — this skill does the collection, drafting, and filing, opens a dedicated chat that follows the issue for tracking, and reports the issue URL back. The target repo is **public**. Filing publishes whatever you include, so gather deliberately, confirm with the user before creating, and never post secrets (see **Guardrails**). ## When to use - The defect is in **First Tree** — the CLI (`first-tree …`), the agent runtime / client, chat delivery, the web app, notifications, GitHub integration, GitLab integration, or Context Tree tooling. - The user wants it **reported / filed / logged**, not just diagnosed. ## When NOT to use - The bug is in the **user's own project code**, a dependency, or a third-party tool — that is normal debugging, not a First Tree issue. - The user only wants help understanding or working around the problem and has not asked to file anything. Fix or explain first; offer to file only if it is a genuine First Tree defect. - It is a **security vulnerability** — do not open a public issue; point the user to the repo's `SECURITY.md` reporting path instead. ## Workflow ### 1. Confirm the scope State briefly what you understand the bug to be and that it looks like a Firs...