Skip to content

chore: ai week warming up phase 1#3316

Open
eduardoformiga wants to merge 5 commits into
devfrom
chore/ai-week
Open

chore: ai week warming up phase 1#3316
eduardoformiga wants to merge 5 commits into
devfrom
chore/ai-week

Conversation

@eduardoformiga

@eduardoformiga eduardoformiga commented May 12, 2026

Copy link
Copy Markdown
Member

What's the purpose of this pull request?

How it works?

How to test it?

Starters Deploy Preview

References

Checklist

You may erase this after checking them all 😉

PR Title and Commit Messages

  • PR title and commit messages follow the Conventional Commits specification
    • Available prefixes: feat, fix, chore, docs, style, refactor, ci and test

PR Description

  • Added a label according to the PR goal - breaking change, bug, contributing, performance, documentation..

Dependencies

  • Committed the pnpm-lock.yaml file when there were changes to the packages

Documentation

  • PR description
  • For documentation changes, ping @Mariana-Caetano to review and update (Or submit a doc request)

Summary by CodeRabbit

  • Chores
    • Created development environment configuration template with example values for Next.js settings, cache optimization, hostname configuration, and server credentials.
    • Updated environment configuration documentation with improved formatting, expanded section headings, and production safety warnings regarding secret management.

Review Change Stack

- Introduced a new .env.example file to serve as a template for local environment variables.
- Included instructions for copying to .env.local and guidelines for production settings.
- Updated vtex.env with improved documentation and organization for local development variables.
…pipeline details

- Added a section for the new diagnostics package for OpenTelemetry integration.
- Included detailed information on the build pipeline using Turbo, including task dependencies and caching behavior.
- Documented dual module output for library packages and bundle size budgets.
- Updated testing guidelines to reflect the use of Vitest for unit testing and accessibility checks.
- Introduced a new script `setup-claude.mjs` to create symlinks for skills, commands, and rules from the `.agents/` directory to the `.claude/` directory.
- Updated `.gitignore` to include `.claude` and added an exception for `packages/core/.env.example`.
- Added a new `.gitkeep` file in the `.agents/commands`, `.agents/rules`, and `.agents/skills` directories to maintain their structure.
- Reformatted import statements and console warning message for better alignment and consistency in the `setup-claude.mjs` script.
@eduardoformiga eduardoformiga requested a review from a team as a code owner May 12, 2026 22:47
@eduardoformiga eduardoformiga requested review from emersonlaurentino and lemagnetic and removed request for a team May 12, 2026 22:47
@coderabbitai

coderabbitai Bot commented May 12, 2026

Copy link
Copy Markdown
Contributor

Walkthrough

This PR adds a .env.example template for local development environment variables and reorganizes the vtex.env file's documentation with clearer sections, production warnings, and expanded guidance for Next.js telemetry, build caching, site hostname, and VTEX API credentials.

Changes

Environment Configuration

Layer / File(s) Summary
Environment setup and documentation
packages/core/.env.example, packages/core/vtex.env
.env.example is created as a new template documenting Next.js telemetry, build/cache behavior, site hostname, and VTEX credentials. vtex.env header and sections are reorganized with production/secrets warnings and improved readability while preserving existing variable values.

Estimated code review effort

🎯 1 (Trivial) | ⏱️ ~3 minutes

Suggested reviewers

  • emersonlaurentino
  • lemagnetic

Poem

📝 A template blooms, clear and bright,
Guiding devs through config's night,
Secrets safe, no leaks in sight,
Environment docs done right! 🎉

🚥 Pre-merge checks | ✅ 4 | ❌ 1

❌ Failed checks (1 inconclusive)

Check name Status Explanation Resolution
Title check ❓ Inconclusive The title "chore: ai week warming up phase 1" is vague and generic; it doesn't clearly describe the actual changes made (environment setup files, documentation, CI scripts). Use a more descriptive title that reflects the main changes, such as "chore: add environment setup templates and AI tooling scripts" or "chore: initialize developer environment and agent configuration".
✅ Passed checks (4 passed)
Check name Status Explanation
Description Check ✅ Passed Check skipped - CodeRabbit’s high-level summary is enabled.
Docstring Coverage ✅ Passed No functions found in the changed files to evaluate docstring coverage. Skipping docstring coverage check.
Linked Issues check ✅ Passed Check skipped because no linked issues were found for this pull request.
Out of Scope Changes check ✅ Passed Check skipped because no linked issues were found for this pull request.

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

✨ Finishing Touches
📝 Generate docstrings
  • Create stacked PR
  • Commit on current branch
🧪 Generate unit tests (beta)
  • Create PR with unit tests
  • Commit unit tests in branch chore/ai-week

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.

@codesandbox-ci

Copy link
Copy Markdown

This pull request is automatically built and testable in CodeSandbox.

To see build info of the built libraries, click here or the icon next to each commit SHA.

@coderabbitai coderabbitai Bot left a comment

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.

Actionable comments posted: 1

🤖 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 `@packages/core/.env.example`:
- Line 9: Update the copy instruction comment that currently reads "#   cp
.env.example .env.local" to a root-safe command or clarify the working
directory; for example, change it to "#   cp packages/core/.env.example
.env.local (run from repo root)" or add an explicit note like "Run from repo
root: cp packages/core/.env.example .env.local" so users running the command
from the repository root won't fail.
🪄 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: Path: .coderabbit.yaml

Review profile: CHILL

Plan: Pro

Run ID: 2d886a5c-1163-4756-b5ce-113356b9dee7

📥 Commits

Reviewing files that changed from the base of the PR and between 8baa617 and 39b75ee.

⛔ Files ignored due to path filters (8)
  • .agents/commands/.gitkeep is excluded by none and included by none
  • .agents/rules/.gitkeep is excluded by none and included by none
  • .agents/skills/.gitkeep is excluded by none and included by none
  • .editorconfig is excluded by none and included by none
  • .gitignore is excluded by none and included by none
  • AGENTS.md is excluded by none and included by none
  • package.json is excluded by none and included by none
  • scripts/setup-claude.mjs is excluded by none and included by none
📒 Files selected for processing (2)
  • packages/core/.env.example
  • packages/core/vtex.env

# Copy this file to `.env.local` (gitignored) and fill in real values for
# local development. Never commit real secrets to the repository.
#
# cp .env.example .env.local

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 | ⚡ Quick win

Clarify the copy command path to avoid setup confusion.

Line 9 assumes execution from packages/core. If run from repo root, it fails. Prefer a root-safe command or explicitly state the working directory.

Suggested edit
-#   cp .env.example .env.local
+#   cp packages/core/.env.example packages/core/.env.local
📝 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.

Suggested change
# cp .env.example .env.local
# cp packages/core/.env.example packages/core/.env.local
🤖 Prompt for 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.

In `@packages/core/.env.example` at line 9, Update the copy instruction comment
that currently reads "#   cp .env.example .env.local" to a root-safe command or
clarify the working directory; for example, change it to "#   cp
packages/core/.env.example .env.local (run from repo root)" or add an explicit
note like "Run from repo root: cp packages/core/.env.example .env.local" so
users running the command from the repository root won't fail.

@eduardoformiga eduardoformiga changed the title chore: ai week chore: ai week warming up phase 1 May 14, 2026
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