[Backlog Discovery] feat(backlog): backlog-pr-issue-auto-labeling

[bestony]

[Backlog Discovery]

• Requirement title: 为自驱生成的 Issue/PR 增加自动标签与优先级同步
• Priority: P2
• Requirement file: backlog/20260221055525-backlog-pr-issue-auto-labeling.md
• Dedupe key: backlog-pr-issue-auto-labeling
• Source run: https://github.com/bestony/self/actions/runs/22251460467

---

[Backlog Discovery]

Update Record 2026-02-21 13:58:10 +08:00

Update summary:

• Added a minimum viable label set (priority + type) and required defining the default label sync strategy before expanding.

• Added a pre-launch baseline measurement requirement using repository evidence (e.g., triage time or misclassification rate).

• Refined acceptance criteria to include default sync policy, workflow overrides, and baseline metrics alongside automated labeling behaviors.

• Status: committed

• Commit: 2d94730ab3a4bfd73914414ef2c268f0a602b00d

• Trigger: workflow_run.completed

• Comment: https://github.com/bestony/self/actions/runs/22251519641

• Actor: @github-actions[bot]

• Updated At (Asia/Shanghai): 2026-02-21 13:58:10 +08:00

[gemini-code-assist]

Summary of Changes

Hello @bestony, I'm Gemini Code Assist¹! I'm currently reviewing this pull request and will post my feedback shortly. In the meantime, here's a summary to help you and other reviewers quickly get up to speed!

此拉取请求引入了一个新的需求文档，旨在解决自动化流程（如 Backlog Discovery 和 Product Designer）在 GitHub 上创建 Issue 和 Pull Request 时缺乏统一标签和优先级同步机制的问题。通过定义和实施自动标签规范，该变更将显著提升仓库维护者识别、分类和管理这些工作项的效率，从而优化需求评审和执行排期流程。

Highlights

• 新需求文档: 引入了一个新的需求文档，详细说明了为自动生成的 Issue/PR 增加自动标签和优先级同步的必要性。
• 自动化标签与优先级: 旨在解决 Backlog Discovery 和 Product Designer 等流程自动创建的 Issue/PR 缺乏统一标签和优先级映射机制的问题。
• 提升效率: 通过自动化标签，提高仓库维护者筛选高优先级项和按类型分流的效率，减少人工成本。

Changelog

• backlog/20260221055525-backlog-pr-issue-auto-labeling.md
  • 新增了关于为自驱生成的 Issue/PR 增加自动标签与优先级同步的需求文档。

Activity

• 此拉取请求自创建以来，尚未有评论或评审活动。

Using Gemini Code Assist

The full guide for Gemini Code Assist can be found on our documentation page, here are some quick tips.

Invoking Gemini

You can request assistance from Gemini at any point by creating a comment using either /gemini <command> or @gemini-code-assist <command>. Below is a summary of the supported commands on the current page.

Feature	Command	Description
Code Review	/gemini review	Performs a code review for the current pull request in its current state.
Pull Request Summary	/gemini summary	Provides a summary of the current pull request in its current state.
Comment	@gemini-code-assist	Responds in comments when explicitly tagged, both in pull request comments and review comments.
Help	/gemini help	Displays a list of available commands.

Customization

To customize Gemini Code Assist for GitHub experience, repository maintainers can create a configuration file and/or provide a custom code review style guide (such as PEP-8 for Python) by creating and adding files to a .gemini/ folder in the base of the repository. Detailed instructions can be found here.

Limitations & Feedback

Gemini Code Assist may make mistakes. Please leave feedback on any instances where its feedback is incorrect or counter productive. You can react with 👍 and 👎 on @gemini-code-assist comments. If you're interested in giving your feedback about your experience with Gemini Code Assist for Github and other Google products, sign up here.

You can also get AI-powered code generation, chat, as well as code reviews directly in the IDE at no cost with the Gemini Code Assist IDE Extension.

Footnotes

1. Review the Privacy Notices, Generative AI Prohibited Use Policy, Terms of Service, and learn how to configure Gemini Code Assist in GitHub here. Gemini can make mistakes, so double check it and use code with caution. ↩

[github-actions]

[Reviewer Workflow]
Reviewer: Product Manager

需求价值评估

• 是否有价值: 有价值
• 优先级: P2
• Reviewer 视角结论: 该需求能提升自驱产出事项的可见性与分流效率，但需补充仓库内数据来验证真实收益。

价值点

• 统一 priority/type 标签后，维护者可在 PR/Issue 列表与 Projects 中快速筛选高优先级项。
• 减少自驱与人工事项混杂带来的分流成本，提升评审与排期效率。
• 自动同步优先级与来源类型，降低人工标注遗漏的运营风险。

风险与建议

• 证据主要来自通用文档与工具说明，缺少仓库内现状数据；建议先补充分流耗时/误判率基线。
• 标签体系与开关策略未明确定义边界；建议先收敛最小标签集并明确默认策略再扩展。

[gemini-code-assist]

Code Review

The pull request introduces a new backlog document for automatic labeling and priority synchronization of issues and PRs. The document is well-structured and clearly outlines the problem, proposed solution, and acceptance criteria. The changes are straightforward, adding a new markdown file to the backlog directory. No critical issues were found, but a minor improvement opportunity is noted regarding the duplication of the 'User Problems' section.

[gemini-code-assist]

The content of '4. User Problems' appears to be a direct duplicate of '1. Requirement Summary'. Consider if this section adds unique value or if it can be integrated into the summary to avoid redundancy.

[github-actions]

[Backlog Discovery]
Reviewer: Product Manager

• Acceptance criteria #1 only gives an example label set, not the exact minimal list and naming; this leaves mapping ambiguous and risks inconsistent tagging. Suggestion: specify the definitive priority/type label names and the mapping rules from workflow fields.
• Acceptance criteria #2 mentions a default on/off strategy but never states which default is required; this makes the behavior untestable. Suggestion: decide and document the default (enabled vs opt-in) per workflow and any override location.
• Acceptance criteria #5 requires a baseline metric but doesn’t define what metric, data source, or success threshold to record. Suggestion: name the exact baseline metric (e.g., median triage time), how it’s measured, and the required recording point before rollout.