diny

Product Introduction

1. Diny is a command-line tool that automatically generates git commit messages by analyzing staged code changes through AI-powered analysis. It integrates directly with git workflows to maintain clean commit histories using conventional commit standards without requiring external API keys. The tool includes a timeline visualization feature that displays commit patterns and project evolution.
2. The core value lies in eliminating manual commit message writing while enforcing consistent formatting standards across development teams. It reduces cognitive load for developers by handling repetitive documentation tasks through local AI processing via Ollama integration. The timeline view provides actionable insights into project history without requiring external dashboard tools.

Main Features

1. Diny automatically generates commit messages by analyzing git diff output of staged changes using Ollama's local AI processing, avoiding cloud API dependencies. It filters out non-essential changes in lockfiles, binaries, and build artifacts to focus on meaningful code modifications. The system learns from user feedback through message regeneration attempts that refine output quality over time.
2. The interactive workflow offers multiple message options with edit/preview capabilities before finalizing commits, including draft mode for message preparation without immediate commits. Users can save generated messages to files or pipe them directly into git commit commands through CLI integration. The tool supports custom feedback loops where users can manually refine AI outputs through text prompts.
3. Timeline analysis features visualize commit patterns through temporal distribution charts and message quality metrics. Custom UI themes (10+ dark/light variations) adapt terminal output styling, including Flexoki color schemes for optimized readability. LazyGit integration enables message generation directly within the TUI interface through predefined custom commands.

Problems Solved

1. Diny addresses inconsistent commit message quality caused by human error and time constraints during frequent commits. It eliminates the need for manual adherence to conventional commit standards through automated formatting enforcement. The tool prevents commit history pollution from uninformative messages like "fix stuff" or temporary notes.
2. The primary target users are development teams and individual programmers maintaining medium-to-large codebases requiring audit-ready commit histories. DevOps engineers implementing compliance standards benefit from its automated documentation capabilities. Open-source maintainers needing clear project histories for contributor coordination find value in the timeline analysis.
3. Typical use cases include sprint-based development requiring daily commit documentation, client projects needing detailed change tracking, and legacy codebase maintenance where historical context is crucial. Teams implementing GitOps workflows use it to maintain deployment-triggering commit quality. Individual developers leverage the tool for personal projects requiring professional-grade history tracking.

Unique Advantages

1. Unlike cloud-dependent AI commit tools, Diny operates locally through Ollama integration without requiring API keys or internet access. It surpasses basic template-based tools by combining AI analysis with user feedback loops for continuous output improvement. The timeline feature provides native commit analytics without third-party dashboard integrations.
2. Innovative features include context-aware noise filtering that ignores non-code files and LazyGit TUI integration for in-workflow message generation. The theme engine supports terminal UI customization beyond standard color schemes, including Flexoki's optimized contrast palettes. Smart regeneration remembers previous attempts within a session to produce progressively better suggestions.
3. Competitive advantages include zero-configuration git alias integration through "diny auto" setup and Windows/macOS/Linux parity via brew/scoop installations. The tool's self-contained nature (no external dependencies beyond Ollama) and MIT licensing enable enterprise adoption. Unique "commit message stashing" allows postponing AI-generated messages without breaking workflow continuity.

Frequently Asked Questions (FAQ)

1. How does Diny handle API keys for AI processing? Diny uses local Ollama instances for AI processing, eliminating the need for cloud API keys or external services. Users must install Ollama separately and run appropriate LLM models locally. All data processing occurs on the user's machine without transmitting code to third parties.
2. Can Diny integrate with existing git hooks? Yes, Diny's CLI output can be piped into standard git commands or triggered through pre-commit hooks. The "--print" flag enables message generation for integration with custom scripts. Users can combine it with commit-msg hooks for automated message validation.
3. How do themes affect functionality? UI themes only modify terminal color schemes and formatting without impacting core functionality. Users can switch themes dynamically using "diny theme list" and selection. Theme configurations persist between sessions through local configuration files.