Skip to content

feat(install): prompt for setup mode and run p10k configure after init#30

Merged
ChangeHow merged 2 commits intomainfrom
feat/install-mode-prompt
Mar 24, 2026
Merged

feat(install): prompt for setup mode and run p10k configure after init#30
ChangeHow merged 2 commits intomainfrom
feat/install-mode-prompt

Conversation

@ChangeHow
Copy link
Owner

Summary

  • install.sh now asks the user to choose between setup (interactive, pick each step) and init (non-interactive, recommended defaults) when invoked without arguments; passing a command directly still bypasses the prompt
  • init mode now runs p10k configure at the end so users get their prompt theme set up immediately
  • AGENTS.md: added Documentation Sync — REQUIRED section enforcing that README.md and README.zh-CN.md must always be updated together
  • README.md + README.zh-CN.md: updated curl install behavior description and init feature list to reflect both changes above

Testing

All 189 tests pass (npm test).

- Split monolithic tools.zsh + fzf.zsh into shared/tools/ modules
  (_loader.zsh, fzf.zsh, runtime.zsh, atuin.zsh, bun.zsh)
- Add path-aware Ctrl-T widget in fzf.zsh
- Add version-based cache invalidation in _loader.zsh
- Widen perf.zsh timing table and add completion cache status line
- Update gphu alias to use git branch --show-current
- Migrate vim config and backups from ~/.config/suitup/ to ~/.config/zsh/
- Update src/steps, verify, clean, setup detection accordingly
- Sync all tests and update AGENTS.md + README.md
- install.sh asks user to choose setup (interactive) or init (defaults)
  when no command is passed; direct args still bypass the prompt
- init mode runs `p10k configure` after all steps complete
- AGENTS.md: add Documentation Sync — REQUIRED section
- README.md + README.zh-CN.md: sync curl behavior and init description
@ChangeHow ChangeHow merged commit 68c73f2 into main Mar 24, 2026
1 check passed
@gemini-code-assist
Copy link

Summary of Changes

Hello, I'm Gemini Code Assist1! 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 significantly refines the installation and configuration process by introducing a more guided and user-friendly installer prompt, alongside automating key post-installation steps like Powerlevel10k setup. It also brings a substantial internal refactoring of tool configurations into a modular, version-aware system, improving the overall maintainability and robustness of the Zsh environment. Comprehensive documentation updates ensure that all changes are clearly communicated and consistent across different language versions.

Highlights

  • Enhanced Installation Experience: The install.sh script now interactively prompts users to choose between setup (interactive, step-by-step) and init (non-interactive, recommended defaults) modes when invoked without arguments, improving user control and clarity during installation.
  • Automated Powerlevel10k Configuration: The init installation mode now automatically runs p10k configure at the end, ensuring that users get their prompt theme set up immediately without manual intervention.
  • Modular Tool Configuration: The Zsh tool configuration has been refactored into a modular structure under configs/shared/tools/, with a new orchestrator (tools.zsh) and individual files for each tool (e.g., fzf.zsh, atuin.zsh, bun.zsh), enhancing organization and maintainability.
  • Version-Based Cache Invalidation for Tool Init: A new _loader.zsh script introduces version-based cache invalidation for tool initialization scripts, ensuring that cached outputs from CLIs like fzf and atuin are rebuilt when the tool's version changes.
  • Documentation Synchronization Policy: A new required policy has been added to AGENTS.md enforcing that README.md and README.zh-CN.md must always be updated together in the same commit when user-facing content changes, ensuring consistency across languages.
  • Standardized Backup Paths: All backup paths and references to configuration directories have been standardized to ~/.config/zsh/backups/ and ~/.config/zsh/ respectively, removing older ~/.config/suitup/ references for a cleaner structure.

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

Copy link

@gemini-code-assist gemini-code-assist bot left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Code Review

This pull request introduces a significant refactoring of the Zsh tool configuration, moving from a single tools.zsh file to a modular structure with dedicated files for each tool (e.g., fzf, atuin, bun, runtime) and a centralized _loader.zsh for caching and loading logic. All configuration files are now consolidated under ~/.config/zsh/, removing the ~/.config/suitup/ directory. The install.sh script has been enhanced to offer an interactive choice between setup and init modes, and the init mode now automatically configures Powerlevel10k if needed. Documentation in both English and Chinese has been updated to reflect these changes, including a new guideline for documentation synchronization. The gphu alias was updated to use git branch --show-current. The only feedback is a suggestion to use Chinese full-width quotation marks for better typographical consistency in the Chinese README.


- 若存在备份,优先恢复最近一次非 suitup 版本的 `~/.zshrc` / `~/.zshenv`
- 对仍与项目模板一致的文件,删除 `~/.config/zsh/` 与 `~/.config/suitup/` 下的 suitup 生成内容
- 若存在备份,优先恢复最近一次"非 suitup 版本"的 `~/.zshrc` / `~/.zshenv`

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

medium

For consistency with the typography used elsewhere in this document, it is recommended to use Chinese full-width quotation marks (“”) instead of English double quotes ("").

Suggested change
- 若存在备份,优先恢复最近一次"非 suitup 版本"`~/.zshrc` / `~/.zshenv`
- 若存在备份,优先恢复最近一次非 suitup 版本`~/.zshrc` / `~/.zshenv`

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