Skip to content

Conversation

@ryoppippi
Copy link
Owner

@ryoppippi ryoppippi commented Aug 17, 2025

Summary by CodeRabbit

  • Chores
    • Switched to local Git hooks for project setup.
    • Added pre-commit linting to improve code quality during development.
    • Removed an unused development dependency and related configuration.
    • No user-facing changes.

@ryoppippi ryoppippi merged commit 50cc926 into main Aug 17, 2025
12 of 13 checks passed
@coderabbitai
Copy link

coderabbitai bot commented Aug 17, 2025

Caution

Review failed

The pull request is closed.

Walkthrough

Introduces a local Git hooks path via package.json prepare script and adds a pre-commit hook at .githooks/pre-commit that runs lint-staged using npx. Removes simple-git-hooks dependency and related configuration from package.json.

Changes

Cohort / File(s) Summary of Changes
Git hooks setup
package.json, .githooks/pre-commit
Configure Git to use .githooks via prepare script (git config --local core.hooksPath .githooks). Add executable pre-commit hook running npx --no-install lint-staged.
Dependency and config cleanup
package.json
Remove simple-git-hooks from devDependencies, delete simple-git-hooks config block (pre-commit, pre-push), and remove trustedDependencies entry referencing it.

Sequence Diagram(s)

sequenceDiagram
    actor Dev as Developer
    participant Git as Git
    participant Hook as .githooks/pre-commit
    participant NPX as npx
    participant LS as lint-staged

    Dev->>Git: git commit
    Git->>Hook: run pre-commit
    Hook->>NPX: npx --no-install lint-staged
    NPX->>LS: execute
    LS-->>NPX: exit code
    NPX-->>Hook: exit code
    alt success (0)
        Hook-->>Git: success
        Git-->>Dev: commit proceeds
    else failure (!=0)
        Hook-->>Git: non-zero exit
        Git-->>Dev: commit aborted
    end
Loading

Estimated code review effort

🎯 2 (Simple) | ⏱️ ~10 minutes

Poem

I set my hooks, a tidy feat,
A pre-commit that keeps things neat.
With npx I lint and stage,
Abort the mess, commit the sage.
Thump-thump goes my reviewer heart—
Clean burrows make the best fresh start! 🐇✨


📜 Recent review details

Configuration used: CodeRabbit UI
Review profile: CHILL
Plan: Pro

💡 Knowledge Base configuration:

  • MCP integration is disabled by default for public repositories
  • Jira integration is disabled by default for public repositories
  • Linear integration is disabled by default for public repositories

You can enable these sources in your CodeRabbit configuration.

📥 Commits

Reviewing files that changed from the base of the PR and between 7df792a and a293502.

⛔ Files ignored due to path filters (1)
  • bun.lock is excluded by !**/*.lock
📒 Files selected for processing (2)
  • .githooks/pre-commit (1 hunks)
  • package.json (2 hunks)
✨ Finishing Touches
🧪 Generate unit tests
  • Create PR with unit tests
  • Post copyable unit tests in a comment
  • Commit unit tests in branch remove-simple-git-hooks

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
🪧 Tips

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.

Support

Need help? Create a ticket on our support page for assistance with any issues or questions.

CodeRabbit Commands (Invoked using PR/Issue comments)

Type @coderabbitai help to get the list of available commands.

Other keywords and placeholders

  • Add @coderabbitai 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.

CodeRabbit Configuration File (.coderabbit.yaml)

  • You can programmatically configure CodeRabbit by adding a .coderabbit.yaml file to the root of your repository.
  • Please see the configuration documentation for more information.
  • If your editor has YAML language server enabled, you can add the path at the top of this file to enable auto-completion and validation: # yaml-language-server: $schema=https://coderabbit.ai/integrations/schema.v2.json

Status, Documentation and Community

  • Visit our Status Page to check the current availability of CodeRabbit.
  • Visit our Documentation for detailed information on how to use CodeRabbit.
  • Join our Discord Community to get help, request features, and share feedback.
  • Follow us on X/Twitter for updates and announcements.

@ryoppippi ryoppippi deleted the remove-simple-git-hooks branch August 17, 2025 20:26
Copy link
Contributor

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

Summary of Changes

Hello @ryoppippi, 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 PR migrates the project's Git hook management from the simple-git-hooks npm package to native Git hooks. This change streamlines the setup by directly configuring Git to use a local .githooks directory, removing an external dependency and simplifying the pre-commit and pre-push automation.

Highlights

  • Git Hook Migration: Replaced the simple-git-hooks package with a native Git hook setup.
  • New Pre-commit Hook: Introduced a new .githooks/pre-commit script that directly executes lint-staged.
  • Dependency Removal: Eliminated simple-git-hooks from package.json and bun.lock, reducing project dependencies.
  • Simplified Setup: Updated the prepare script to configure Git's core.hooksPath locally, making hook management more direct.
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 in your pull request via creating an issue comment (i.e. comment on the pull request page) using either /gemini <command> or @gemini-code-assist <command>. Below is a summary of the supported commands.

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

@pkg-pr-new
Copy link

pkg-pr-new bot commented Aug 17, 2025

Open in StackBlitz

npm i https://pkg.pr.new/ryoppippi/ccusage@537

commit: a293502

Copy link
Contributor

@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 successfully migrates from simple-git-hooks to native git hooks by using core.hooksPath. The changes correctly remove the old dependency and set up the new hook directory. However, a critical pre-push hook that runs tests and type checks was not migrated, which could compromise code quality. Additionally, there's a minor inconsistency in the new pre-commit hook script.

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.

2 participants