Repository navigation
feat: personalize marius-mode - #6
Conversation
Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
Codex Review SummaryThis comment shows the latest Codex review activity on this pull request.
ℹ️ About Codex in GitHubYour team has set up Codex to review pull requests in this repo. Reviews are triggered when you
Codex reacts with 👀 while any review is running, comments if it has suggestions, and reacts with 👍 once all reviews finish with no findings. |
![chatgpt-codex-connector[bot]](https://avatars.githubusercontent.com/in/1144995?s=60&v=4){kind=small}
There was a problem hiding this comment.
💡 Codex Review
Here are some automated review suggestions for this pull request.
Reviewed commit: 3b2c1e45d9
ℹ️ About Codex in GitHub
Your team has set up Codex to review pull requests in this repo. Reviews are triggered when you
- Open a pull request for review
- Mark a draft as ready
- Comment "@codex review".
If Codex has suggestions, it will comment; otherwise it will react with 👍.
Codex can also answer questions or update the PR. Try commenting "@codex address that feedback".
| 1. **Run the owner loop unchanged.** Resolve the forge once for the program. GitHub CLI (`gh`) is the default. If `command -v origin` succeeds and Origin can resolve the repository, use `origin pr ...` for PR create, edit, view, watch, and merge operations. Otherwise stay on `gh` and record the fallback. Never require Graphite (`gt`). One subagent per PR (a remote or cloud agent if the harness offers one) owns its change end to end: build, first push, a ready PR opened before self-proof, self-proof (gates, CI, receipts), skeptical Bugbot triage per `../references/bugbot-triage.md`, a slop-strip (reread the diff against the **laziness-protocol** principle skill and delete what does not earn its place), `/no-comments` (the **no-comments** skill), and babysit to green per `playbooks/babysit.md`. Owners parallelize when the work is self-contained. Within about 15 minutes, every owner starts a `decisions.tsv` trail per the **show-me-your-work** skill, pushes its first branch snapshot, and opens the PR ready, never draft. Keep the trail uncommitted and return it in the report. Owners also keep the `children.tsv` of Autopilot-full step 2. | ||
| 2. **Audit on the wake chain.** The root runs an audit tick roughly every 30 minutes. A local root arms each tick as a real recurring loop (Claude Code: `/loop`). The loop uses a monitored-shell 30-minute sleep and emits an output-notification sentinel. A cloud root uses the existing cloud-sleeper wake chain instead. Never leave the cadence to memory or lossy completion notifications. At each tick, re-read this playbook file in full, then re-read the armed `/goal`. Audit the operation against both. Fix drift during that tick. Probe each owner with a generic liveness or status check. Count only side effects as progress: commits, pushes, PR or check deltas, and store reports. Treat a lane that passes its expected runtime without a side effect as stuck. Stand it down and dispatch a replacement at once. Do not wait for a polite return. Probe all subagents and end the tick per Autopilot-full step 6. | ||
| 1. **Run the owner loop.** Resolve the forge once for the program. GitHub CLI (`gh`) is the default. If `command -v origin` succeeds and Origin can resolve the repository, use `origin pr ...` for PR create, edit, view, watch, and merge operations. Otherwise stay on `gh` and record the fallback. Never require Graphite (`gt`). One subagent per PR (a remote or cloud agent if the harness offers one) owns its change end to end: build, first push, a ready PR opened before self-proof, self-proof (gates, CI, receipts), skeptical Bugbot triage per `../references/bugbot-triage.md`, a slop-strip (reread the diff against the **laziness-protocol** principle skill and delete what does not earn its place), `/no-comments` (the **no-comments** skill), and babysit to green per `playbooks/babysit.md`. Owners parallelize when the work is self-contained. Within about 15 minutes, every owner starts a `decisions.tsv` trail per the **show-me-your-work** skill, pushes its first branch snapshot, and opens the PR ready, never draft. Keep the trail uncommitted and return it in the report. As soon as a subagent starts, the owner adds its ID, expected runtime (at least the longest past run of that kind), and state to a `children.tsv` kept uncommitted like the trail. | ||
| 2. **Audit on the wake chain.** The root runs an audit tick roughly every 30 minutes. A local root arms each tick as a real recurring loop (Claude Code: `/loop`). The loop uses a monitored-shell 30-minute sleep and emits an output-notification sentinel. A cloud root uses the existing cloud-sleeper wake chain instead. Never leave the cadence to memory or lossy completion notifications. At each tick, re-read this playbook file in full, then re-read the armed `/goal`. Audit the operation against both. Fix drift during that tick. Probe each owner with a generic liveness or status check. Count only side effects as progress: commits, pushes, PR or check deltas, and store reports. Treat a lane that passes its expected runtime without a side effect as stuck. Stand it down and dispatch a replacement at once. Do not wait for a polite return. Each tick also runs that stuck test over every owner's `children.tsv`. The owner records each stuck subagent as stuck and replaces it if its work is still needed. The root does both when the owner cannot. A stall never proves or drops the work. End the tick only when no delegated work is left. |
There was a problem hiding this comment.
When an owner or verifier exits with an error before its expected runtime, it does not satisfy the only remaining stuck condition, and it is no longer delegated work, so the tick can end without replacing it. The deleted Autopilot-full logic explicitly classified errored lanes as stuck; preserve that condition here so an early tool or agent failure cannot silently drop required build or verification work.
Useful? React with 👍 / 👎.
| "AskQuestion", "Task tool", "subagent_type", "generalPurpose", "pstack-models", "setup-pstack", | ||
| "cursor-team-kit", "create-skill", "~/.cursor/", "poteto-mode", "poteto-agent", | ||
| "grok-", "gpt-5", "claude-opus-", | ||
| "grok-", "gpt-5", "claude-opus-", "deslop", "control-ui", "control-cli", "\u2014", |
There was a problem hiding this comment.
The new terms are checked only under skills/, so user-facing guide regressions still pass validation; the current docs/guide/05-build-and-clean.md demonstrates this with deslop and cursor-team-kit on line 51 and another deslop instruction on line 73. Include docs/guide in the term scan and clean these references so the validator enforces the repository's harness-neutral requirement across the documented interface.
AGENTS.md reference: AGENTS.md:L13-L13
Useful? React with 👍 / 👎.
Rules rewritten from patterns seen in 2+ history slices, ~/AGENTS.md, and a structured interview: plan first then run, confirm pushes and PRs, strict scope, findings-only reviews, real-surface verification with thorough tests, tracker sync, handoff notes, inline by default. Drops the orchestrate and autopilot-full playbooks and inlines what autopilot-stack needed from them. check.mjs now also bans cursor-team-kit skill names and the em dash.
Stacked on the automate-me PR.
🤖 Generated with Claude Code