Generate AI prompts from the upstream catalog#131
Conversation
|
Warning Review limit reached
More reviews will be available in 35 minutes and 43 seconds. Learn how PR review limits work. Your organization has used up its prepaid credits, and credit purchases are no longer available. Enable the review add-on in the billing tab to keep reviews running — you're only billed for reviews past your plan's rate limits ($0.25/file). ⌛ How to resolve this issue?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 credits. 🚦 How do rate 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 see our Fair Usage Limits Policy for further information. ℹ️ Review info⚙️ Run configurationConfiguration used: Organization UI Review profile: CHILL Plan: Pro Run ID: 📒 Files selected for processing (9)
✨ 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 |
|
Cloudflare preview deployed.
|
Greptile SummaryThis PR wires upstream
Confidence Score: 4/5Safe to merge; the generated artifacts are committed and drift-guarded, all existing tests pass, and the two parser edge cases do not affect the current upstream YAML format. The pipeline end-to-end is well-structured and tested. The two custom YAML parser issues (comment stripping before quote detection, and scripts/prepare-prompts.mjs — specifically Important Files Changed
Flowchart%%{init: {'theme': 'neutral'}}%%
flowchart TD
A[upstream react_on_rails repo] -->|prompts.yml| B[sync:docs]
B -->|content/upstream/prompts.yml| C[prepare:prompts]
C --> D[parsePromptsYaml + validatePromptCatalog]
D --> E[collectPreparedDocRoutes]
E --> F{validatePromptRoutes}
F -->|fail| G[Error: missing route]
F -->|pass| H[renderPromptArtifacts]
H --> I[prompts.ts]
H --> J[prompts.json]
H --> K[llms.txt]
I & J & K --> L[build: prepare:prompts:check]
L --> M{drift check}
M -->|no| N[Error: out of date]
M -->|yes| O[Docusaurus build]
%%{init: {'theme': 'base', 'themeVariables': {"darkMode": true, "background": "#0d1117", "primaryColor": "#21262d", "primaryTextColor": "#e6edf3", "primaryBorderColor": "#8b949e", "lineColor": "#8b949e", "textColor": "#e6edf3", "edgeLabelBackground": "#161b22", "actorBkg": "#21262d", "actorBorder": "#8b949e", "actorTextColor": "#e6edf3", "actorLineColor": "#8b949e", "signalColor": "#8b949e", "signalTextColor": "#e6edf3", "noteBkgColor": "#373320", "noteBorderColor": "#d4a72c", "noteTextColor": "#f0e6c0", "labelBoxBkgColor": "#21262d", "labelBoxBorderColor": "#8b949e", "labelTextColor": "#e6edf3", "loopTextColor": "#e6edf3", "activationBkgColor": "#30363d", "activationBorderColor": "#8b949e"}}}%%
flowchart TD
A[upstream react_on_rails repo] -->|prompts.yml| B[sync:docs]
B -->|content/upstream/prompts.yml| C[prepare:prompts]
C --> D[parsePromptsYaml + validatePromptCatalog]
D --> E[collectPreparedDocRoutes]
E --> F{validatePromptRoutes}
F -->|fail| G[Error: missing route]
F -->|pass| H[renderPromptArtifacts]
H --> I[prompts.ts]
H --> J[prompts.json]
H --> K[llms.txt]
I & J & K --> L[build: prepare:prompts:check]
L --> M{drift check}
M -->|no| N[Error: out of date]
M -->|yes| O[Docusaurus build]
Reviews (1): Last reviewed commit: "Generate prompts from the upstream catal..." | Re-trigger Greptile |
There was a problem hiding this comment.
💡 Codex Review
Here are some automated review suggestions for this pull request.
Reviewed commit: 8208d89d1c
ℹ️ 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".
Bugbot couldn't run - usage limit reachedBugbot is counted against Cursor usage for this user or team, and this run hit a usage or spend limit. A user or team admin can review and increase usage limits in the Cursor dashboard. (requestId: serverGenReqId_99118f41-dbcf-46fa-b406-1eb0d9a678d8) |
|
Addressed the Greptile parser edge-case findings in 11bb92c:
Fresh local checks after the change: I left the |
There was a problem hiding this comment.
💡 Codex Review
Here are some automated review suggestions for this pull request.
Reviewed commit: 11bb92c6e9
ℹ️ 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".
Bugbot couldn't run - usage limit reachedBugbot is counted against Cursor usage for this user or team, and this run hit a usage or spend limit. A user or team admin can review and increase usage limits in the Cursor dashboard. (requestId: serverGenReqId_9c0529fa-ea19-4d42-a7fd-364915df06d4) |
|
You have reached your Codex usage limits for code reviews. You can see your limits in the Codex usage dashboard. |
|
You have reached your Codex usage limits for code reviews. You can see your limits in the Codex usage dashboard. |
|
You have reached your Codex usage limits for code reviews. You can see your limits in the Codex usage dashboard. |
Summary
react_on_rails/prompts.ymlintocontent/upstream/prompts.ymlduringsync:docs.prototypes/docusaurus/src/constants/prompts.ts,static/prompts.json, andstatic/prompts/llms.txtfrom the synced catalog.static/llms.txtdocs route-map artifact from the currentmainstatic-file sync, avoiding a prompt/docs artifact collision.doc_routevalues against prepared Docusaurus routes and heading fragments before publishing artifacts.buildchecks committed artifacts, and PR CI fails if prompt generation rewrites tracked artifacts duringprepare:docs.mainso the prompt sync coexists with the rootllms*.txtstatic-file sync.Closes #126.
Evidence
6b48ca053d9dc9e67aabf645177f00a95b72a610, merged 2026-06-19T04:49:32Z)./prompts/llms.txtand/prompts.jsonare emitted underprototypes/docusaurus/static/and present in the Docusaurus build output./llms.txtremains available for the docs machine-readable route map produced by the root static-file sync onmain.Tests
npm run test:prepare-promptsnode --test scripts/sync-docs.test.mjsnpm run test:docs-layoutnode --test scripts/prepare-docs.test.mjsnpm run sync:docs && npm run prepare:docs && npm run buildnpm run buildgit diff --check/git diff --cached --checkNote:
npm run buildpasses with the existing Docusaurus broken-link/broken-anchor warnings from synced docs.Review Resolution
11bb92c.83fa3cc.a43bac1by failing PR CI when generation changes tracked prompt artifacts.mainrootllms.txtcollision ine364dbbby moving the prompt text corpus to/prompts/llms.txt.prepare:docs:subsetintentionally prepares only a reduced docs slice.Coordination / Workflow Notes
UNKNOWN;.agents/skills/pr-batch/SKILL.mdand.agents/workflows/pr-processing.mdare absent both locally and onorigin/main, so this used installed$pr-batchfallback concepts.