refactor(todos): remove internal file-based todo system (#635)
Co-authored-by: Claude Opus 4.7 (1M context) <noreply@anthropic.com>
This commit is contained in:
@@ -19,12 +19,40 @@ CRITICAL: You MUST execute every step below IN ORDER. Do NOT skip any required s
|
||||
|
||||
4. `/ce-code-review mode:autofix plan:<plan-path-from-step-2>`
|
||||
|
||||
Pass the plan file path from step 2 so ce-code-review can verify requirements completeness.
|
||||
Pass the plan file path from step 2 so ce-code-review can verify requirements completeness. Read the Residual Actionable Work summary the skill emits.
|
||||
|
||||
5. `/ce-todo-resolve`
|
||||
5. **Persist review autofixes** (REQUIRED after step 4, before residual handoff)
|
||||
|
||||
6. `/ce-test-browser`
|
||||
Check `git status --short`. If `ce-code-review mode:autofix` changed files, stage only those review-fix files, commit them with `fix(review): apply autofix feedback`, and push the current branch before continuing. If an upstream exists, run `git push`. If no upstream exists, resolve a writable remote dynamically: prefer `origin` when present, otherwise use `git remote` and choose the first configured remote. Then run `git push --set-upstream <remote> HEAD`. Do not proceed to step 6, run browser tests, or output DONE while review autofix edits remain only in the working tree. If no files changed, explicitly note that there were no review autofixes to persist.
|
||||
|
||||
7. Output `<promise>DONE</promise>` when complete
|
||||
6. **Autonomous residual handoff** (only when step 4 reported one or more residual `downstream-resolver` findings; skip when it reported `Residual actionable work: none.`)
|
||||
|
||||
Do not prompt the user. This step embraces the autopilot contract: residuals must become durable before DONE, but the agent never stops to ask.
|
||||
|
||||
1. Load `references/tracker-defer.md` in **non-interactive mode**. Pass the residual actionable findings from step 4's summary (or the run artifact when the summary was truncated).
|
||||
2. Collect the structured return: `{ filed: [...], failed: [...], no_sink: [...] }`.
|
||||
3. Compose a `## Residual Review Findings` markdown section from the structured return:
|
||||
- For each item in `filed`: a bullet with severity, file:line, title, and a link to the tracker ticket URL.
|
||||
- For each item in `failed`: a bullet with severity, file:line, title, and the failure reason (e.g., `Defer failed: gh returned 401 — tracker unavailable`).
|
||||
- For each item in `no_sink`: a bullet with severity, file:line, and title inlined verbatim so the PR body or fallback file is the durable record.
|
||||
4. Detect the current branch's open PR without prompting:
|
||||
|
||||
```bash
|
||||
gh pr view --json number,url,body,state
|
||||
```
|
||||
|
||||
5. If an open PR exists, update it directly with `gh`; do not load any confirmation-driven PR update skill. Append or replace the `## Residual Review Findings` section in the current PR body, write the new body to an OS temp file, then run:
|
||||
|
||||
```bash
|
||||
gh pr edit PR_NUMBER --body-file BODY_FILE
|
||||
```
|
||||
|
||||
6. If no open PR exists, create a tracked fallback file at `docs/residual-review-findings/<branch-or-head-sha>.md` containing the composed section and the source PR-review run context. Stage only that file, commit it with `docs(review): record residual review findings`, and push the current branch. If an upstream exists, run `git push`. If no upstream exists, resolve a writable remote dynamically: prefer `origin` when present, otherwise use `git remote` and choose the first configured remote. Then run `git push --set-upstream <remote> HEAD`. This is the durable no-PR sink. Do not output DONE until either the existing PR body has been updated or this fallback file commit has been pushed. If both paths fail, stop and report the failed commands; do not silently proceed.
|
||||
|
||||
Never block DONE on tracker filing failures once residuals have been durably recorded. A `no_sink` outcome is success only when the findings are present in the PR body or in the pushed fallback file.
|
||||
|
||||
7. `/ce-test-browser`
|
||||
|
||||
8. Output `<promise>DONE</promise>` when complete
|
||||
|
||||
Start with step 2 now (or step 1 if ralph-loop is available). Remember: plan FIRST, then work. Never skip the plan.
|
||||
|
||||
Reference in New Issue
Block a user