Skip to content

Add manual dev environment testing checklist for coding agents#3074

Merged
justin808 merged 2 commits intomainfrom
jg/manual-testing-checklist
Apr 10, 2026
Merged

Add manual dev environment testing checklist for coding agents#3074
justin808 merged 2 commits intomainfrom
jg/manual-testing-checklist

Conversation

@justin808
Copy link
Copy Markdown
Member

@justin808 justin808 commented Apr 8, 2026

Summary

Adds a structured checklist that coding agents must follow to verify the dev environment works before submitting PRs. This was motivated by shakacode/react-webpack-rails-tutorial#723 where all 38 rspec tests passed but bin/dev wouldn't even start — the agent never tested the actual development experience.

The new doc at .claude/docs/manual-dev-environment-testing.md defines 5 phases (dev server startup, page smoke test, SSR verification, interactive functionality, process health), a matrix mapping change types to required phases, common failure modes, and a reporting template. AGENTS.md and CLAUDE.md are updated to reference it.

Pull Request checklist

  • Add/update test to cover these changes
  • Update documentation
  • Update CHANGELOG file

Other Information

Kept abstract and repo-agnostic — no hardcoded paths or routes from the tutorial app. The checklist applies to any Rails + React on Rails app with a Procfile.dev-based dev setup.


Note

Low Risk
Low risk: documentation-only changes that add contributor guidance and do not affect runtime code paths.

Overview
Adds a new .claude/docs/manual-dev-environment-testing.md guide requiring manual bin/dev verification (startup, page smoke, SSR checks, interactivity, and process health) for PRs that change startup/build/serve behavior, plus a reporting template for PR descriptions.

Updates AGENTS.md and CLAUDE.md to reference this checklist so agents consistently run dev-environment smoke tests in addition to automated suites.

Reviewed by Cursor Bugbot for commit 7bda689. Bugbot is set up for automated code reviews on this repo. Configure here.

Summary by CodeRabbit

  • Documentation
    • Added a comprehensive manual development-environment testing guide that requires PRs affecting app startup, build, or serving to include manual verification. Includes phased checklists (startup, per-page smoke tests, SSR, interactivity, process health), change-type-to-required-phase mapping, common failure modes, and reporting templates.
    • Updated agent and operational docs to reference the new testing guidance.

Automated tests can pass while bin/dev is completely broken (as seen in
shakacode/react-webpack-rails-tutorial#723). This adds a structured
checklist that agents must follow when changes affect how the app starts,
builds, or serves.

Co-Authored-By: Claude Opus 4.6 (1M context) <[email protected]>
@coderabbitai
Copy link
Copy Markdown
Contributor

coderabbitai Bot commented Apr 8, 2026

Walkthrough

Added a new manual dev-environment testing checklist and updated repository instructions to require manual verification for PRs that affect application startup, build, or serving behavior.

Changes

Cohort / File(s) Summary
Manual Dev Environment Checklist
.claude/docs/manual-dev-environment-testing.md
New comprehensive manual end-to-end verification guide with five phased checklists (dev server startup, per-route smoke tests, SSR checks, interactive functionality, process health), change-type → required-phase mapping, common failure modes, and PR reporting templates.
Docs / Agent References
AGENTS.md, CLAUDE.md
Added rule pointing agents to perform manual environment verification when changes affect startup/build/serve; added reference to the new checklist document.

Estimated code review effort

🎯 1 (Trivial) | ⏱️ ~3 minutes

Poem

🐰 I hopped through docs and left a trail,
Five checks to follow, detailed and hale.
From startup hum to pages true,
I tested paths and watched for few—
Devs can rest while rabbits prevail. 🥕

🚥 Pre-merge checks | ✅ 3
✅ Passed checks (3 passed)
Check name Status Explanation
Description Check ✅ Passed Check skipped - CodeRabbit’s high-level summary is enabled.
Title check ✅ Passed The title clearly and specifically describes the main change: adding a manual dev environment testing checklist document for coding agents.
Docstring Coverage ✅ Passed No functions found in the changed files to evaluate docstring coverage. Skipping docstring coverage check.

✏️ Tip: You can configure your own custom pre-merge checks in the settings.

✨ Finishing Touches
🧪 Generate unit tests (beta)
  • Create PR with unit tests
  • Commit unit tests in branch jg/manual-testing-checklist

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.

❤️ Share

Comment @coderabbitai help to get the list of available commands and usage tips.

Copy link
Copy Markdown

@chatgpt-codex-connector chatgpt-codex-connector Bot left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

💡 Codex Review

Here are some automated review suggestions for this pull request.

Reviewed commit: 4db9e56455

ℹ️ 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".

Comment thread .claude/docs/manual-dev-environment-testing.md Outdated
@greptile-apps
Copy link
Copy Markdown

greptile-apps Bot commented Apr 8, 2026

Greptile Summary

Adds .claude/docs/manual-dev-environment-testing.md — a structured 5-phase checklist for agents to verify the dev environment before submitting PRs — and wires it into both AGENTS.md and CLAUDE.md. The doc is well-scoped, repo-agnostic, and its two cross-references (pr-testing-guide.md, testing-build-scripts.md) both resolve correctly.

Confidence Score: 5/5

Safe to merge — documentation-only change with no runtime impact.

All three files are documentation/config only. Cross-references resolve correctly, the prose is clear and actionable, and the single finding (Phase 1 omitted from two table rows) is a P2 clarity nit that doesn't block merge.

No files require special attention.

Vulnerabilities

No security concerns identified.

Important Files Changed

Filename Overview
.claude/docs/manual-dev-environment-testing.md New doc defining 5 checklist phases for manual dev-env verification; cross-references (pr-testing-guide.md, testing-build-scripts.md) both exist; minor table ambiguity where Phase 1 is omitted for rows that implicitly depend on it.
AGENTS.md Single line added under Testing section linking to the new manual-dev-environment-testing.md guide; path and prose are correct.
CLAUDE.md One entry appended to the Claude-Specific Workflow doc list pointing to the new guide; no issues.

Flowchart

%%{init: {'theme': 'neutral'}}%%
flowchart TD
    A[PR changes detected] --> B{Touches startup/build/serve?}
    B -- No --> C[Manual testing optional]
    B -- Yes --> D[Consult phase matrix]
    D --> E[Phase 1: Dev Server Startup\nBLOCKING]
    E -- Fails --> F[🛑 Stop — fix before proceeding]
    E -- Passes --> G{Required phases\nper change type}
    G --> H[Phase 2: Page Smoke Test]
    G --> I[Phase 3: SSR Verification]
    G --> J[Phase 4: Interactive Functionality]
    G --> K[Phase 5: Process Health]
    H & I & J & K --> L[Report results in PR description]
    L --> M{Can't run bin/dev?}
    M -- Yes --> N[⚠️ Declare DEV ENVIRONMENT UNTESTED]
    M -- No --> O[✅ Submit PR]
Loading

Reviews (1): Last reviewed commit: "Add manual dev environment testing check..." | Re-trigger Greptile

Comment thread .claude/docs/manual-dev-environment-testing.md
Copy link
Copy Markdown
Contributor

@coderabbitai coderabbitai Bot left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Actionable comments posted: 1

🧹 Nitpick comments (1)
.claude/docs/manual-dev-environment-testing.md (1)

72-72: Use hyphenated compound adjective for readability.

full page reloadsfull-page reloads.

🤖 Prompt for AI Agents
Verify each finding against the current code and only fix it if needed.

In @.claude/docs/manual-dev-environment-testing.md at line 72, Update the
checklist line that currently reads "Client-side navigation works without full
page reloads (for SPA routes)" to use the hyphenated compound adjective: change
"full page reloads" to "full-page reloads" so the line becomes "Client-side
navigation works without full-page reloads (for SPA routes)"; locate and edit
that exact checklist item in the document to apply the fix.
🤖 Prompt for all review comments with AI agents
Verify each finding against the current code and only fix it if needed.

Inline comments:
In @.claude/docs/manual-dev-environment-testing.md:
- Around line 31-35: Replace the "yarn install" command in the shell snippet
with "pnpm install" so the JS dependency step uses pnpm only; specifically
update the code block that currently contains "yarn install  # or pnpm install,
per project" to instead read "pnpm install" (remove the yarn alternative) so the
manual-dev-environment-testing instructions enforce pnpm for JavaScript
installs.

---

Nitpick comments:
In @.claude/docs/manual-dev-environment-testing.md:
- Line 72: Update the checklist line that currently reads "Client-side
navigation works without full page reloads (for SPA routes)" to use the
hyphenated compound adjective: change "full page reloads" to "full-page reloads"
so the line becomes "Client-side navigation works without full-page reloads (for
SPA routes)"; locate and edit that exact checklist item in the document to apply
the fix.
🪄 Autofix (Beta)

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: Organization UI

Review profile: CHILL

Plan: Pro

Run ID: b9f04e74-4245-48a2-86b3-b725bdaccf4d

📥 Commits

Reviewing files that changed from the base of the PR and between 7bed8ec and 4db9e56.

📒 Files selected for processing (3)
  • .claude/docs/manual-dev-environment-testing.md
  • AGENTS.md
  • CLAUDE.md

Comment thread .claude/docs/manual-dev-environment-testing.md
Comment thread .claude/docs/manual-dev-environment-testing.md Outdated
Comment thread .claude/docs/manual-dev-environment-testing.md Outdated
Comment thread .claude/docs/manual-dev-environment-testing.md
Comment thread .claude/docs/manual-dev-environment-testing.md
@claude
Copy link
Copy Markdown
Contributor

claude Bot commented Apr 8, 2026

Review: Add manual dev environment testing checklist

Well-motivated PR — the incident in shakacode/react-webpack-rails-tutorial#723 is exactly the kind of failure that structured checklists prevent. The structure (phases, trigger matrix, failure modes, reporting template) is solid and follows the pattern of existing docs in .claude/docs/.

Issues

Minor corrections (see inline comments):

  1. yarn install as primary example (line 34) — This repo uses pnpm. Having yarn first and pnpm as a comment may mislead agents working in this repo.

  2. "Visit every route" (line 51) — Impractical at scale. Should be "primary routes" or "routes touched by the PR."

  3. Matrix gap (line 21 trigger list) — "Environment variables used at startup" appears in the trigger list but has no row in the matrix. Agents following the matrix won't know which phases apply.

  4. "Never omit this section" contradicts "optional" (line 114) — The top of the doc says manual testing is optional for docs/CI-only PRs, but the footer says never omit the reporting section. The intent is good (always disclose), but the phrasing creates a contradiction. Worth clarifying that the section should always appear even if its content is "skipped because docs-only."

No blocking concerns

The AGENTS.md and CLAUDE.md changes are clean — the new bullet slots in naturally and the link path is consistent with other references in those files. The pr-testing-guide.md and testing-build-scripts.md cross-links both resolve to real files.

@justin808
Copy link
Copy Markdown
Member Author

Skipped-item rationale for summary-only comments:

@justin808
Copy link
Copy Markdown
Member Author

Review cleanup summary for PR #3074.

Scan window: full PR history (no previous summary cutoff; no check all reviews override). Reviewed feedback created between 2026-04-08T03:36:10Z and 2026-04-08T03:39:35Z.

Mattered

  • Addressed .claude/docs/manual-dev-environment-testing.md:34: replaced yarn install primary example with pnpm install and kept a generic note for project-required package manager.
  • Addressed .claude/docs/manual-dev-environment-testing.md:93-95: added explicit Phase 1 prerequisite for New routes or pages and React component changes.
  • Addressed .claude/docs/manual-dev-environment-testing.md:93: added matrix row for Environment variables used at startup (1, 2, 3).
  • Addressed .claude/docs/manual-dev-environment-testing.md:51: narrowed route smoke-test guidance to primary routes and PR-touched routes.
  • Addressed .claude/docs/manual-dev-environment-testing.md:133: clarified reporting guidance so optional skips are disclosed explicitly.

Skipped

  • https://github.com/shakacode/react_on_rails/pull/3074#issuecomment-4203619743 (CodeRabbit walkthrough): summary/status-only content.
  • https://github.com/shakacode/react_on_rails/pull/3074#issuecomment-4203623161 (Greptile summary): summary-only content.
  • https://github.com/shakacode/react_on_rails/pull/3074#issuecomment-4203633920 (Claude summary): duplicate synthesis of inline comments already handled.
  • https://github.com/shakacode/react_on_rails/pull/3074#discussion_r3049042668 (CodeRabbit inline): duplicate of existing yarn/pnpm thread.
  • https://github.com/shakacode/react_on_rails/pull/3074#discussion_r3049044787 (Claude inline): duplicate of existing yarn/pnpm thread.

Inline feedback threads for handled items were replied to and resolved; skipped-summary rationale was posted at https://github.com/shakacode/react_on_rails/pull/3074#issuecomment-4212584742.

Future full-PR scans should start after this summary comment unless check all reviews is explicitly requested.

Copy link
Copy Markdown

@chatgpt-codex-connector chatgpt-codex-connector Bot left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

💡 Codex Review

Here are some automated review suggestions for this pull request.

Reviewed commit: 7bda6896da

ℹ️ 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".

```bash
# 1. Install dependencies
bundle install
pnpm install # or your project's required JS package manager
Copy link
Copy Markdown

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

P2 Badge Enforce pnpm-only command in Phase 1 checklist

Fresh evidence after the earlier yarn-specific wording was removed: this line still states pnpm install “or your project's required JS package manager,” which tells agents that non-pnpm managers are acceptable. In this repository, AGENTS.md requires pnpm for all JS operations and forbids npm/yarn, so following this checklist during mandatory dev-environment verification can still produce unsupported dependency state (including stray lockfiles) and inconsistent local results.

Useful? React with 👍 / 👎.

Copy link
Copy Markdown
Contributor

@coderabbitai coderabbitai Bot left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Actionable comments posted: 1

♻️ Duplicate comments (1)
.claude/docs/manual-dev-environment-testing.md (1)

34-34: ⚠️ Potential issue | 🟠 Major

Enforce pnpm-only wording for agent instructions

Line 34 still allows alternate JS package managers (or your project's required JS package manager), which conflicts with repo policy for agent-facing workflows. Please make this command strictly pnpm-only in this document.

Suggested edit
-pnpm install  # or your project's required JS package manager
+pnpm install

Based on learnings: "Follow AGENTS.md as the canonical policy for commands, tests, lint workflow, formatting, style requirements, git/PR safety boundaries, and project directory boundaries." and "Use pnpm for all JavaScript/Node operations; never use npm or yarn.

🤖 Prompt for AI Agents
Verify each finding against the current code and only fix it if needed.

In @.claude/docs/manual-dev-environment-testing.md at line 34, Remove the
alternative package manager text and make the instruction strictly pnpm-only by
replacing the existing line containing "pnpm install  # or your project's
required JS package manager" with a single command "pnpm install" so the
agent-facing doc enforces the repo policy; update the line that contains the
pnpm install command to exactly "pnpm install" (no trailing commentary).
🤖 Prompt for all review comments with AI agents
Verify each finding against the current code and only fix it if needed.

Inline comments:
In @.claude/docs/manual-dev-environment-testing.md:
- Line 72: Update the checklist item text "[ ] Client-side navigation works
without full page reloads (for SPA routes)" by hyphenating the compound
adjective to read "full-page reloads" so the line becomes "[ ] Client-side
navigation works without full-page reloads (for SPA routes)"; locate and edit
that exact string in the .claude/docs/manual-dev-environment-testing.md file.

---

Duplicate comments:
In @.claude/docs/manual-dev-environment-testing.md:
- Line 34: Remove the alternative package manager text and make the instruction
strictly pnpm-only by replacing the existing line containing "pnpm install  # or
your project's required JS package manager" with a single command "pnpm install"
so the agent-facing doc enforces the repo policy; update the line that contains
the pnpm install command to exactly "pnpm install" (no trailing commentary).
🪄 Autofix (Beta)

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: Organization UI

Review profile: CHILL

Plan: Pro

Run ID: e031c27f-6926-4b96-b2c8-099a6e8e1e6b

📥 Commits

Reviewing files that changed from the base of the PR and between 4db9e56 and 7bda689.

📒 Files selected for processing (1)
  • .claude/docs/manual-dev-environment-testing.md

### Phase 4: Interactive Functionality

- [ ] Forms submit and produce expected results
- [ ] Client-side navigation works without full page reloads (for SPA routes)
Copy link
Copy Markdown
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

⚠️ Potential issue | 🟡 Minor

Hyphenate compound adjective for clarity

On Line 72, prefer “full-page reloads” (instead of “full page reloads”) for cleaner technical writing.

🧰 Tools
🪛 LanguageTool

[uncategorized] ~72-~72: If this is a compound adjective that modifies the following noun, use a hyphen.
Context: ... ] Client-side navigation works without full page reloads (for SPA routes) - [ ] Interact...

(EN_COMPOUND_ADJECTIVE_INTERNAL)

🤖 Prompt for AI Agents
Verify each finding against the current code and only fix it if needed.

In @.claude/docs/manual-dev-environment-testing.md at line 72, Update the
checklist item text "[ ] Client-side navigation works without full page reloads
(for SPA routes)" by hyphenating the compound adjective to read "full-page
reloads" so the line becomes "[ ] Client-side navigation works without full-page
reloads (for SPA routes)"; locate and edit that exact string in the
.claude/docs/manual-dev-environment-testing.md file.

@justin808 justin808 merged commit d73245e into main Apr 10, 2026
28 of 29 checks passed
@justin808 justin808 deleted the jg/manual-testing-checklist branch April 10, 2026 04:25
justin808 added a commit that referenced this pull request Apr 12, 2026
### Summary

Adds a structured checklist that coding agents must follow to verify the
dev environment works before submitting PRs. This was motivated by
shakacode/react-webpack-rails-tutorial#723 where all 38 rspec tests
passed but `bin/dev` wouldn't even start — the agent never tested the
actual development experience.

The new doc at `.claude/docs/manual-dev-environment-testing.md` defines
5 phases (dev server startup, page smoke test, SSR verification,
interactive functionality, process health), a matrix mapping change
types to required phases, common failure modes, and a reporting
template. AGENTS.md and CLAUDE.md are updated to reference it.

### Pull Request checklist

- [x] ~Add/update test to cover these changes~
- [x] Update documentation
- [x] ~Update CHANGELOG file~

### Other Information

Kept abstract and repo-agnostic — no hardcoded paths or routes from the
tutorial app. The checklist applies to any Rails + React on Rails app
with a `Procfile.dev`-based dev setup.

<!-- CURSOR_SUMMARY -->
---

> [!NOTE]
> **Low Risk**
> Low risk: documentation-only changes that add contributor guidance and
do not affect runtime code paths.
> 
> **Overview**
> Adds a new `.claude/docs/manual-dev-environment-testing.md` guide
requiring **manual `bin/dev` verification** (startup, page smoke, SSR
checks, interactivity, and process health) for PRs that change
startup/build/serve behavior, plus a reporting template for PR
descriptions.
> 
> Updates `AGENTS.md` and `CLAUDE.md` to reference this checklist so
agents consistently run dev-environment smoke tests in addition to
automated suites.
> 
> <sup>Reviewed by [Cursor Bugbot](https://cursor.com/bugbot) for commit
7bda689. Bugbot is set up for automated
code reviews on this repo. Configure
[here](https://www.cursor.com/dashboard/bugbot).</sup>
<!-- /CURSOR_SUMMARY -->

<!-- This is an auto-generated comment: release notes by coderabbit.ai
-->
## Summary by CodeRabbit

* **Documentation**
* Added a comprehensive manual development-environment testing guide
that requires PRs affecting app startup, build, or serving to include
manual verification. Includes phased checklists (startup, per-page smoke
tests, SSR, interactivity, process health),
change-type-to-required-phase mapping, common failure modes, and
reporting templates.
* Updated agent and operational docs to reference the new testing
guidance.
<!-- end of auto-generated comment: release notes by coderabbit.ai -->

---------

Co-authored-by: Claude Opus 4.6 (1M context) <[email protected]>
justin808 added a commit that referenced this pull request Apr 12, 2026
### Summary

Adds a structured checklist that coding agents must follow to verify the
dev environment works before submitting PRs. This was motivated by
shakacode/react-webpack-rails-tutorial#723 where all 38 rspec tests
passed but `bin/dev` wouldn't even start — the agent never tested the
actual development experience.

The new doc at `.claude/docs/manual-dev-environment-testing.md` defines
5 phases (dev server startup, page smoke test, SSR verification,
interactive functionality, process health), a matrix mapping change
types to required phases, common failure modes, and a reporting
template. AGENTS.md and CLAUDE.md are updated to reference it.

### Pull Request checklist

- [x] ~Add/update test to cover these changes~
- [x] Update documentation
- [x] ~Update CHANGELOG file~

### Other Information

Kept abstract and repo-agnostic — no hardcoded paths or routes from the
tutorial app. The checklist applies to any Rails + React on Rails app
with a `Procfile.dev`-based dev setup.

<!-- CURSOR_SUMMARY -->
---

> [!NOTE]
> **Low Risk**
> Low risk: documentation-only changes that add contributor guidance and
do not affect runtime code paths.
> 
> **Overview**
> Adds a new `.claude/docs/manual-dev-environment-testing.md` guide
requiring **manual `bin/dev` verification** (startup, page smoke, SSR
checks, interactivity, and process health) for PRs that change
startup/build/serve behavior, plus a reporting template for PR
descriptions.
> 
> Updates `AGENTS.md` and `CLAUDE.md` to reference this checklist so
agents consistently run dev-environment smoke tests in addition to
automated suites.
> 
> <sup>Reviewed by [Cursor Bugbot](https://cursor.com/bugbot) for commit
7bda689. Bugbot is set up for automated
code reviews on this repo. Configure
[here](https://www.cursor.com/dashboard/bugbot).</sup>
<!-- /CURSOR_SUMMARY -->

<!-- This is an auto-generated comment: release notes by coderabbit.ai
-->
## Summary by CodeRabbit

* **Documentation**
* Added a comprehensive manual development-environment testing guide
that requires PRs affecting app startup, build, or serving to include
manual verification. Includes phased checklists (startup, per-page smoke
tests, SSR, interactivity, process health),
change-type-to-required-phase mapping, common failure modes, and
reporting templates.
* Updated agent and operational docs to reference the new testing
guidance.
<!-- end of auto-generated comment: release notes by coderabbit.ai -->

---------

Co-authored-by: Claude Opus 4.6 (1M context) <[email protected]>
justin808 added a commit that referenced this pull request Apr 12, 2026
### Summary

Adds a structured checklist that coding agents must follow to verify the
dev environment works before submitting PRs. This was motivated by
shakacode/react-webpack-rails-tutorial#723 where all 38 rspec tests
passed but `bin/dev` wouldn't even start — the agent never tested the
actual development experience.

The new doc at `.claude/docs/manual-dev-environment-testing.md` defines
5 phases (dev server startup, page smoke test, SSR verification,
interactive functionality, process health), a matrix mapping change
types to required phases, common failure modes, and a reporting
template. AGENTS.md and CLAUDE.md are updated to reference it.

### Pull Request checklist

- [x] ~Add/update test to cover these changes~
- [x] Update documentation
- [x] ~Update CHANGELOG file~

### Other Information

Kept abstract and repo-agnostic — no hardcoded paths or routes from the
tutorial app. The checklist applies to any Rails + React on Rails app
with a `Procfile.dev`-based dev setup.

<!-- CURSOR_SUMMARY -->
---

> [!NOTE]
> **Low Risk**
> Low risk: documentation-only changes that add contributor guidance and
do not affect runtime code paths.
> 
> **Overview**
> Adds a new `.claude/docs/manual-dev-environment-testing.md` guide
requiring **manual `bin/dev` verification** (startup, page smoke, SSR
checks, interactivity, and process health) for PRs that change
startup/build/serve behavior, plus a reporting template for PR
descriptions.
> 
> Updates `AGENTS.md` and `CLAUDE.md` to reference this checklist so
agents consistently run dev-environment smoke tests in addition to
automated suites.
> 
> <sup>Reviewed by [Cursor Bugbot](https://cursor.com/bugbot) for commit
7bda689. Bugbot is set up for automated
code reviews on this repo. Configure
[here](https://www.cursor.com/dashboard/bugbot).</sup>
<!-- /CURSOR_SUMMARY -->

<!-- This is an auto-generated comment: release notes by coderabbit.ai
-->
## Summary by CodeRabbit

* **Documentation**
* Added a comprehensive manual development-environment testing guide
that requires PRs affecting app startup, build, or serving to include
manual verification. Includes phased checklists (startup, per-page smoke
tests, SSR, interactivity, process health),
change-type-to-required-phase mapping, common failure modes, and
reporting templates.
* Updated agent and operational docs to reference the new testing
guidance.
<!-- end of auto-generated comment: release notes by coderabbit.ai -->

---------

Co-authored-by: Claude Opus 4.6 (1M context) <[email protected]>
justin808 added a commit that referenced this pull request Apr 12, 2026
…ages

* origin/main: (44 commits)
  Consolidate CSP nonce sanitization into shared module (#2828)
  Add comprehensive --rsc-pro generator tests (#3098)
  fix: cross-env validation and docs for renderer password (#3090)
  Improve package metadata and Pro upgrade CTAs (#3112)
  docs: standardize warning syntax to GFM alert format (#3115)
  docs: improve react-intl documentation for React Server Components (#3085)
  Fix generator CI SSR regression on main (#3110)
  Refocus GitHub README on docs navigation (#3113)
  Add manual dev environment testing checklist for coding agents (#3074)
  Bump version to 16.6.0
  Update CHANGELOG.md for 16.6.0 (#3078)
  fix: node-renderer diagnostic improvements (#3086)
  fix: pin third-party npm deps in generator to prevent peer dep conflicts (#3083)
  chore(deps): bump lodash from 4.17.23 to 4.18.1 in the npm-security group across 1 directory (#2920)
  fix: refactor formatExceptionMessage to accept generic request context (#2877)
  Bump version to 16.6.0.rc.1
  Update CHANGELOG.md for 16.6.0.rc.1 (#3079)
  Update CHANGELOG.md unreleased section (#3077)
  Fix Content-Length mismatch and null renderingRequest errors in node renderer (#3069)
  Improve memory debugging docs with simpler heap snapshot approach (#3072)
  ...

# Conflicts:
#	docs/pro/home-pro.md
#	docs/pro/react-on-rails-pro.md
#	docs/sidebars.ts
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant