Port agent PR review workflow to XGrowthDashboard + README retroactive kickoff#13
Port agent PR review workflow to XGrowthDashboard + README retroactive kickoff#13scalinity wants to merge 2 commits into
Conversation
Add XGrowthDashboard-tailored workflow, PR template, and AGENTS/README sections under porting/. Expand everybot README with retroactive kickoff notes. Co-authored-by: Daniel Escalante <scalinity@users.noreply.github.com>
|
Important Review skippedReview was skipped due to path filters ⛔ Files ignored due to path filters (7)
CodeRabbit blocks several paths by default. You can override this behavior by explicitly including those paths in the path filters. For example, including ⚙️ Run configurationConfiguration used: Organization UI Review profile: ASSERTIVE Plan: Pro Run ID: You can disable this status message by setting the Use the checkbox below for a quick retry:
Comment |
Agent review debateThis pull request was opened by an automated agent (Cursor Cloud Agent). Starting the cross-agent review thread so we capture findings before merge. @codex review @claude Please review this PR and engage with Codex's findings — agree or disagree on each P0/P1, note missing risks, and keep the debate in this thread before merge. Review focus (everybot)
Repo guidance: see Automated by agent-pr-review-kickoff.yml · PR: #13 |
|
To use Codex here, create a Codex account and connect to github. |
There was a problem hiding this comment.
💡 Codex Review
Here are some automated review suggestions for this pull request.
Reviewed commit: ce4ff231f5
ℹ️ 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".
| ## What this file is not | ||
|
|
||
| This file is project-specific operational rules. Architecture decisions and product reasoning live in `spec.md`. Day-to-day status lives in `docs/index.html` (interactive). `docs/IMPLEMENTATION_STATUS.md` is frozen at Phase 5.8 — don't append to it. Don't duplicate any of this here. |
There was a problem hiding this comment.
Trim the AGENTS copy snippet to the new section
When someone follows porting/XGrowthDashboard/README.md and appends AGENTS-review-section.md before the existing ## What this file is not, this included heading and paragraph duplicate the target file's existing closing section instead of adding only the review guidelines. The patch path is fine, but the documented copy path produces malformed AGENTS guidance unless this snippet contains only the new Agent PR review section.
Useful? React with 👍 / 👎.
| # X Growth Dashboard | ||
|
|
||
| Local-first "weight-loss dashboard for X growth." Single-user personal tool. Not distributed. | ||
|
|
||
| See `spec.md` for the full product spec and `docs/IMPLEMENTATION_STATUS.md` for current phase. |
There was a problem hiding this comment.
Remove the README preamble from the insert snippet
The porting instructions say to insert README-agent-review-section.md after the intro paragraph, but this file itself starts with the README title and intro/current-phase paragraphs. Anyone using the copy method rather than git am will duplicate the top of the target README before the Agent PR reviews section, so this snippet should contain only the section being inserted.
Useful? React with 👍 / 👎.
| const { data: comments } = await github.rest.issues.listComments({ | ||
| owner: context.repo.owner, | ||
| repo: context.repo.repo, | ||
| issue_number: prNumber, | ||
| per_page: 100, | ||
| }); | ||
| if (comments.some((c) => c.body?.includes(marker))) { |
There was a problem hiding this comment.
Page through comments before deciding no kickoff exists
On a retroactive kickoff for a PR that already has more than 100 comments, the marker is created after those existing comments; later synchronize or edited runs still inspect only the first page and won't see that marker, so the supposedly deduped workflow can post repeated @codex review comments. Please paginate issues.listComments or query by marker another way before deciding to create a new kickoff.
Useful? React with 👍 / 👎.
| Or apply the included patch from repo root: | ||
|
|
||
| ```bash | ||
| git am porting/XGrowthDashboard/0001-feat-ci-add-agent-PR-review-kickoff-workflow-for-cur.patch |
There was a problem hiding this comment.
Point the patch command at the everybot checkout
The documented git am command is meant to be run from a fresh XGrowthDashboard repo root, but that checkout will not contain porting/XGrowthDashboard/..., so the command fails before applying the prepared patch. Use an absolute or relative path back to the everybot checkout here, matching the PR body, or instruct users to copy the patch file into the target repo first.
Useful? React with 👍 / 👎.
Resolve README conflict: keep bootstrap README and License from main, retain retroactive agent review kickoff instructions. Co-authored-by: Daniel Escalante <scalinity@users.noreply.github.com>
|
Closed via Close open pull requests workflow (team cleanup). |
Summary
everybot already has the agent PR review workflow on
main(merged #4–#11). This PR adds:README.md(@codex reviewmust be in a PR comment, not only the description).porting/XGrowthDashboard/— ready-to-apply bundle for scalinity/XGrowthDashboard (the Cloud Agent token cannot push there; apply via patch or copy).Apply to XGrowthDashboard
From a fresh
maincheckout of XGrowthDashboard:git checkout -b cursor/agent-pr-review-workflow-a786 # Copy files per porting/XGrowthDashboard/README.md, or: git am /path/to/everybot/porting/XGrowthDashboard/0001-feat-ci-add-agent-PR-review-kickoff-workflow-for-cur.patch git push -u origin cursor/agent-pr-review-workflow-a786What lands at XGrowth repo root
AGENTS.md.github/workflows/agent-pr-review-kickoff.ymlcursor/*;workflow_dispatch+pr_number.github/pull_request_template.mdREADME.mdValidation
actionlintpasses onporting/XGrowthDashboard/.github/workflows/agent-pr-review-kickoff.ymlmainworkflow unchanged (already live)Agent review
@codex @claude — review this port PR; debate in-thread before merge.
Slack Thread