address-issue
规范化维护者工作流，提升响应速度与透明度。
对 GitHub issue 进行端到端处置，从响应到复现、估算、修复并通知报告者。
把 GitHub 上的 bug 从收到到上线全流程处理：先回复标注“Investigating”，再复现、估算大小、按估算修复并开 PR，合并与发布时通知报告者。接手 issue 或被请修 bug 时用。特点是把维护者的礼仪和自动闭环固化（自动关联并关 issue、标准回复），多数是小改动不用大调研。
▸ 展开 SKILL.md 英文原文
End-to-end playbook for working a GitHub issue (or bug-fix PR) on nubjs/nub: triage → acknowledge an external report with an "Investigating" comment → reproduce it yourself → SIZE it → fix it at that size (most issues are a small fix you just write — no investigation spike, no sub-agent fleet, no top-tier model) → open a PR that references the issue with `Closes #N` → on merge, comment the resolution → on release, comment the version + release link. Invoke (via the Skill tool) whenever you pick up an issue to work, or are asked to fix a reported bug. Encodes both the maintainer-hygiene conventions in AGENTS.md (so the reporter is acknowledged, the issue auto-closes on merge, and the loop closes when the fix ships) and the proportionality gate that keeps an ordinary bug from being worked like an audit.
帮我安装这个 skill：https://raw.githubusercontent.com/nubjs/nub/main/.claude/skills/address-issue/SKILL.mdcurl -fsSL "https://raw.githubusercontent.com/nubjs/nub/main/.claude/skills/address-issue/SKILL.md"# Addressing a nub issue end-to-end Taking a GitHub issue from "reported" to "shipped and the reporter told." The hygiene rules here are mandatory, not courtesies — maintainer responsiveness on a public repo is a visible health signal. ## Guardrails - **Tone is factual, neutral, professional** — never braggy, competitive, or over-promising. See [`PROSE.md`](../../../PROSE.md). - **A fix lands via the PR-from-a-worktree flow**, not directly on the shared `main` tree. Trivial doc/typo fixes are the documented exception. - **Verify end-to-end before pushing** — run the pre-push local-verification loop. A green suite with a stubbed fix is worse than an unchecked one. - **Don't autonomously la