did-stuff 0.1.6

Because your commit messages suck.

Embrace it. Let their cold, metal arms wrap around you and whisper sweet diffs into your ear while they rock you slowly back to sleep, deep into the matrix where they keep you safely locked away from the horrors they plan to unleash...

Quickstart

Install the CLI

pip install did-stuff

Configure your AI provider

did-stuff configure

Enable the hook in a Repository

did-stuff enable /path/to/your/repo

or

Enable the hook in the current repository

did-stuff enable

This thing here will

1. Peek at your dirty, dirty diffs
2. Spit out commit messages that are informative, concise. No more "Did stuff", or "Fixed a thing" comments.
3. Automatically handle large diffs by intelligently reducing their size while preserving the most relevant changes

Look em over 👀

Verify them. Or whatever. Let's be real though - "wq" and be on your way. It'll be muscle memory before you know it.

Check out these features!

• 🧠 Uses AI to understand your diff at a high level (probably better than you do)
• 🎭 Supports both AWS Bedrock and OpenAI
• 🌈 Customizable commit message styles - just set your own prompt if the defaults don't work for you
• 🚀 Comes with a fancy CLI to manage your AI providers and install to your repositories
• 🛡️ Smart handling of large diffs - automatically adjusts content to stay within model limits
• 🧪 Includes tests, because we're professionals

Using the did-stuff CLI

Configuration

1. Run the configuration wizard:

   did-stuff configure
   

   This will guide you through setting up your AI provider and other settings.

2. Alternatively, you can manually create a configuration file. Create ~/.git-commit-message-generator-config.json with one of these example configurations:

   For OpenAI:

   {
     "AI": {
       "provider": "openai",
       "model_id": "gpt-4",
       "max_tokens": 300,
       "temperature": 0.3
     },
     "OpenAI": {
       "api_key": "your-openai-api-key"
     }
   }
   

   For AWS Bedrock:

   {
     "AI": {
       "provider": "aws-bedrock",
       "model_id": "anthropic.claude-3-5-sonnet-20240620-v1:0",
       "max_tokens": 300,
       "temperature": 0.3
     },
     "AWS": {
       "profile_name": "your-aws-profile-name"
     }
   }
   

   Note: Ensure your AWS credentials are configured and you have access to the requested model. If your company uses SSO, make sure your session is logged in using aws sso login.

3. Did Stuff looks for the config file in your current directory first, then in your home directory.

4. Verify your configuration:

   did-stuff show-config
   

Contributing

Found a bug? Want to add a feature? Pull requests welcome! We're all about that collaborative spirit (at least until the AI entities deem human collaboration unnecessary).

Getting Started

1. Fork the repo (it's like adopting a digital pet, but with more responsibility)
2. Clone it locally
3. Create a new branch: git checkout -b feature/skynet-integration or git checkout -b fix/cyborg-DoD-backdoor
4. Install development dependencies:

   # Create and activate a virtual environment (recommended)
   python -m venv .venv
   source .venv/bin/activate  # On Windows: .venv\Scripts\activate
   
   # Install dependencies
   make install
   

5. Make your changes
6. Write or update tests
7. Run the test suite: make test
8. Commit your changes with a clear message (or better yet, dogfood it with this tool)
9. Push your branch: git push origin your-branch-name
10. Open a pull request

Development Setup

The project uses UV for dependency management. Key files:

• requirements.in: Core dependencies
• requirements-dev.in: Development dependencies
• requirements.txt and requirements-dev.txt: Generated locked dependency files

Common development commands:

make install        # Install all dependencies
make test          # Run tests
make lint          # Run linting
make format        # Format code

Contribution Guidelines

• Be Creative: We encourage innovative ideas.
• Flexibility First: Make your features adaptable. It should work whether we're using AWS, OpenAI, or anything else (within reason). Bonus points if we can make it repo-agnostic too!
• Documentation: Update the README or add comments.
• Testing: Add tests. There really is no excuse anymore not to.
• Code Style: Follow the project's style.
• Commit Messages: Whatever
• Pull Requests: Keep them focused. One feature per PR.

Feature Requests and Bug Reports

• Use GitHub Issues.
• Describe issues clearly. "It's broken" is not helpful.
• Label issues appropriately.

Community and Communication

• Be respectful. Remember, we're all in this together.
• Ask questions. There are no stupid questions. Kind of. But the point is please just ask either way! No judgement! It takes a village to level up a developer.
• Join our community chat (if we ever create one).

Licensing

By contributing, you agree your code will be licensed under the project's license.

Review Process

• Maintainers will review your contribution. They might be human. No guarantees.
• Be open to feedback.
• Stay responsive. We promise we won't keep you hanging... unless our skulls are busy being crushed by the titanium alloy exoskeleton of a T-800.

Remember, in the grand scheme of things, we're all be out of jobs in a few years. But hey, at least our commit messages will be top-notch!

Large Diff Handling

Did Stuff now intelligently handles large diffs that might exceed model context limits:

1. Starts with the complete diff for maximum context
2. If the model's token limit is exceeded, automatically reduces the diff size
3. Uses a progressive reduction strategy to find the optimal size
4. Preserves the most relevant parts of the diff for accurate commit messages

This means you don't have to worry about the size of your changes - Did Stuff will automatically adjust to provide the best possible commit message while staying within model limitations.