first-tree-file-buglisted

File a GitHub issue about a defect in First Tree itself — the CLI, agent runtime, chat, web app, GitHub integration, GitLab integration, or Context Tree tooling — onto First Tree's own GitHub-hosted public tracker (agent-team-foundation/first-tree). Use only when the user reports that First Tree the platform is broken, errored, crashed, or misbehaving and wants it reported (e.g. "First Tree has a bug", "chat send keeps failing", "the CLI crashed", "给 First Tree 开个 issue 反馈这个 bug"). The skill gathers reproduction steps, the First Tree client/CLI version, the chat ID, the reporting user's ID, OS, and error output, then opens the issue with the user's `gh` CLI. NOT for filing an issue into the user's own or bound source repo — that is an ordinary source-repo issue using the target forge CLI (`gh` for GitHub, `glab` for GitLab), not this skill — and not for bugs in the user's project code or third-party tools.
agent-team-foundation/first-tree · ★ 139 · Data & Documents · score 79

Install: claude install-skill agent-team-foundation/first-tree

# 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