docs: position Tutti as agent ops - #125
Merged
Merged
Conversation
📝 WalkthroughWalkthroughDocumentation refactors reposition Tutti as an adapter-based "agent operations" layer and generalize the SDLC loop into five durable stages: intake → execution → review → gate → record; README, new WHY_TUTTI, CODEX_SDLC_ORCHESTRATION, and pr-review-loop docs were updated to reflect templates, quickstart commands, architecture, and review gating. ChangesAdapter-Based Operations Platform Positioning
Sequence Diagram(s)sequenceDiagram
autonumber
participant Dev
participant Tutti as Orchestrator
participant Adapter
participant CI_VCS as VCS/CI
participant Log as EventLog
Dev->>Tutti: submit/change (intake)
Tutti->>Adapter: dispatch execution request
Adapter->>Tutti: execution result (artifacts, status)
Tutti->>Adapter: request review (review slot)
Adapter->>Tutti: review resolution (approved/comment)
Tutti->>CI_VCS: verify required checks
CI_VCS->>Tutti: checks green/failed
Tutti->>Log: record final outcome (record)
Estimated code review effort🎯 2 (Simple) | ⏱️ ~10 minutes Possibly related PRs
Poem
🚥 Pre-merge checks | ✅ 5✅ Passed checks (5 passed)
✏️ Tip: You can configure your own custom pre-merge checks in the settings. ✨ Finishing Touches🧪 Generate unit tests (beta)
Thanks for using CodeRabbit! It's free for OSS, and your support helps us grow. If you like it, consider giving us a shout-out. Review rate limit: 0/1 reviews remaining, refill in 60 minutes.Comment |
![coderabbitai[bot]](https://avatars.githubusercontent.com/in/347564?s=60&v=4){kind=small}
There was a problem hiding this comment.
🧹 Nitpick comments (2)
docs/pr-review-loop.md (1)
37-47: ⚡ Quick winAlign the canonical loop wording with the adapter model.
Line 39 defines a durable, adapter-neutral gate, but the canonical loop still hardcodes CodeRabbit-specific waiting language at Line 17. Make Step 2 adapter-neutral and keep CodeRabbit as an example to avoid mixed guidance.
Proposed doc tweak
-2. Wait for CodeRabbit feedback (`wait_and_collect_coderabbit.py`). +2. Wait for configured review-adapter feedback (for CodeRabbit today: `wait_coderabbit.sh` + `collect_coderabbit_feedback.sh`).🤖 Prompt for AI Agents
Verify each finding against the current code and only fix it if needed. In `@docs/pr-review-loop.md` around lines 37 - 47, Update the canonical loop Step 2 to use adapter-neutral wording: replace the CodeRabbit-specific "wait for CodeRabbit thread resolution" phrasing with a generic gate such as "wait for durable gate: review feedback resolved and required checks green", and move the CodeRabbit-specific behavior (e.g., "CodeRabbit thread resolution -> review feedback resolved") into the Adapter model / examples section; ensure Step 2 references the durable gate concept (not CodeRabbit) while the Adapter model lists CodeRabbit as an example implementation.README.md (1)
23-31: ⚡ Quick winAvoid dual “Quick Start” entry points.
This new activation flow is strong, but there is another
## Quick Startat Line 118 with overlapping setup steps. Rename the later section (e.g., source install/manual setup) or merge them so onboarding has one obvious path.Proposed doc tweak
-## Quick Start +## Install from source (alternative)🤖 Prompt for AI Agents
Verify each finding against the current code and only fix it if needed. In `@README.md` around lines 23 - 31, There are two duplicate "## Quick Start" headings causing confusion; locate the first quick-start block that shows the new activation flow (the bash snippet with cargo/tt commands) and the later "## Quick Start" section, then either merge their unique setup steps into a single consolidated Quick Start or rename the later section to a clear alternative title (e.g., "Source install / Manual setup" or "Alternative installation") and update any cross-references so the onboarding has one obvious entry point; ensure the renamed header uses consistent Markdown heading syntax.
🤖 Prompt for all review comments with AI agents
Verify each finding against the current code and only fix it if needed.
Nitpick comments:
In `@docs/pr-review-loop.md`:
- Around line 37-47: Update the canonical loop Step 2 to use adapter-neutral
wording: replace the CodeRabbit-specific "wait for CodeRabbit thread resolution"
phrasing with a generic gate such as "wait for durable gate: review feedback
resolved and required checks green", and move the CodeRabbit-specific behavior
(e.g., "CodeRabbit thread resolution -> review feedback resolved") into the
Adapter model / examples section; ensure Step 2 references the durable gate
concept (not CodeRabbit) while the Adapter model lists CodeRabbit as an example
implementation.
In `@README.md`:
- Around line 23-31: There are two duplicate "## Quick Start" headings causing
confusion; locate the first quick-start block that shows the new activation flow
(the bash snippet with cargo/tt commands) and the later "## Quick Start"
section, then either merge their unique setup steps into a single consolidated
Quick Start or rename the later section to a clear alternative title (e.g.,
"Source install / Manual setup" or "Alternative installation") and update any
cross-references so the onboarding has one obvious entry point; ensure the
renamed header uses consistent Markdown heading syntax.
ℹ️ Review info
⚙️ Run configuration
Configuration used: Repository UI
Review profile: CHILL
Plan: Pro
Run ID: 85dc5818-6bcc-4e6b-9b74-48e3fdb8e605
📒 Files selected for processing (4)
README.mddocs/CODEX_SDLC_ORCHESTRATION.mddocs/WHY_TUTTI.mddocs/pr-review-loop.md
Contributor
Author
|
@coderabbitai review |
✅ Actions performedReview triggered.
|
There was a problem hiding this comment.
🧹 Nitpick comments (1)
README.md (1)
147-147: ⚡ Quick winMake the status header explicitly time-scoped to avoid fast staleness.
Line 147 uses
v0.10.0+ — May 2026, which can read as “current” even after it ages. Consider wording like “As of May 2026” or moving the date into a sentence below the heading.🤖 Prompt for AI Agents
Verify each finding against the current code and only fix it if needed. In `@README.md` at line 147, The heading "## Project Status (v0.10.0+ — May 2026)" reads as evergreen; update it to time-scoped wording such as "## Project Status (v0.10.0+ — As of May 2026)" or remove the date from the header and add a sentence immediately below like "Status information current as of May 2026" so the file clearly signals the snapshot date; edit the README heading text accordingly (reference header text "## Project Status (v0.10.0+ — May 2026)").
🤖 Prompt for all review comments with AI agents
Verify each finding against the current code and only fix it if needed.
Nitpick comments:
In `@README.md`:
- Line 147: The heading "## Project Status (v0.10.0+ — May 2026)" reads as
evergreen; update it to time-scoped wording such as "## Project Status (v0.10.0+
— As of May 2026)" or remove the date from the header and add a sentence
immediately below like "Status information current as of May 2026" so the file
clearly signals the snapshot date; edit the README heading text accordingly
(reference header text "## Project Status (v0.10.0+ — May 2026)").
ℹ️ Review info
⚙️ Run configuration
Configuration used: Repository UI
Review profile: CHILL
Plan: Pro
Run ID: 8d20f9cc-e865-46c0-b947-971760798bd3
📒 Files selected for processing (2)
README.mddocs/pr-review-loop.md
✅ Files skipped from review due to trivial changes (1)
- docs/pr-review-loop.md
This was referenced May 4, 2026
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
1 participant
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Summary
Versioning (required)
Cargo.tomlversionCHANGELOG.mdNo version bump: documentation-only positioning/onboarding change. No CLI, workflow contract, runtime behavior, package contents, or release artifact changes.
SemVer choice
Version selected:
vN/A(docs-only, no release bump)Validation
cargo test -qRelease
vX.Y.Z)No tag planned. This PR should ride with the next documentation/release train.
Summary by CodeRabbit