repo tasks: authoring replay tasks from merged PRs
メンテナーはふだん 1 日以内に返信
まだ誰も着手していません。
評価
- 難易度
- 5/5
- 見積もり時間
- 1週間以上
- 初心者へのやさしさ
- 42/100
- issue の種類
- 機能追加
- 明瞭さ
- おおむね明確
- 活発さ
- 活発
- 技術スタック
- python
調査の方向性
Start by reading the existing repo tasks replay implementation and the task contract’s section 3 to see how review replay builds tasks and how feature or fix tasks are graded. Then inspect the manifest handling and repo tasks check path, along with the network-free fixture tests. Done means authoring tasks from merged PRs are accepted by repo tasks check, with the untouched base failing and the PR diff passing as the oracle.
索引モデルが issue の本文から書いたものです。
説明
Problem
repo tasks replay builds dokimi:review_replay tasks, which measure what guidance does to an agent reviewing code. Most guidance is read while writing code. Of the eight AGENTS.md files in IntelPython/dpnp#3099, most lines say where a new function's kernel and dispatch helpers go, how tests are laid out, and what a changelog entry looks like. The review replay of that PR exercised little of it.
dokimi can already grade such work. A task.json with family: feature or fix and the repository's own grade entry point does it (contract §3). But those tasks are written by hand, so this measurement is skipped too, just as review counting was before repo tasks replay.
Proposal
Build authoring tasks from merged PRs, with the same input and the same rules for what to leave out as review replay: repo tasks replay --kind authoring, or a sibling subcommand. Per merged PR:
- Base: the merge base of the PR with
mergeCommit^1, as for review replay. - Prompt: the PR's title and description, with links to its commits and diff and anything quoting the change removed.
--prompt-filereplaces the default. - Hidden tests: the test files the PR added or changed. They are held out of the workspace and applied only at grade time.
- Grade: the repository's test command from the manifest, on the hidden tests; the gate is that they pass.
oracleis the PR's own diff, sorepo tasks checkcan show that the base fails and the oracle passes. - Left out: guidance files and
eval_dir, as review replay leaves them out.
Open questions
- Which PRs qualify: with tests, under a size limit, not only refactors.
- Leaked tests: a description that names the test functions.
- Build cost: dpnp needs its SYCL extensions built for every cell. How much can the manifest's caches and a prebuilt base image save?
- Partial credit: some hidden tests passing. Should it count, as a score rather than a gate?
- Flaky tests: run the oracle twice in
tasks check?
Done when
On a window of merged PRs of a real repository, the command writes tasks that repo tasks check accepts (the untouched base fails, the oracle passes). The tests use a fixture repository with no network.
- 主要言語
- Python
- スター
- 9
- フォーク
- 9
- 平均マージ
- 1日 8時間
- マージ済み PR（30日）
- 267
環境構築
- Dockerfile・Docker Compose ファイルなし
- プルリクエストのテンプレートあり
- コントリビューションガイドを読む
はじめの一歩
- issue を最後まで読み、次にプロジェクトのコントリビューションガイドを読みます。
- 着手することを issue にコメントします — 二人が同じ作業をするのを防げます。
- リポジトリをフォークし、ブランチを切って変更します。
- issue 番号を参照したプルリクエストを送ります。
intel/dokimi のほかの issue
-
難易度 4/5 3〜5日 初心者へのやさしさ 45/100
メンテナーはふだん 1 日以内に返信
-
難易度 3/5 1〜2日 初心者へのやさしさ 65/100
メンテナーはふだん 1 日以内に返信
-
難易度 3/5 1〜2日 初心者へのやさしさ 70/100
メンテナーはふだん 1 日以内に返信
-
難易度 3/5 1〜2日 初心者へのやさしさ 65/100
メンテナーはふだん 1 日以内に返信
-
難易度 5/5 1週間以上 初心者へのやさしさ 35/100
メンテナーはふだん 1 日以内に返信
似ている issue
-
Status: Triage Type: Quest
難易度 2/5 1〜3時間 初心者へのやさしさ 66/100
GTNewHorizons/GT-New-Horizons-Modpack#27490 ·
メンテナーはふだん 1 日以内に返信
-
Bug
難易度 2/5 1〜3時間 初心者へのやさしさ 72/100
メンテナーはふだん 1 日以内に返信
-
bug
難易度 2/5 1〜3時間 初心者へのやさしさ 82/100
retentioneering/retentioneering-tools#231 ·
メンテナーはふだん 1 日以内に返信
-
backend bug documentation
難易度 2/5 1〜3時間 初心者へのやさしさ 78/100
geolens-io/geolens#3568 ·
メンテナーはふだん 1 日以内に返信
-
enhancement
難易度 1/5 1時間未満 初心者へのやさしさ 88/100
mprov-ng/mprov_control_center#450 ·
メンテナーはふだん 1 日以内に返信