New skill: issue_prioritization_workflow, prioritize issues with a coding agent and GitHub Projects or GitLab
メンテナーはふだん 1 日以内に返信
まだ誰も着手していません。
評価
- 難易度
- 5/5
- 見積もり時間
- 1週間以上
- 初心者へのやさしさ
- 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
- 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? - 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?
- 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?
- Does the skill use the
ghcommand line and theglabcommand line, or a Model Context Protocol server for GitHub and for GitLab? - 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?
- 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? - How does this skill relate to the existing
bug_triage_workflowskill: does the new skill replace it, call it, or stay separate and cover all issue types? - What is the maximum size of the Ready queue: ten issues, as the source suggests, or a number that the developer chooses?
Source
- 主要言語
- 言語のデータがありません
- スター
- 1
- フォーク
- 0
- 平均マージ
- 10分
- マージ済み PR（30日）
- 11
環境構築
このプロジェクトには開発コンテナ、Dockerfile、コントリビューションガイドがありません。まず README を読み、一般的な手順ははじめてのコントリビューションガイドを参照してください。
はじめの一歩
- issue を最後まで読み、次にプロジェクトのコントリビューションガイドを読みます。
- 着手することを issue にコメントします — 二人が同じ作業をするのを防げます。
- リポジトリをフォークし、ブランチを切って変更します。
- issue 番号を参照したプルリクエストを送ります。
jeromeetienne/coding_agent_plugin のほかの issue
-
難易度 2/5 1〜3時間 初心者へのやさしさ 72/100
jeromeetienne/coding_agent_plugin#29 ·
メンテナーはふだん 1 日以内に返信
-
難易度 2/5 1〜3時間 初心者へのやさしさ 64/100
jeromeetienne/coding_agent_plugin#7 ·
メンテナーはふだん 1 日以内に返信
-
難易度 3/5 半日 初心者へのやさしさ 68/100
jeromeetienne/coding_agent_plugin#26 ·
メンテナーはふだん 1 日以内に返信
-
難易度 3/5 1〜2日 初心者へのやさしさ 35/100
jeromeetienne/coding_agent_plugin#25 ·
メンテナーはふだん 1 日以内に返信
-
難易度 5/5 1週間以上 初心者へのやさしさ 35/100
jeromeetienne/coding_agent_plugin#19 · コメント 3 件 ·
メンテナーはふだん 1 日以内に返信
jeromeetienne/coding_agent_plugin の issue をすべて見る
似ている issue
-
難易度 2/5 1〜3時間 初心者へのやさしさ 85/100
メンテナーはふだん 1 日以内に返信
-
bug documentation
難易度 2/5 1〜3時間 初心者へのやさしさ 83/100
cqframework/vscode-cql#198 ·
-
bug documentation good first issue help wanted testing
難易度 2/5 1〜3時間 初心者へのやさしさ 84/100
メンテナーはふだん 1 日以内に返信
-
Show evidence time and supersede warnings in the memory inspector対応中かも @Sinchanak-212 が今日担当しました。 オープンarea: ux good first issue priority: medium
難易度 2/5 1〜3時間 初心者へのやさしさ 84/100
-
bug
難易度 2/5 1〜3時間 初心者へのやさしさ 78/100
rohit746/pdf-view.nvim#109 ·
メンテナーはふだん 1 日以内に返信