Add AI analysis prompt generator to config exporter #695
Conversation
When running `bin/export-bundler-config --doctor`, the tool now generates an AI-ANALYSIS-PROMPT.md file alongside the exported configuration files. This prompt file provides comprehensive instructions for AI assistants to analyze webpack/rspack configurations and suggest improvements. It includes: - Context about the exported configuration files - React on Rails standard configuration patterns - Analysis objectives covering: * Migration issues (webpack ↔ rspack) * Build errors and warnings * Client vs server optimizations * Development vs production optimizations * Best practices and performance improvements - Instructions for providing additional context (build logs, custom configs) - Desired output format specification The prompt is designed to help developers get actionable feedback from AI tools (ChatGPT, Claude, Gemini, etc.) when troubleshooting or optimizing their bundler configurations. Changes: - Add AiPromptGenerator class in package/configExporter/aiPromptGenerator.ts - Integrate prompt generation into doctor mode in cli.ts - Export AiPromptGenerator from configExporter/index.ts - Add comprehensive test suite for AI prompt generation - Update troubleshooting.md documentation
WalkthroughAdds an AI prompt generator and integrates it into the config-export "doctor" flow: generates AI-ANALYSIS-PROMPT.md alongside exported files, updates CLI output to include the artifact, re-exports the generator, adds tests, updates docs, and changes the package public TypeScript declaration export shape. Changes
Sequence Diagram(s)sequenceDiagram
autonumber
actor User
participant CLI as configExporter/cli
participant Exporter as Config Exporter
participant Prompt as AiPromptGenerator
participant FS as File System
User->>CLI: run doctor/export (--doctor)
CLI->>Exporter: export config files
Exporter-->>CLI: createdFiles + metadata (bundler)
CLI->>Prompt: generatePrompt(createdFiles, targetDir, bundler, includeRoRctx)
Prompt-->>CLI: "AI-ANALYSIS-PROMPT.md" (markdown content)
CLI->>FS: write "AI-ANALYSIS-PROMPT.md" to disk
FS-->>CLI: path
CLI-->>User: summary (created files, Configuration Files:, AI Analysis:)
Estimated code review effort🎯 4 (Complex) | ⏱️ ~60 minutes Possibly related PRs
Suggested reviewers
Poem
Pre-merge checks and finishing touches✅ Passed checks (3 passed)
✨ Finishing touches
🧪 Generate unit tests (beta)
📜 Recent review detailsConfiguration used: CodeRabbit UI Review profile: CHILL Plan: Pro 📒 Files selected for processing (1)
🧰 Additional context used📓 Path-based instructions (1)**/*📄 CodeRabbit inference engine (CLAUDE.md)
Files:
🧬 Code graph analysis (1)package/configExporter/aiPromptGenerator.ts (2)
⏰ Context from checks skipped due to timeout of 90000ms. You can increase the timeout in your CodeRabbit configuration to a maximum of 15 minutes (900000ms). (12)
🔇 Additional comments (2)
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 |
Pull Request Review: AI Analysis Prompt GeneratorSummaryThis PR adds a helpful AI analysis prompt generator to the config exporter's --doctor mode. The implementation is well-structured and thoroughly tested. Overall, this is a solid contribution that adds value to the troubleshooting workflow. StrengthsCode Quality
Implementation Details
Documentation
|
Issues and Recommendations1. CRITICAL: Missing Trailing NewlineFile: package/configExporter/aiPromptGenerator.ts:277 The file is missing a trailing newline after line 276. According to CLAUDE.md line 5, this is required by the project's linting rules. Fix: Add a newline after line 276 2. index.d.ts Changes Appear UnrelatedFile: package/index.d.ts The changes to this file seem to be a complete rewrite unrelated to the AI prompt feature:
Questions: Were these changes intentional? If unrelated, they should be reverted or split into a separate PR. 3. Minor: Unused ImportFile: package/configExporter/aiPromptGenerator.ts:2 The ConfigMetadata type is imported but never used. This will cause linting warnings. Fix: Remove the unused import |
4. Enhancement: Type Safety for Bundler ParameterFile: package/configExporter/aiPromptGenerator.ts:18-22 The bundler parameter is typed as string, but should be "webpack" | "rspack" for better type safety. 5. Code Style: String ConcatenationFile: package/configExporter/aiPromptGenerator.ts:157-161 Multi-line string concatenation could be cleaner by joining the two sections.push() calls into one. 6. Testing: Consider Edge CasesFile: test/package/configExporter/aiPromptGenerator.test.js The tests are comprehensive, but consider adding tests for:
|
Security, Performance, and TestingSecurity ReviewNo security concerns identified:
Performance ConsiderationsNo performance concerns:
Test Coverage AssessmentCoverage: Excellent The test suite covers:
Missing coverage (nice-to-have):
|
Checklist Before Merge
Final RecommendationApprove with minor changes This is a valuable feature that enhances the troubleshooting workflow. The code is well-written and well-tested. Once the critical trailing newline issue is fixed and the index.d.ts changes are clarified, this PR will be ready to merge. The AI prompt generation is a creative solution to help users get assistance with configuration issues, and the implementation is solid. Suggestions for Future Enhancement
Great work on this feature! |
PR Review: AI Analysis Prompt GeneratorOverviewThis PR adds an excellent new feature that generates AI analysis prompts for webpack/rspack configurations. The implementation is clean, well-tested, and provides real value for debugging and optimization workflows. ✅ Code Quality & Best PracticesStrengths:
Minor Suggestions:
🐛 Potential Bugs & IssuesIssues Found:
Minor Issues:
⚡ Performance ConsiderationsGood:
No concerns - Performance impact is minimal, only adds a small file write operation. 🔒 Security ConcernsAnalysis:
Verdict: No security concerns identified. The PR description's claim of "no security implications" is accurate. 🧪 Test CoverageStrengths:
Suggestions for improvement:
📋 Additional Recommendations
🎯 SummaryOverall Assessment: ✅ Approved with minor suggestions This is a high-quality PR that adds valuable functionality for users debugging webpack/rspack configurations. The implementation is clean, well-tested, and follows project conventions. Key Points:
Recommended Actions Before Merge:
Great work on this feature! 🎉 The AI prompt will be genuinely useful for users troubleshooting configuration issues. Review generated with Claude Code |
Include direct links to React on Rails example configuration files in the AI analysis prompt. This provides AI assistants with reference implementations to compare against when analyzing user configurations. Added links to: - commonWebpackConfig.js - clientWebpackConfig.js - serverWebpackConfig.js - webpack.config.js These examples demonstrate React on Rails best practices for webpack/rspack configuration including proper client/server bundle separation and SSR setup. Changes: - Add 'Reference Configuration Examples' subsection to AI prompt - Include GitHub links to React on Rails dummy app configs - Update test to verify reference links are included
![coderabbitai[bot]](https://avatars.githubusercontent.com/in/347564?s=60&v=4){kind=small}
There was a problem hiding this comment.
Actionable comments posted: 1
🧹 Nitpick comments (2)
package/configExporter/aiPromptGenerator.ts (1)
54-54: Reuse a single timestamp for consistency.We call
new Date().toISOString()twice, which can produce slightly different values in the same prompt. Capture it once and reuse so headers stay aligned.- sections.push(`- **Exported At**: ${new Date().toISOString()}`) + const timestamp = new Date().toISOString() + sections.push(`- **Exported At**: ${timestamp}`) ... - sections.push(`**Date**: ${new Date().toISOString()}`) + sections.push(`**Date**: ${timestamp}`)Also applies to: 264-264
test/package/configExporter/aiPromptGenerator.test.js (1)
10-186: Consider adding error handling tests and reducing test brittleness.The test coverage is solid for happy paths, but could be enhanced:
- Error handling: Add tests for edge cases like empty
exportedFilesarrays, null/undefined parameters, or invalid bundler names.- String brittleness: Tests rely heavily on exact string matching. If the prompt wording changes slightly, many tests could fail. Consider testing for structure/presence of key elements rather than exact strings where appropriate.
- Test duplication: Several tests have similar setup code. Consider using
test.eachfor bundler-specific tests or extracting common setup into helper functions.Example refactor using
test.each:test.each([ ['webpack'], ['rspack'] ])('generatePrompt includes all sections for %s', (bundler) => { const exportedFiles = [ `${bundler}-development-client.yaml`, `${bundler}-development-server.yaml`, `${bundler}-production-client.yaml`, `${bundler}-production-server.yaml` ] const prompt = generator.generatePrompt(exportedFiles, '/path/to/exports', bundler) expect(prompt).toContain(`**Bundler**: ${bundler}`) expect(prompt).toContain('# AI Configuration Analysis Request') // ... other assertions })
📜 Review details
Configuration used: CodeRabbit UI
Review profile: CHILL
Plan: Pro
📒 Files selected for processing (6)
docs/troubleshooting.md(1 hunks)package/configExporter/aiPromptGenerator.ts(1 hunks)package/configExporter/cli.ts(3 hunks)package/configExporter/index.ts(1 hunks)package/index.d.ts(1 hunks)test/package/configExporter/aiPromptGenerator.test.js(1 hunks)
🧰 Additional context used
📓 Path-based instructions (1)
**/*
📄 CodeRabbit inference engine (CLAUDE.md)
End every file with a trailing newline character
Files:
package/index.d.tstest/package/configExporter/aiPromptGenerator.test.jspackage/configExporter/index.tspackage/configExporter/cli.tsdocs/troubleshooting.mdpackage/configExporter/aiPromptGenerator.ts
🧬 Code graph analysis (4)
package/index.d.ts (1)
package/types/index.ts (1)
Configuration(58-58)
test/package/configExporter/aiPromptGenerator.test.js (2)
package/configExporter/aiPromptGenerator.ts (1)
AiPromptGenerator(8-276)package/configExporter/index.ts (1)
AiPromptGenerator(5-5)
package/configExporter/cli.ts (2)
package/configExporter/aiPromptGenerator.ts (1)
AiPromptGenerator(8-276)package/configExporter/index.ts (1)
AiPromptGenerator(5-5)
package/configExporter/aiPromptGenerator.ts (2)
package/configExporter/index.ts (1)
AiPromptGenerator(5-5)lib/shakapacker/configuration.rb (1)
bundler(108-110)
⏰ Context from checks skipped due to timeout of 90000ms. You can increase the timeout in your CodeRabbit configuration to a maximum of 15 minutes (900000ms). (9)
- GitHub Check: Testing (ubuntu-latest, 22.x)
- GitHub Check: Testing (ubuntu-latest, 20.x)
- GitHub Check: test
- GitHub Check: Generator specs (ubuntu-latest, 3.1, gemfiles/Gemfile-rails.7.1.x)
- GitHub Check: Generator specs (ubuntu-latest, 2.7, gemfiles/Gemfile-rails.7.0.x)
- GitHub Check: Test Bundler Switching
- GitHub Check: Testing (ubuntu-latest, 3.3, gemfiles/Gemfile-rails.7.1.x)
- GitHub Check: Testing (ubuntu-latest, 3.3, gemfiles/Gemfile-rails.7.0.x)
- GitHub Check: claude-review
🔇 Additional comments (1)
test/package/configExporter/aiPromptGenerator.test.js (1)
1-8: LGTM!The import and test setup are correct. The use of
beforeEachensures proper test isolation by creating a fresh generator instance for each test.
| expect(prompt).toContain("**Bundler**: webpack") | ||
| expect(prompt).toMatch(/\*\*Date\*\*: \d{4}-\d{2}-\d{2}T/) | ||
| }) | ||
| }) |
There was a problem hiding this comment.
Add trailing newline to comply with coding guidelines.
The file must end with a trailing newline character.
Apply this diff:
expect(prompt).toMatch(/\*\*Date\*\*: \d{4}-\d{2}-\d{2}T/)
})
})
+Based on coding guidelines.
📝 Committable suggestion
‼️ IMPORTANT
Carefully review the code before committing. Ensure that it accurately replaces the highlighted code, contains no missing lines, and has no issues with indentation. Thoroughly test & benchmark the code to ensure it meets the requirements.
| }) | |
| expect(prompt).toMatch(/\*\*Date\*\*: \d{4}-\d{2}-\d{2}T/) | |
| }) | |
| }) | |
🤖 Prompt for AI Agents
In test/package/configExporter/aiPromptGenerator.test.js around line 186, the
file is missing a trailing newline; add a single newline character at the end of
the file (ensure the final line ends with '\n'), save and commit so the file
ends with a trailing newline to comply with coding guidelines.
Pull Request Review: AI Analysis Prompt GeneratorI've completed a comprehensive review of PR #695. Overall, this is a well-implemented feature that adds significant value to the troubleshooting workflow. Here are my findings: ✅ StrengthsCode Quality
Implementation
|
Code Review: AI Analysis Prompt GeneratorI have completed a thorough review of PR #695. Overall, this is a well-designed and valuable addition to the config exporter that will help users get intelligent configuration analysis. StrengthsCode Quality
User Experience
Best Practices
Areas for Improvement1. Minor: File ending newline (aiPromptGenerator.ts:299)According to the project CLAUDE.md guidelines, all files must end with a trailing newline. The file currently ends at line 299 without a trailing newline. 2. Minor: Type definition changes (index.d.ts)The type definitions were significantly refactored in this PR. The PR description mentions TypeScript declarations consolidated but could use more context about why this change was made. 3. Enhancement: Consider input validationThe bundler parameter is directly interpolated into the prompt. While currently safe, consider documenting expected values or adding validation. 4. Test coverage: Missing edge caseCould add test for empty exportedFiles array. Recommendations by PriorityHigh Priority
Medium Priority
Security AssessmentNo security concerns identified:
Performance ConsiderationsMinimal performance impact:
Test CoverageExcellent test coverage with 11 tests covering all major functionality Overall AssessmentRecommendation: APPROVE with minor fixes This PR adds significant value to the shakapacker ecosystem by making configuration troubleshooting more accessible through AI assistance. The implementation is clean, well-tested, and follows good software engineering practices. Action Items Before Merge:
Great work on this feature! |
There was a problem hiding this comment.
Actionable comments posted: 1
🧹 Nitpick comments (2)
package/configExporter/aiPromptGenerator.ts (2)
54-54: Extract timestamp to avoid inconsistency.The timestamp is generated twice using
new Date().toISOString()(lines 54 and 287). While unlikely, these calls could produce different values if execution crosses a millisecond boundary. Extract the timestamp to a constant at the beginning of the method to ensure consistency.Apply this diff:
): string { + const timestamp = new Date().toISOString() + const clientDevFile = exportedFiles.find((f) => f.includes("development-client") )Then update both usages:
sections.push(`- **Bundler**: ${bundler}`) - sections.push(`- **Exported At**: ${new Date().toISOString()}`) + sections.push(`- **Exported At**: ${timestamp}`) sections.push(`- **Export Directory**: ${targetDir}`)sections.push("**Generated by Shakapacker Config Exporter**") sections.push(`**Bundler**: ${bundler}`) - sections.push(`**Date**: ${new Date().toISOString()}`) + sections.push(`**Date**: ${timestamp}`) sections.push("")Also applies to: 287-287
128-138: Hardcoded GitHub URLs are valid; consider pinning to a release tag
All links return HTTP 200 and the default branch ismaster, but they may break if the branch or paths change. For long-term stability, link to a specific version tag (e.g., a release) instead ofmaster.
📜 Review details
Configuration used: CodeRabbit UI
Review profile: CHILL
Plan: Pro
📒 Files selected for processing (2)
package/configExporter/aiPromptGenerator.ts(1 hunks)test/package/configExporter/aiPromptGenerator.test.js(1 hunks)
🚧 Files skipped from review as they are similar to previous changes (1)
- test/package/configExporter/aiPromptGenerator.test.js
🧰 Additional context used
📓 Path-based instructions (1)
**/*
📄 CodeRabbit inference engine (CLAUDE.md)
End every file with a trailing newline character
Files:
package/configExporter/aiPromptGenerator.ts
🧬 Code graph analysis (1)
package/configExporter/aiPromptGenerator.ts (2)
package/configExporter/index.ts (1)
AiPromptGenerator(5-5)lib/shakapacker/configuration.rb (1)
bundler(108-110)
⏰ Context from checks skipped due to timeout of 90000ms. You can increase the timeout in your CodeRabbit configuration to a maximum of 15 minutes (900000ms). (3)
- GitHub Check: Generator specs (ubuntu-latest, 3.2, gemfiles/Gemfile-rails.7.0.x)
- GitHub Check: Test Bundler Switching
- GitHub Check: claude-review
🔇 Additional comments (2)
package/configExporter/aiPromptGenerator.ts (2)
299-299: Ensure file ends with a trailing newline.Per the coding guidelines, all files must end with a trailing newline character. Please verify that this file ends with a newline after the closing brace.
As per coding guidelines.
8-291: Well-structured implementation!The
AiPromptGeneratorclass is well-designed with:
- Clear separation between metadata gathering and content generation
- Comprehensive coverage of analysis objectives (migration issues, build errors, optimizations)
- Conditional sections that adapt to context (React on Rails)
- Logical progression from high-level context to specific analysis requests
- Appropriate use of markdown formatting for readability
The prompt structure effectively guides AI assistants through the configuration analysis workflow.
| import { basename } from "path" | ||
| import { ConfigMetadata } from "./types" |
There was a problem hiding this comment.
🛠️ Refactor suggestion | 🟠 Major
Remove unused imports.
Neither basename nor ConfigMetadata are used in this file. Removing these unused imports will clean up the code and reduce confusion.
Apply this diff to remove the unused imports:
-import { basename } from "path"
-import { ConfigMetadata } from "./types"
-
/**
* Generates an AI prompt file for analyzing webpack/rspack configuration exports.
* The prompt helps AI identify issues and suggest optimizations for the bundler configuration.
*/
export class AiPromptGenerator {📝 Committable suggestion
‼️ IMPORTANT
Carefully review the code before committing. Ensure that it accurately replaces the highlighted code, contains no missing lines, and has no issues with indentation. Thoroughly test & benchmark the code to ensure it meets the requirements.
| import { basename } from "path" | |
| import { ConfigMetadata } from "./types" | |
| /** | |
| * Generates an AI prompt file for analyzing webpack/rspack configuration exports. | |
| * The prompt helps AI identify issues and suggest optimizations for the bundler configuration. | |
| */ | |
| export class AiPromptGenerator { |
🤖 Prompt for AI Agents
In package/configExporter/aiPromptGenerator.ts around lines 1 to 2, the imports
"basename" from path and "ConfigMetadata" from ./types are unused; remove those
two named imports from the file's import statements (delete the basename import
and the ConfigMetadata import) and run a quick grep/TS compile to ensure no
remaining references, leaving only actually used imports in this module.
Update AI prompt to mention upcoming exported reference configurations in YAML format. These will be generated via a rake task (tracked in react_on_rails#1862) that runs the generators and exports configs. This provides better context to users about: - Current reference: JavaScript source config files - Future reference: Exported YAML configs for direct comparison The YAML exports will make it easier for AI to compare configurations since they'll be in the same format as the user's exported configs. Changes: - Add 'Coming Soon' section for YAML reference configs - Link to react_on_rails#1862 tracking the rake task - Update test to verify issue link is included - Clarify distinction between source (JS) and exported (YAML) configs
Update AI prompt to specify that reference configurations will include 8 YAML files total: 4 for webpack and 4 for rspack, covering all development/production × client/server combinations. This aligns with the updated react_on_rails#1862 which now specifies generating configs for both bundlers to support migration scenarios. Changes: - Mention 8 total config files in the coming soon section - Clarify breakdown: 4 webpack + 4 rspack configurations - Makes it clear users will have reference configs for both bundlers
There was a problem hiding this comment.
Actionable comments posted: 0
♻️ Duplicate comments (1)
package/configExporter/aiPromptGenerator.ts (1)
1-2: Remove unused imports.Neither
basenamenorConfigMetadataare used in this file.Apply this diff to remove the unused imports:
-import { basename } from "path" -import { ConfigMetadata } from "./types" - /** * Generates an AI prompt file for analyzing webpack/rspack configuration exports. * The prompt helps AI identify issues and suggest optimizations for the bundler configuration. */ export class AiPromptGenerator {
🧹 Nitpick comments (1)
package/configExporter/aiPromptGenerator.ts (1)
18-314: Compute timestamp once for consistency.The method calls
new Date().toISOString()twice (lines 54 and 310). Computing it once ensures consistent timestamps throughout the generated prompt and avoids redundant computation.Apply this diff:
generatePrompt( exportedFiles: string[], targetDir: string, bundler: string, includeReactOnRailsContext = true ): string { + const timestamp = new Date().toISOString() + const clientDevFile = exportedFiles.find((f) => f.includes("development-client") ) const serverDevFile = exportedFiles.find((f) => f.includes("development-server") ) const clientProdFile = exportedFiles.find((f) => f.includes("production-client") ) const serverProdFile = exportedFiles.find((f) => f.includes("production-server") ) const sections: string[] = [] // Header sections.push("# AI Configuration Analysis Request") sections.push("") sections.push( `This directory contains exported ${bundler} configuration files for analysis.` ) sections.push( "Please analyze these configurations and provide recommendations." ) sections.push("") // Context section sections.push("## Context") sections.push("") sections.push(`- **Bundler**: ${bundler}`) - sections.push(`- **Exported At**: ${new Date().toISOString()}`) + sections.push(`- **Exported At**: ${timestamp}`) sections.push(`- **Export Directory**: ${targetDir}`)And at the footer:
// Footer sections.push("---") sections.push("") sections.push("**Generated by Shakapacker Config Exporter**") sections.push(`**Bundler**: ${bundler}`) - sections.push(`**Date**: ${new Date().toISOString()}`) + sections.push(`**Date**: ${timestamp}`) sections.push("") return sections.join("\n") }
📜 Review details
Configuration used: CodeRabbit UI
Review profile: CHILL
Plan: Pro
📒 Files selected for processing (1)
package/configExporter/aiPromptGenerator.ts(1 hunks)
🧰 Additional context used
📓 Path-based instructions (1)
**/*
📄 CodeRabbit inference engine (CLAUDE.md)
End every file with a trailing newline character
Files:
package/configExporter/aiPromptGenerator.ts
🧬 Code graph analysis (1)
package/configExporter/aiPromptGenerator.ts (2)
package/configExporter/index.ts (1)
AiPromptGenerator(5-5)lib/shakapacker/configuration.rb (1)
bundler(108-110)
⏰ Context from checks skipped due to timeout of 90000ms. You can increase the timeout in your CodeRabbit configuration to a maximum of 15 minutes (900000ms). (2)
- GitHub Check: test
- GitHub Check: claude-review
Update AI prompt to specify that reference configurations will include 10 YAML files total: 5 for webpack and 5 for rspack. The additional files are development client configs with HMR enabled, which capture the dev server configuration including: - Hot Module Replacement settings - Dev server configuration (port, host, HTTPS) - Live reload configuration - Proxy settings This aligns with updated react_on_rails#1862 which now includes HMR configs to help users troubleshoot dev server and hot reload issues. Changes: - Update from 8 to 10 total config files - List all 5 config types (dev client, dev client HMR, dev server, prod client, prod server) - Explain importance of HMR configs for dev server troubleshooting - Clarify that each bundler (webpack/rspack) gets all 5 variants
Code Review: AI Analysis Prompt GeneratorOverall AssessmentThis is a well-designed feature that adds significant value to the troubleshooting workflow. The code is clean, well-tested, and follows TypeScript best practices. I have identified a few minor issues and suggestions for improvement. ✅ Strengths
🐛 Potential Issues1. Missing Newline at End of aiPromptGenerator.ts (Critical)File: According to CLAUDE.md: "ALWAYS end all files with a trailing newline character. This is required by the project's linting rules." The new Fix: Add a newline after the closing brace on line 330. 2. Missing Newline in Test File (Critical)File: Same issue - the test file also needs a trailing newline after the final closing parenthesis. 3. Type Definition Changes Look SuspiciousFile: The changes to
Questions:
Recommendation: Either revert these changes or explain them in the PR description and ensure they are tested. 📝 Code Quality Suggestions1. Hardcoded Date FormattingFile: The code uses 2. Magic String for Markdown ExtensionFile: Consider checking against the actual prompt filename instead of using 3. Consider Adding Error HandlingFile: The AI prompt generation does not have try-catch error handling. If it fails, the entire doctor mode would fail. Consider wrapping in try-catch and continuing with other outputs. 🧪 Test CoverageOverall: Excellent test coverage with 11 test cases Suggestions:
🔒 Security & ⚡ PerformanceSecurity: No concerns - generates static markdown files only 🎯 SummaryThis is a solid PR with a useful feature. The main blockers are:
Once these are addressed, this will be ready to merge! Great work on creating a feature that will genuinely help users debug their configurations! 🚀 |
Summary
Adds automatic AI analysis prompt generation to the
bin/export-bundler-config --doctorcommand. This creates anAI-ANALYSIS-PROMPT.mdfile alongside exported configurations, providing comprehensive instructions for AI assistants to analyze webpack/rspack configs.Key Improvements
What's Included in the AI Prompt
The generated prompt instructs AI to analyze:
Example Output
When running
bin/export-bundler-config --doctor, you now get:Test Plan
AiPromptGenerator(11 tests)Breaking Changes
None - this is purely additive functionality.
Security Implications
None - generates documentation files only, no code execution or external dependencies.
Summary by CodeRabbit
New Features
CLI
Documentation
Refactor
Tests