You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
-**Schema metadata:**`ProblemSchemaEntry` must reflect the current registry schema shape, including `display_name`, `aliases`, `dimensions`, and constructor-facing `fields`
110
121
-**Optimization problems:**`type Metric = SolutionSize<W::Sum>`, implement `OptimizationProblem` with `direction()`
@@ -280,3 +290,5 @@ Run /review-pipeline to process Copilot comments, fix CI, and run agentic tests.
280
290
| Dirty working tree | Use `pipeline_worktree.py prepare-issue-branch` — it stops before branching if the worktree is dirty |
281
291
| Bundling model + rule in one PR | Each PR must contain exactly one model or one rule — STOP and block if model is missing (Step 3.5) |
282
292
| Plan files left in PR | Delete plan files before final push (Step 7c) |
293
+
|`make paper` or export steps changed tracked JSON after verification | Run `git status --short`, stage expected generated exports, and STOP if unexpected files remain before push |
294
+
|`make copilot-review` cannot find a resumed PR branch | Request review with `gh copilot-review "$PR"` so resumed local branch names do not matter |
-`action == "resume-pr"`: existing PR checked out — `issue-to-pr` will skip plan creation and jump to execution
160
+
- If the resumed branch later proves stale against `main` (for example, merge conflicts span registry/CLI/skill wiring or a merge helper reports `likely_complex: true`), STOP autonomous repair and move the issue to `Final review` for human triage instead of forcing a large migration inside project-pipeline
151
161
-`action == "create-worktree"`: fresh branch from `origin/main`
152
162
153
163
All subsequent steps run inside the worktree. This ensures the user's main checkout is never modified.
@@ -246,3 +256,4 @@ Completed: 2/4 | Review pool: 3 | Returned to Ready: 1
246
256
| Working in main checkout | All work happens in `.worktrees/` — never modify the main checkout |
247
257
| Missing items from project board |`gh project item-list` defaults to 30 items — always use `--limit 500`|
248
258
| Creating a fresh branch when PR exists | Check `issue-context` action field first — use `checkout-pr` for existing PRs instead of `create-issue`|
259
+
| Forcing a very stale resume PR through autonomous conflict repair | If a resumed PR has broad merge conflicts (`likely_complex: true`, registry/CLI/skill churn, etc.), stop and move it to `Final review`|
Copy file name to clipboardExpand all lines: .claude/skills/review-pipeline/SKILL.md
+11-5Lines changed: 11 additions & 5 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -99,6 +99,7 @@ The report is the Step 0 packet. It should already include:
99
99
- Comment Summary
100
100
- CI / Coverage
101
101
- Merge Prep
102
+
- PR head branch
102
103
- Linked Issue Context
103
104
104
105
Branch from the report:
@@ -118,7 +119,7 @@ The bundle already handled the mechanical claim step:
118
119
- the selected reviewed PR is claimed through the review queue
119
120
- explicit `--pr` matches on ambiguous cards are treated as deterministic disambiguation and claimed automatically
120
121
121
-
When you need to take actions later, use the identifiers already printed in the report (`Board item`, `PR`, worktree path). If you need structured data, prefer parsing the existing packet or ensure Step 0 was generated as JSON once; do not rerun Step 0 just to switch formats inside the same invocation.
122
+
When you need to take actions later, use the identifiers already printed in the report (`Board item`, `PR`, worktree path, `PR head branch`). If you need structured data, prefer parsing the existing packet or ensure Step 0 was generated as JSON once; do not rerun Step 0 just to switch formats inside the same invocation.
122
123
123
124
All subsequent steps run inside the prepared worktree and should read facts from the report instead of re-fetching them by default.
124
125
@@ -132,7 +133,7 @@ All subsequent steps run inside the prepared worktree and should read facts from
132
133
133
134
Read the merge result from the report's `Merge Prep` section.
134
135
135
-
- If the report says the merge status is `clean`: push the merge commit and continue.
136
+
- If the report says the merge status is `clean`: push the merge commit to the packet's `PR head branch`and continue.
136
137
- If there are conflicts:
137
138
1. Inspect the conflicting files listed in the report.
138
139
2. Compare the current skill versions on main vs the PR branch to understand which patterns are current.
@@ -146,11 +147,13 @@ Use the report as the primary mechanical context:
146
147
-`Comment Summary`
147
148
-`CI / Coverage`
148
149
-`Linked Issue Context`
150
+
-`Merge Prep` (`PR head branch`)
149
151
150
152
Inspect the report's Copilot comment count and linked issue context. If there are actionable comments: invoke `/fix-pr` to address them, then push:
151
153
152
154
```bash
153
-
git push
155
+
HEAD_REF_NAME=<from the review-pipeline packet>
156
+
git push origin HEAD:"$HEAD_REF_NAME"
154
157
```
155
158
156
159
If Copilot approved with no actionable comments: skip to next step.
@@ -196,7 +199,9 @@ Run agentic feature tests on the modified feature:
196
199
-`[Model]` PRs: the new problem model name
197
200
-`[Rule]` PRs: the new reduction rule (source -> target)
198
201
199
-
2.**Invoke `/agentic-tests:test-feature`** with the identified feature. This simulates a downstream user exercising the feature from docs and examples. You MUST use the Skill tool to invoke `agentic-tests:test-feature`.
202
+
2.**Invoke `/agentic-tests:test-feature`** with the identified feature. This simulates a downstream user exercising the feature from docs and examples.
203
+
- In environments with a Skill tool, use that tool.
204
+
- In Codex, open `~/.claude/commands/agentic-tests:test-feature.md` directly and follow it instead of assuming slash-command support.
200
205
201
206
3.**If test-feature reports issues:** treat every reported issue as real until you have checked it in the **current PR worktree/branch**.
202
207
- Reproduce each issue from the current PR branch/worktree before acting. If it does not reproduce there, classify it as `not reproducible in current worktree`.
0 commit comments