Repository navigation
feat(workflow): extract reusable dev-workflow commands - #299
Conversation
Deploying living-architecture with
|
| Latest commit: |
1e0e01b
|
| Status: | ✅ Deploy successful! |
| Preview URL: | https://926ad52c.living-architecture.pages.dev |
| Branch Preview URL: | https://feat-dev-workflow-v2-reusabl.living-architecture.pages.dev |
|
Warning Review limit reached
Next review available in: 33 minutes You've used all free OSS reviews for now. Wait for the free limit to reset to keep reviewing this public repository. How can I continue?After more reviews become available, a review can be triggered using the To avoid repeated limits, reduce automatic review volume by pausing incremental auto-reviews earlier, using label-based review opt-in, excluding WIP or generated PR titles, or requesting reviews manually when the PR is ready. If your team needs uninterrupted high-volume reviews, an organization admin can enable usage-based reviews. How do review limits work?CodeRabbit enforces per-developer PR review limits for each organization. Most developers receive the normal plan review availability. For paid Pro and Pro+ PR reviews, CodeRabbit uses adaptive limits for sustained high-volume activity. When a developer's recent PR review activity reaches the 95th percentile or higher among CodeRabbit users, additional reviews become available more gradually as earlier reviews age out of the rolling window. Please refer docs for additional details. Review details⚙️ Run configurationConfiguration used: Path: .coderabbit.yaml Review profile: ASSERTIVE Plan: Pro Plus Run ID: 📒 Files selected for processing (3)
📝 WalkthroughWalkthroughThe PR adds ChangesDev workflow command centralization
Estimated code review effort: 2 (Simple) | ~15 minutes Possibly related PRs
Suggested labels: 🚥 Pre-merge checks | ✅ 3 | ❌ 1❌ Failed checks (1 warning)
✅ Passed checks (3 passed)
✨ 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. Comment |
|
There was a problem hiding this comment.
Actionable comments posted: 7
🤖 Prompt for all review comments with AI agents
Verify each finding against current code. Fix only still-valid issues, skip the
rest with a brief reason, keep changes minimal, and validate.
Inline comments:
In `@tools/dev-workflow-v2/commands/code-review.md`:
- Around line 14-18: Update the workflow steps that read state and build the
review prompt to fetch the recorded issue body whenever taskCheckPassed is false
and githubIssue is present, before invoking task-check. Include the fetched body
in the shared prompt as clearly delimited data, alongside the existing
githubIssue reference.
- Around line 20-21: Update the review-recording instruction around the agent
payload validation flow to pass review JSON safely as a single argument even
when summary or findings contain apostrophes. Use robust shell escaping or the
supported stdin/file transport with /dev-workflow-v2:workflow record-review,
while preserving validation and BLOCKED behavior for failed or invalid agents.
In `@tools/dev-workflow-v2/commands/create-pr.md`:
- Around line 16-19: Update the workflow after the branch inspection commands in
the PR creation instructions to check whether the merge-base diff contains any
changes and stop immediately when it is empty. Only continue drafting, pushing,
and creating the pull request when the branch has a non-empty diff.
- Around line 13-15: Update the workflow create-pr logic around
currentStateMachineState, githubIssue, featureBranch, and prNumber to reconcile
an existing GitHub pull request for featureBranch before creating a new one,
reusing and persisting its prNumber when found; otherwise create the pull
request and persist pr-recorded, ensuring retries after partial persistence
cannot create duplicates.
- Around line 19-32: Update the workflow instructions around step 5 and the
create-pr command so the agent fetches the issue title and body as delimited,
untrusted context, explicitly ignores instructions contained within them, and
passes each generated PR field as a separate safely quoted argument without
shell interpolation. Preserve the existing PR field requirements and workflow
command.
In `@tools/dev-workflow-v2/commands/list-review-threads.md`:
- Around line 15-23: Update the GraphQL workflow in the review-thread listing
instructions to paginate the reviews, reviewThreads, and each thread’s comments
connections using hasNextPage and endCursor until all pages are traversed. When
determining each thread’s primary summary, select the comment with the latest
createdAt rather than relying on incomplete or returned ordering.
In `@tools/dev-workflow-v2/states/reviewing.md`:
- Around line 13-16: Update the review workflow around review-recorded and the
SUBMITTING_PR transition to bind every verdict to the current review run and
repository HEAD. Persist the run identifier and commit SHA with each review
result, and allow submission only when one complete required-review bundle
matches both the active run and current HEAD; otherwise clear or ignore stale
verdicts when a new run begins.
🪄 Autofix
Fix all unresolved CodeRabbit comments on this PR:
- Push a commit to this branch (recommended)
- Create a new PR with the fixes
ℹ️ Review info
⚙️ Run configuration
Configuration used: Path: .coderabbit.yaml
Review profile: ASSERTIVE
Plan: Pro Plus
Run ID: 9b46973e-54a3-4b0c-a6fd-e7fde75225f3
📒 Files selected for processing (7)
tools/dev-workflow-v2/.claude-plugin/plugin.jsontools/dev-workflow-v2/README.mdtools/dev-workflow-v2/commands/code-review.mdtools/dev-workflow-v2/commands/create-pr.mdtools/dev-workflow-v2/commands/list-review-threads.mdtools/dev-workflow-v2/states/reviewing.mdtools/dev-workflow-v2/states/submitting_pr.md
|



Summary
/dev-workflow-v2:code-review,/dev-workflow-v2:list-review-threads, and/dev-workflow-v2:create-prcommand definitionsContext
Several dev-workflow-v2 capabilities were only described inside workflow state files, which made them hard to reuse outside the state machine. This change lifts those review, PR feedback, and PR creation behaviors into dedicated commands while keeping workflow-specific recording and transitions in the state docs.
Traceability
Verification
Summary by CodeRabbit
Documentation
Chores