New skill: issue_prioritization_workflow, prioritize issues with a coding agent and GitHub Projects or GitLab

未关闭
  • 哪里不对？
#4 1 条评论 0 个 reaction 已指派 0 人 在 GitHub 查看

维护者通常 1 天内回复

还没有人认领这个 Issue。

评估

难度
5/5
预计耗时
一周以上
新手友好度
35/100
Issue 类型
功能
描述清晰度
基本清楚
活跃度
活跃
技术栈
github, gitlab
领域
devtools

调研方向

Read the first comment for the full process summarized by the issue, then inspect the existing bug_triage_workflow skill to understand the project’s skill conventions. Define how the skill handles the listed open questions about GitHub Projects, GitLab, objectives, scoring, and queue size; done means a SKILL.md for issue_prioritization_workflow that proposes priorities and a ranked Ready queue for approval before updating a board.

由索引模型根据 Issue 内容生成。

描述

Goal

Create a new skill, with its instructions in SKILL.md, that lets a coding agent prioritize the open issues of a repository and keep that priority order in the project board of the issue tracker.

  • The coding agent estimates the impact, the urgency, and the effort of each open issue, and finds the dependencies and the blockers between issues.
  • The coding agent proposes a priority level (P0, P1, P2, P3) and an explicitly ranked Ready queue, and explains each choice in one or two sentences.
  • The developer approves the proposed priorities and the proposed ranking before the coding agent changes any issue or any project board.
  • The coding agent writes the approved priorities and the approved ranking to GitHub Projects, or to the equivalent feature in GitLab.
  • The developer can run the skill again whenever the objectives change, or once a week, to keep the priority order current.

The full process is summarized in the first comment of this issue.

Proposed name

issue_prioritization_workflow

Proposed description

Prioritize the open issues of a repository and keep a ranked Ready queue in GitHub Projects or in the equivalent feature in GitLab. Use when the developer asks which issue to work on next, asks to assign priorities, or asks to update the project board. Propose every priority and every ranking first, and change issues or project boards only after the developer approves.

Open questions

  1. Which GitLab feature is the equivalent of GitHub Projects: issue boards with scoped labels (for example priority::1), the issue weight field for the effort, or epics? Do these features need a paid GitLab tier?
  2. Where does the skill store the priority level and the effort in a personal GitHub repository: in custom fields of GitHub Projects, or in labels? Does the native Priority field and the native Effort field of GitHub issues apply only to organization repositories?
  3. How does the skill store the explicit ranking of the Ready queue: the item order of a GitHub Projects view, a number field, or a pinned issue that lists the queue?
  4. Does the skill use the gh command line and the glab command line, or a Model Context Protocol server for GitHub and for GitLab?
  5. How does the skill learn the current objectives of the project: from the developer in the conversation, from a file in the repository, or from a milestone?
  6. Does the skill keep the formula Score = (Impact × Urgency) / Effort, or only use the three estimates as input for the judgment of the coding agent?
  7. How does this skill relate to the existing bug_triage_workflow skill: does the new skill replace it, call it, or stay separate and cover all issue types?
  8. What is the maximum size of the Ready queue: ten issues, as the source suggests, or a number that the developer chooses?

Source

https://chatgpt.com/c/6ad9d01f-a480-83ed-bef3-e98d23ac1e04

主要语言
没有语言数据
星标
1
派生
0
平均合并
7 分钟
30 天内合并 PR
17

环境准备

这个项目没有提供开发容器、Dockerfile 或贡献指南，环境需要你自己搭建：先看它的 README，通用步骤见我们的新手贡献指南。

从这里开始

  1. 先读完整个 Issue，再读项目的贡献指南。
  2. 在 Issue 下留言说明你要接手 —— 这能避免两个人做同样的事。
  3. Fork 仓库，在一个分支上完成修改。
  4. 提交 Pull Request，并在描述里引用这个 Issue 编号。

jeromeetienne/coding_agent_plugin 的其他 Issue

查看 jeromeetienne/coding_agent_plugin 的全部 Issue

相似的 Issue

更多 DevTools Issue

把新 issue 发到你的邮箱

精选适合新手参与的 GitHub issue 摘要。