Skip to content

Add shelltime cc statusline integration to README#194

Merged
AnnatarHe merged 1 commit intomainfrom
claude/add-statusline-docs-UZEA1
Jan 4, 2026
Merged

Add shelltime cc statusline integration to README#194
AnnatarHe merged 1 commit intomainfrom
claude/add-statusline-docs-UZEA1

Conversation

@AnnatarHe
Copy link
Copy Markdown
Contributor

Add documentation for the shelltime cc statusline command that integrates with Claude Code's status bar feature, linking to the official docs and the detailed internal guide.

Add documentation for the `shelltime cc statusline` command that integrates
with Claude Code's status bar feature, linking to the official docs and
the detailed internal guide.
@gemini-code-assist
Copy link
Copy Markdown
Contributor

Summary of Changes

Hello @AnnatarHe, 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 enhances the project's documentation by introducing a comprehensive guide for integrating shelltime with Claude Code's status bar. This new documentation empowers users to monitor real-time cost and context usage directly within their development environment, fostering better resource management and transparency.

Highlights

  • New Documentation Section: A new section titled 'Claude Code Statusline Integration' has been added to the README.md file.
  • Statusline Integration: The documentation details how to integrate the shelltime cc statusline command with Claude Code's status bar.
  • Real-time Metrics: The integration allows for displaying real-time cost and context usage directly in the Claude Code status bar.
  • Setup Instructions: Clear setup instructions, including a JSON snippet for Claude Code settings, are provided.
  • Detailed Explanation: An example of the status line output is shown, along with a table explaining each metric displayed (Model, Session cost, Today's cost, Context usage).
  • External and Internal Links: The documentation includes links to the official Claude Code status bar documentation and a more detailed internal guide (docs/CC_STATUSLINE.md).
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.

@AnnatarHe AnnatarHe merged commit 316eb66 into main Jan 4, 2026
2 checks passed
@AnnatarHe AnnatarHe deleted the claude/add-statusline-docs-UZEA1 branch January 4, 2026 06:35
@codecov
Copy link
Copy Markdown

codecov Bot commented Jan 4, 2026

Codecov Report

✅ All modified and coverable lines are covered by tests.

Flag Coverage Δ
unittests 37.17% <ø> (?)

Flags with carried forward coverage won't be shown. Click here to find out more.
see 2 files with indirect coverage changes

🚀 New features to boost your workflow:
  • ❄️ Test Analytics: Detect flaky tests, report on failures, and find test suite problems.

Copy link
Copy Markdown
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 adds a new section to the README.md file to document the Claude Code statusline integration. The documentation is clear and provides a good overview for users. I have one suggestion to improve the clarity of the setup instructions to prevent users from accidentally overwriting their settings file.

Comment thread README.md

### Setup

Add to your Claude Code settings (`~/.claude/settings.json`):
Copy link
Copy Markdown
Contributor

Choose a reason for hiding this comment

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

medium

To prevent users from accidentally overwriting their existing Claude Code configuration, it's better to be more explicit in the setup instructions. The current phrasing "Add to..." could be misinterpreted as replacing the entire file. I suggest rephrasing to clarify that the statusLine key should be added or updated within their existing settings.json file.

Suggested change
Add to your Claude Code settings (`~/.claude/settings.json`):
In your Claude Code settings file (`~/.claude/settings.json`), add or update the `statusLine` key:

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