Jeeves

Jeeves is a command-line tool that creates AI-powered Git commit messages that mercilessly roast you and your code.

• Generate intelligent conventional commit messages with gitmoji based on your staged changes that point out what an idiot you are.
• Option to automatically stage all changes before committing
• Option to push changes after committing
• Customizable AI prompts for tailored commit message generation
• Choose any AI model (chat-gpt 4.1-mini by default)

✨ refactor(HTMLText): rewrite HTML parsing and rendering from scratch because why not torture future maintainers Completely scrap the previously sane approach of leveraging NSAttributedString's native HTML importer—because parsing HTML by hand in SwiftUI is obviously a great idea—and replace it with a painfully verbose custom parser that handles only a handful of tags (<b>, <i>, <u>, <strong>, <em>) by rudimentary string manipulation and manual state tracking.

Add a fragile, regex-based preprocessing pipeline to replace paragraph and break tags with newlines, which predictably will fail on anything but the simplest input and blatantly ignores the complexity of HTML’s DOM and semantics. Implement a hopelessly naive tag parser and format stack that counts nested tags without any error recovery, inviting undefined behavior from malformed or unexpected inputs.

Replace cached AttributedString with a freshly built one on each render, ignoring performance consequences and the obvious benefits of reuse or incremental updates—because rendering performance doesn’t matter, right?

Throw in a sprawling debug preview showcasing trivial formatting examples like "Bold text", "<b>Bold <i>nested</i></b>", and some paragraph-handling tests to prove the gross oversimplification, all stacked in a monstrously long VStack with no regard for code readability or separation of concerns.

In summary: regress from standard, battle-tested Cocoa HTML rendering to a brittle, hand-rolled solution that’s both inefficient and incomplete. Future developers, good luck deciphering this spaghetti; you’ll need it.

• Ruby 2.6 or higher
• Git

gem install jeeves-git-commit

This automatically adds Jeeves to your PATH.

1. Clone this repository:

git clone https://github.com/jubishop/Jeeves.git
cd Jeeves

2. Build and install the gem:

gem build jeeves.gemspec
gem install jeeves-git-commit-*.gem

1. Clone this repository:

git clone https://github.com/jubishop/Jeeves.git
cd Jeeves

2. Run the install script:

./install.sh

The script will:

• Install Jeeves to /usr/local/bin (or ~/.local/bin if you don't have write access)
• Add the install location to your PATH if necessary
• Set up the config directory with the default prompt file
• Make sure the script is executable

1. Clone this repository:

git clone https://github.com/jubishop/Jeeves.git
cd Jeeves

2. Make the script executable:

chmod +x bin/jeeves

3. Create a symbolic link to make Jeeves available globally:

ln -s "$(pwd)/bin/jeeves" /usr/local/bin/jeeves

Jeeves requires an OpenRouter API key to generate commit messages. You need to set this as an environment variable:

export OPENROUTER_API_KEY="your_openrouter_api_key"

You can get an API key from OpenRouter.

Optionally, you can specify a different model by setting:

export GIT_COMMIT_MODEL="openai/gpt-4o"

The default model is openai/gpt-4.1-mini if not specified.

Jeeves supports two levels of prompt configuration with the following priority order:

1. Repository-Specific Prompt (Highest Priority): Create a .jeeves_prompt file in the root of your Git repository to customize the prompt for that specific project.
2. Global Prompt (Fallback): Stored in ~/.config/jeeves/prompt. This is used when no repository-specific prompt is found.

When you run Jeeves, it will:

1. First look for a .jeeves_prompt file in the root of the current Git repository
2. If not found, fall back to the global prompt at ~/.config/jeeves/prompt

This allows you to have a default prompt for all your projects while still being able to customize the prompt for specific repositories that may have different requirements or coding standards.

Example Repository-Specific Prompt: See example.jeeves_prompt in this repository for an example of how you might customize the prompt for a JavaScript/Node.js project with specific requirements (that also doesn't roast you).

When you run Jeeves for the first time, if there's no global prompt file in the config directory, it will copy config/prompt to the config directory automatically.

The special string: {{DIFF}}, in your prompt will be replaced with the current git diff.

Navigate to your Git repository and run:

jeeves [options]

Options:

• -a, --all: Stage all changes before committing
• -p, --push: Push changes after committing
• --version: Show version information
• -h, --help: Show help message

# Generate a commit message for already staged changes
jeeves

# Stage all changes and generate a commit message
jeeves -a

# Stage all changes, generate a commit message, and push
jeeves -a -p

MIT

Jeeves follows a specific project structure where all gemspec files and built gem files (.gem) are placed in the gemspec/ folder rather than the root directory. This keeps the root directory clean and organized.

Jeeves provides several rake tasks to streamline development:

# Run the test suite
rake test

# Build the gem and place it in the gemspec/ folder
rake build

# Build, install and test the gem
rake install

# Build and push the gem to RubyGems
rake push

The default task is rake test.

Jeeves uses Minitest for testing. To run the tests:

bundle install
rake test

The test suite includes:

• Unit tests for the CLI functionality
• Tests for version consistency
• Mock tests for API interactions (using WebMock)

Justin Bishop (jubishop)