style: fix lint errors on main branch

[jbdevprimary]

Summary

• Organize imports in src/services/index.ts
• Fix unused variable in check-expo-compatibility.js

Small lint fix to allow CI to pass on other PRs.

🤖 Generated with Claude Code

[coderabbitai]

Warning

Rate limit exceeded

@jbdevprimary has exceeded the limit for the number of commits that can be reviewed per hour. Please wait 16 minutes and 23 seconds before requesting another review.

⌛ How to resolve this issue?

After the wait time has elapsed, a review can be triggered using the @coderabbitai review command as a PR comment. Alternatively, push new commits to this PR.

We recommend that you space out your commits to avoid hitting the rate limit.

🚦 How do rate limits work?

CodeRabbit enforces hourly rate limits for each developer per organization.

Our paid plans have higher rate limits than the trial, open-source and free plans. In all cases, we re-allow further reviews after a brief timeout.

Please see our FAQ for further information.

📥 Commits

Reviewing files that changed from the base of the PR and between ff80413 and 83ecebf.

📒 Files selected for processing (3)

• packages/core/src/git/GitService.ts
• scripts/check-expo-compatibility.js
• src/services/index.ts

---

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.}

[gemini-code-assist]

Summary of Changes

Hello @jbdevprimary, I'm Gemini Code Assist¹! I'm currently reviewing this pull request and will post my feedback shortly. In the meantime, here's a summary to help you and other reviewers quickly get up to speed!

This pull request focuses on resolving minor linting and formatting issues to ensure the continuous integration pipeline passes smoothly. The changes primarily involve organizing type exports, updating Node.js built-in module import paths, and refining code style in a script, all without introducing any functional modifications.

Highlights

• Linting Fixes: Addressed various linting issues across two files to ensure the continuous integration pipeline passes without errors.
• Import Organization: Reordered type exports in 'src/services/index.ts' for better organization, likely adhering to a specific linting rule for consistent ordering.
• Code Style Refinements: Applied minor formatting adjustments in 'scripts/check-expo-compatibility.js', including updating Node.js built-in module imports to use the 'node:' protocol and consolidating multi-line strings for improved readability.

Using Gemini Code Assist

The full guide for Gemini Code Assist can be found on our documentation page, here are some quick tips.

Invoking Gemini

You can request assistance from Gemini at any point by creating a comment using either /gemini <command> or @gemini-code-assist <command>. Below is a summary of the supported commands on the current page.

Feature	Command	Description
Code Review	/gemini review	Performs a code review for the current pull request in its current state.
Pull Request Summary	/gemini summary	Provides a summary of the current pull request in its current state.
Comment	@gemini-code-assist	Responds in comments when explicitly tagged, both in pull request comments and review comments.
Help	/gemini help	Displays a list of available commands.

Customization

To customize Gemini Code Assist for GitHub experience, repository maintainers can create a configuration file and/or provide a custom code review style guide (such as PEP-8 for Python) by creating and adding files to a .gemini/ folder in the base of the repository. Detailed instructions can be found here.

Limitations & Feedback

Gemini Code Assist may make mistakes. Please leave feedback on any instances where its feedback is incorrect or counter productive. You can react with 👍 and 👎 on @gemini-code-assist comments. If you're interested in giving your feedback about your experience with Gemini Code Assist for Github and other Google products, sign up here.

You can also get AI-powered code generation, chat, as well as code reviews directly in the IDE at no cost with the Gemini Code Assist IDE Extension.

Footnotes

1. Review the Privacy Notices, Generative AI Prohibited Use Policy, Terms of Service, and learn how to configure Gemini Code Assist in GitHub here. Gemini can make mistakes, so double check it and use code with caution. ↩

[gemini-code-assist]

Code Review

This pull request introduces minor but valuable lint fixes across the codebase. The changes include organizing imports in src/services/index.ts for better readability and updating module imports in scripts/check-expo-compatibility.js to use the node: prefix, which is a modern best practice for clarity. Several formatting adjustments are also included, contributing to a more consistent code style. Overall, these changes are positive, improve code quality, and I approve of them.

[github-actions]

🚀 Expo preview is ready!

• Project → thumbcode
• Platforms → android, ios
• Scheme → thumbcode
• Runtime Version → 0.1.0
• More info

Learn more about 𝝠 Expo Github Action

[sonarqubecloud]

Quality Gate passed

Issues
0 New issues
0 Accepted issues

Measures
0 Security Hotspots
0.0% Coverage on New Code
0.0% Duplication on New Code

See analysis details on SonarQube Cloud