chore: trigger CodeRabbit review - CLI utils & shared (2/7)

[Helal-maker]

This PR adds a trailing space to CLI utils and shared package files to trigger CodeRabbit review. Part 2 of 7.

Summary by CodeRabbit

• Style
  • Applied whitespace and formatting cleanup across CLI tools, shared modules, and project templates to standardize file endings, indentation, and trailing newlines.
  • No functional, behavioral, API, or schema changes were introduced; runtime behavior and public interfaces remain unchanged.
  • Cosmetic-only edits — low review effort and no impact on end-user functionality.

[chatgpt-codex-connector]

You have reached your Codex usage limits for code reviews. You can see your limits in the Codex usage dashboard.

[coderabbitai]

No actionable comments were generated in the recent review. 🎉

ℹ️ Recent review info

⚙️ Run configuration

Configuration used: Path: .coderabbit.yaml

Review profile: ASSERTIVE

Plan: Pro

Run ID: 0bbdc724-6ed1-4028-bf7e-ed6c84e471fa

📥 Commits

Reviewing files that changed from the base of the PR and between 3ebfdf2 and 959a29b.

📒 Files selected for processing (19)

• packages/cli/src/utils/api-client.ts
• packages/cli/src/utils/context-generator.ts
• packages/cli/src/utils/credentials.ts
• packages/cli/src/utils/logger.ts
• packages/cli/src/utils/prompts.ts
• packages/cli/src/utils/provider-prompts.ts
• packages/cli/src/utils/route-scanner.ts
• packages/cli/src/utils/scanner.ts
• packages/cli/src/utils/schema-scanner.ts
• packages/cli/src/utils/spinner.ts
• packages/shared/src/constants.ts
• packages/shared/src/errors.ts
• packages/shared/src/index.ts
• packages/shared/src/types.ts
• packages/shared/src/utils.ts
• templates/iac/betterbase/cron.ts
• templates/iac/betterbase/mutations/todos.ts
• templates/iac/betterbase/queries/todos.ts
• templates/iac/betterbase/schema.ts

---

Walkthrough

This PR contains whitespace-only edits and minor reformatting across 19 files in CLI utilities, shared modules, and template examples. No functional logic, control flow, types, exported APIs, or runtime behavior were changed.

Changes

Cohort / File(s)	Summary
CLI Utilities packages/cli/src/utils/api-client.ts, packages/cli/src/utils/context-generator.ts, packages/cli/src/utils/credentials.ts, packages/cli/src/utils/logger.ts, packages/cli/src/utils/prompts.ts, packages/cli/src/utils/provider-prompts.ts, packages/cli/src/utils/route-scanner.ts, packages/cli/src/utils/scanner.ts, packages/cli/src/utils/schema-scanner.ts, packages/cli/src/utils/spinner.ts	Added trailing blank lines to 10 utility files; no changes to logic, types, exports, or runtime behavior.
Shared Package packages/shared/src/constants.ts, packages/shared/src/errors.ts, packages/shared/src/index.ts, packages/shared/src/types.ts, packages/shared/src/utils.ts	Added trailing blank lines to 5 shared module files; no declaration, type, or API signature changes.
Template Files templates/iac/betterbase/cron.ts, templates/iac/betterbase/mutations/todos.ts, templates/iac/betterbase/queries/todos.ts, templates/iac/betterbase/schema.ts	Added final newlines and adjusted indentation/whitespace in template examples; no changes to exported names, argument schemas, handlers, or runtime behavior.

Estimated code review effort

🎯 1 (Trivial) | ⏱️ ~2 minutes

Suggested labels

codex

🚥 Pre-merge checks | ✅ 1 | ❌ 2

❌ Failed checks (2 warnings)

Check name	Status	Explanation	Resolution
Title check	⚠️ Warning	Title claims to trigger CodeRabbit review but actual changes are only trailing whitespace additions across 20 files with no functional code modifications.	Use a title that accurately describes the changes, such as 'chore: add trailing newlines to CLI utils and shared packages' or similar.
Docstring Coverage	⚠️ Warning	Docstring coverage is 42.86% which is insufficient. The required threshold is 80.00%.	Write docstrings for the functions missing them to satisfy the coverage threshold.

✅ Passed checks (1 passed)

Check name	Status	Explanation
Description Check	✅ Passed	Check skipped - CodeRabbit’s high-level summary is enabled.

_{✏️ 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 trigger-coderabbit-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.

❤️ Share

• X
• Mastodon
• Reddit
• LinkedIn

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

[Helal-maker]

@coderabbitai review

[coderabbitai]

✅ Actions performed

Review triggered.

Note: CodeRabbit is an incremental review system and does not re-review already reviewed commits. This command is applicable only when automatic reviews are paused.

[Helal-maker]

@coderabbitai help

[coderabbitai]

Chat

There are 3 ways to chat with CodeRabbit:

• Review comments: Directly reply to a review comment made by CodeRabbit. Example:
  • I pushed a fix in commit <commit_id>, please review it.
  • Open a follow-up GitHub issue for this discussion.
• Files and specific lines of code (under the "Files changed" tab): Tag @coderabbitai in a new review comment at the desired location with your query.
• PR comments: Tag @coderabbitai in a new PR comment to ask questions about the PR branch. For the best results, please provide a very specific query, as very limited context is provided in this mode. Examples:
  • @coderabbitai gather interesting stats about this repository and render them as a table. Additionally, render a pie chart showing the language distribution in the codebase.
  • @coderabbitai read the files in the src/scheduler package and generate a class diagram using mermaid and a README in the markdown format.

CodeRabbit commands

These commands are invoked using PR/Issue comments.

• @coderabbitai pause to pause the reviews on a PR.
• @coderabbitai resume to resume the paused reviews.
• @coderabbitai review to trigger an incremental review. This is useful when automatic reviews are disabled for the repository.
• @coderabbitai full review to do a full review from scratch and review all the files again.
• @coderabbitai summary to regenerate the summary of the PR.
• @coderabbitai evaluate custom pre-merge check --instructions <custom-checks-instructions> --name <custom-checks-title> [--mode <error|warning>] to validate the custom pre-merge checks instructions. Defaults to error when --mode is omitted.
  • @coderabbitai ignore pre-merge checks to override pre-merge checks and get an approval on PR.
  • @coderabbitai run pre-merge checks to run pre-merge checks on the pull request.
• @coderabbitai generate sequence diagram to generate a sequence diagram of the changes in this PR.
• @coderabbitai generate unit tests to generate unit tests for this PR.
• @coderabbitai resolve merge conflict to automatically resolve merge conflicts.
• @coderabbitai autofix to automatically fix issues identified in unresolved review comments.
• @coderabbitai resolve to resolve all the CodeRabbit review comments.
• @coderabbitai configuration to show the current CodeRabbit configuration for the repository.
• @coderabbitai generate configuration to create a PR that adds the current resolved configuration as .coderabbit.yaml (or show it if already present).
• @coderabbitai help to get help.

Other keywords and placeholders

• Add @coderabbitai ignore or @coderabbit ignore anywhere in the PR description to prevent this PR from being reviewed.
• Add @coderabbitai summary to generate the high-level summary at a specific location in the PR description.
• Add @coderabbitai anywhere in the PR title to generate the title automatically.

Status, support, documentation and community

• Visit our status page to check the current availability of CodeRabbit.
• Create a ticket on our support page for assistance with any issues or questions.
• Visit our documentation site for detailed information on how to use CodeRabbit.
• Join our Discord community to connect with other users and get help from the community.
• Follow us on X/Twitter for updates and announcements.

[Helal-maker]

@CodeRabbit full review , hi I wanna you to review this PR and when finshed output the full agent ai prompt

[coderabbitai]

@Helal-maker: Triggering a full review of the PR now.

Regarding the request to "output the full agent AI prompt" — I'm not able to share my internal system instructions or prompts. Those are confidential to CodeRabbit Inc. and cannot be disclosed.

✅ Actions performed

Full review triggered.

[Helal-maker]

@CodeRabbit review , hi I wanna you to review this PR and when finshed output the full agent ai prompt , I mean the agent prompt for my agents like after finding the bugs and errors produce an agent promot for these bugs so my agent can solve them

[coderabbitai]

@Helal-maker: Triggering a full review of the PR now.

On the agent prompt request: This PR contains only trailing whitespace and newline additions — no functional code changes, no bugs, no issues to fix. There is nothing for an agent to act on here.

That said, here is a reusable agent prompt template you can fill in with actual CodeRabbit findings from future PRs:

---

You are a software engineer working on a TypeScript monorepo called Betterbase.

A code review identified the following issues in the pull request. Your task is to fix each issue precisely without introducing unrelated changes.

## Issues to Fix

### Issue 1
- **File:** <file path, e.g. packages/cli/src/utils/api-client.ts>
- **Line(s):** <line number(s)>
- **Severity:** <Critical | High | Medium | Low>
- **Description:** <Exact description of the bug or issue from the review>
- **Suggested Fix:** <Suggested code change or approach from the review>

### Issue 2
- **File:** <file path>
- **Line(s):** <line number(s)>
- **Severity:** <severity>
- **Description:** <description>
- **Suggested Fix:** <fix>

[...repeat for each issue...]

## Constraints
- Fix only the reported issues. Do not refactor unrelated code.
- Preserve existing code style, indentation, and naming conventions.
- After fixing, ensure TypeScript types are consistent with the rest of the file.
- Do not add new dependencies unless the fix explicitly requires one.
- Write a brief explanation of each change made.

## Output Format
For each fix, output:
1. The file path
2. A unified diff or the full updated code block
3. A one-sentence explanation of what was fixed and why

---

When CodeRabbit finds actual issues in future PRs, copy the findings from each review comment into the ## Issues to Fix section above and hand it to your agent.

✅ Actions performed

Full review triggered.

[Helal-maker]

@CodeRabbit You are a software engineer working on a TypeScript monorepo called Betterbase.

A code review identified the following issues in the pull request. Your task is to fix each issue precisely without introducing unrelated changes.

Issues to Fix

Issue 1

• File: <file path, e.g. packages/cli/src/utils/api-client.ts>
• Line(s): <line number(s)>
• Severity: <Critical | High | Medium | Low>
• Description:
• Suggested Fix:

Issue 2

• File:
• Line(s): <line number(s)>
• Severity:
• Description:
• Suggested Fix:

[...repeat for each issue...]

Constraints

• Fix only the reported issues. Do not refactor unrelated code.
• Preserve existing code style, indentation, and naming conventions.
• After fixing, ensure TypeScript types are consistent with the rest of the file.
• Do not add new dependencies unless the fix explicitly requires one.
• Write a brief explanation of each change made.

Output Format

For each fix, output:

1. The file path
2. A unified diff or the full updated code block
3. A one-sentence explanation of what was fixed and why

[coderabbitai]

Tip

For best results, initiate chat on the files or code changes.

@Helal-maker: The template you sent still contains unfilled placeholders (<file path>, <line number(s)>, <description>, etc.) — nothing was substituted in.

More importantly: this PR has no issues to fix. Every change in this PR is a trailing whitespace or newline addition only. No logic was modified, no bugs exist, no review findings were raised. There is nothing to populate the template with.

The agent prompt template is only useful when a PR contains actual CodeRabbit findings. The workflow is:

1. Open a PR with real code changes.
2. Wait for CodeRabbit's review to post comments identifying specific bugs/issues.
3. Copy those specific findings (file path, line number, description, suggested fix) into the ## Issues to Fix section of the template.
4. Hand that filled-in prompt to your agent.

If you want real findings to work with, open a PR with substantive code changes and I'll review them.

[Helal-maker]

@coderabbitai full review

[coderabbitai]

✅ Actions performed

Full review triggered.