feat: support quick init on fresh machines

[ChangeHow]

Summary

• add a non-interactive init flow and make install.sh bootstrap missing package-manager prerequisites so curl | bash works on fresh machines
• align generated zsh config with the shared ~/.config/zsh/shared/* layout for plugins, aliases, highlighting, and completion
• remove work-specific hints from shipped machine-local config and update tests to guard against sensitive or non-generic content

Verification

• npm test

[gemini-code-assist]

Summary of Changes

Hello, 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 enhances the user experience for new users by providing a streamlined, non-interactive initialization process. It also improves the robustness of the installation process by automatically handling missing prerequisites. The changes to the Zsh configuration ensure a consistent and maintainable setup, while removing work-specific hints promotes broader usability.

Highlights

• Non-Interactive Initialization: Introduces a non-interactive init flow, enabling quick setup with recommended defaults, streamlining the initial configuration process.
• Automated Prerequisite Installation: The install.sh script now bootstraps missing package manager prerequisites, allowing curl | bash to work seamlessly on fresh machines.
• Aligned Zsh Configuration: Generated Zsh configurations are now aligned with the shared ~/.config/zsh/shared/* layout, standardizing the structure for plugins, aliases, highlighting, and completion.
• Work-Specific Hint Removal: Removes work-specific hints from the shipped machine-local configuration, enhancing privacy and ensuring configurations are generic and reusable.

🧠 New Feature in Public Preview: You can now enable Memory to help Gemini Code Assist learn from your team's feedback. This makes future code reviews more consistent and personalized to your project's style. Click here to enable Memory in your admin console.

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.

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 a non-interactive init command and refactors the Zsh configuration structure, which is a great improvement for new machine setups. The install.sh script is now much more capable, attempting to bootstrap dependencies like Zsh and Node.js. The code changes are well-structured, and the test suite has been comprehensively updated to cover the new features. I've found a couple of areas for improvement: one in the install.sh script to make Node.js installation more reliable on Linux, and another to make a Git alias more robust.

[Copilot]

@ChangeHow I've opened a new pull request, #28, to work on those changes. Once the pull request is ready, I'll request review from you.