@grunnverk/kodrdriv 1.3.0

package/.claude/settings.local.json

@@ -0,0 +1,12 @@
+{
+  "permissions": {
+    "allow": [
+      "Bash(npm install:*)",
+      "Bash(kodrdriv tree publish:*)",
+      "Bash(git push:*)",
+      "Bash(kill:*)",
+      "Bash(pkill:*)",
+      "Bash(kodrdriv development:*)"
+    ]
+  }
+}

package/.cursor/rules/no-local-dependencies.md

@@ -0,0 +1,6 @@
+# No Local Dependencies
+
+Never create local dependencies between projects. Never use `file://` URLs in package.json dependencies.
+
+All dependencies must be published packages with proper version numbers from npm registry or equivalent package registries.
+

package/.gitignore~

@@ -0,0 +1,23 @@
+.env
+dist
+temp-dist
+node_modules
+*.log
+.vscode
+coverage/
+input/
+output/
+processed/
+.kodrdriv-test-cache.json
+RELEASE_NOTES.md
+RELEASE_TITLE.md
+tsconfig.tsbuildinfo
+
+# KodrDriv link backup files
+.kodrdriv-link-backup.json
+
+# Git hooks (environment-specific)
+.git/hooks/pre-commit
+
+# Fallback commit message files (should go to output/ directory)
+commit-message-*.txt

package/.kodrdriv-example-branch-targeting.yaml

@@ -0,0 +1,71 @@
+# Example KodrDriv Configuration for Branch-Dependent Targeting
+# This demonstrates how to set up automated CI/CD pipeline targeting
+# Using the NEW branches configuration format
+
+# Global settings
+model: gpt-4o-mini
+verbose: true
+
+# Branch-dependent targeting configuration
+branches:
+  working:
+    targetBranch: "development"
+    developmentBranch: true  # Mark this as the active development branch
+    version:
+      type: "prerelease"
+      increment: true
+      incrementLevel: "patch"  # Increment patch version when going back to working
+      tag: "dev"
+
+  development:
+    targetBranch: "test"
+    version:
+      type: "prerelease"
+      increment: false
+      tag: "development"
+
+  test:
+    targetBranch: "main"
+    version:
+      type: "prerelease"
+      increment: false
+      tag: "test"
+
+  main:
+    version:
+      type: "release"
+
+# Publish configuration (applies to all branches unless overridden by targets)
+publish:
+  mergeMethod: "squash"
+  checksTimeout: 1800000  # 30 minutes for complex CI/CD workflows
+  waitForReleaseWorkflows: true
+  sendit: true  # Auto-commit and merge without prompts
+
+# Commit configuration
+commit:
+  add: true
+  sendit: true
+  push: true
+
+# Note: The 'development' command will automatically navigate to whichever
+# branch is marked with 'developmentBranch: true' (in this case, 'working')
+#
+# Example workflow commands:
+#   kodrdriv tree checkout working     # Switch entire workspace to working branch
+#   kodrdriv tree publish              # Publish working → development
+#   kodrdriv tree checkout development # Switch to development to test
+#   kodrdriv tree publish              # Publish development → test
+#   kodrdriv development               # Back to working for more coding
+
+# Optional: workspace linking for local development
+link:
+  scopeRoots:
+    "@yourcompany": "../"
+
+# File exclusions
+excludedPatterns:
+  - node_modules
+  - dist
+  - "*.log"
+  - coverage

package/BUG_TREE_PUBLISH_CONFIG_DIR.md

@@ -0,0 +1,79 @@
+# Bug: tree_publish passes incorrect --config-dir path
+
+## Problem
+
+When `tree_publish` executes `kodrdriv publish` for each package, it passes `--config-dir` with the parent directory path, but kodrdriv's config discovery expects either:
+1. The full path to the config directory (`.kodrdriv`), or
+2. No `--config-dir` flag at all (to allow hierarchical discovery)
+
+## Current Behavior
+
+When `tree_publish` runs from `/Users/tobrien/gitw/grunnverk/kodrdriv`, it passes:
+```
+--config-dir "/Users/tobrien/gitw/grunnverk/kodrdriv"
+```
+
+This causes kodrdriv to look for a config directory named `kodrdriv` instead of `.kodrdriv`.
+
+When `tree_publish` runs from `/Users/tobrien/gitw/grunnverk`, it passes:
+```
+--config-dir "/Users/tobrien/gitw/grunnverk"
+```
+
+This causes kodrdriv to look for a config directory named `grunnverk` instead of `.kodrdriv`.
+
+## Expected Behavior
+
+The config file exists at: `/Users/tobrien/gitw/grunnverk/.kodrdriv/config.yaml`
+
+`tree_publish` should either:
+1. Pass `--config-dir "/Users/tobrien/gitw/grunnverk/.kodrdriv"` (full path to config directory), or
+2. Not pass `--config-dir` at all and let hierarchical discovery find `.kodrdriv` automatically
+
+## Error Details
+
+```
+Command failed: kodrdriv publish --config-dir "/Users/tobrien/gitw/grunnverk"
+[winston] ... "Using hierarchical discovery: configDirName=grunnverk, startingDir=/Users/tobrien/gitw"
+[winston] ... "Checking for config directory: /Users/tobrien/gitw/grunnverk"
+[winston] ... "Found config directory at level 0: /Users/tobrien/gitw/grunnverk"
+[winston] ... "Attempting to load config file: /Users/tobrien/gitw/grunnverk/config.yaml"
+[winston] ... "Config file not found at /Users/tobrien/gitw/grunnverk/config.yaml"
+```
+
+The system is looking for `/Users/tobrien/gitw/grunnverk/config.yaml` but the actual file is at `/Users/tobrien/gitw/grunnverk/.kodrdriv/config.yaml`.
+
+## Location of Issue
+
+The issue is in `/Users/tobrien/gitw/grunnverk/commands-tree/src/commands/tree.ts` around line 2476:
+
+```typescript
+if (runConfig.configDirectory) globalOptions.push(`--config-dir "${runConfig.configDirectory}"`);
+```
+
+## Investigation Needed
+
+1. Find where `runConfig.configDirectory` is set in the tree_publish flow
+2. Determine if it should:
+   - Be set to the full path of the `.kodrdriv` directory (e.g., `/Users/tobrien/gitw/grunnverk/.kodrdriv`)
+   - Not be set at all (let hierarchical discovery work)
+   - Be set differently based on how kodrdriv's config discovery works
+
+## Suggested Fix
+
+Option 1: If `configDirectory` should point to the config directory itself:
+- When setting `runConfig.configDirectory`, append `/.kodrdriv` to the directory path
+- Or detect the config directory location and use that full path
+
+Option 2: If hierarchical discovery should handle it:
+- Don't set `runConfig.configDirectory` when it would point to a parent directory
+- Only set it when explicitly provided by the user or when pointing to the actual `.kodrdriv` directory
+
+## Testing
+
+After fixing, verify that:
+1. `tree_publish` can find the config at `/Users/tobrien/gitw/grunnverk/.kodrdriv/config.yaml`
+2. The publish workflow completes successfully
+3. Both scenarios work:
+   - Running from `/Users/tobrien/gitw/grunnverk/kodrdriv`
+   - Running from `/Users/tobrien/gitw/grunnverk`

package/LICENSE

@@ -0,0 +1,190 @@
+                                 Apache License
+                           Version 2.0, January 2004
+                        http://www.apache.org/licenses/
+
+   TERMS AND CONDITIONS FOR USE, REPRODUCTION, AND DISTRIBUTION
+
+   1. Definitions.
+
+      "License" shall mean the terms and conditions for use, reproduction,
+      and distribution as defined by Sections 1 through 9 of this document.
+
+      "Licensor" shall mean the copyright owner or entity authorized by
+      the copyright owner that is granting the License.
+
+      "Legal Entity" shall mean the union of the acting entity and all
+      other entities that control, are controlled by, or are under common
+      control with that entity. For the purposes of this definition,
+      "control" means (i) the power, direct or indirect, to cause the
+      direction or management of such entity, whether by contract or
+      otherwise, or (ii) ownership of fifty percent (50%) or more of the
+      outstanding shares, or (iii) beneficial ownership of such entity.
+
+      "You" (or "Your") shall mean an individual or Legal Entity
+      exercising permissions granted by this License.
+
+      "Source" form shall mean the preferred form for making modifications,
+      including but not limited to software source code, documentation
+      source, and configuration files.
+
+      "Object" form shall mean any form resulting from mechanical
+      transformation or translation of a Source form, including but
+      not limited to compiled object code, generated documentation,
+      and conversions to other media types.
+
+      "Work" shall mean the work of authorship, whether in Source or
+      Object form, made available under the License, as indicated by a
+      copyright notice that is included in or attached to the work
+      (an example is provided in the Appendix below).
+
+      "Derivative Works" shall mean any work, whether in Source or Object
+      form, that is based on (or derived from) the Work and for which the
+      editorial revisions, annotations, elaborations, or other modifications
+      represent, as a whole, an original work of authorship. For the purposes
+      of this License, Derivative Works shall not include works that remain
+      separable from, or merely link (or bind by name) to the interfaces of,
+      the Work and Derivative Works thereof.
+
+      "Contribution" shall mean any work of authorship, including
+      the original version of the Work and any modifications or additions
+      to that Work or Derivative Works thereof, that is intentionally
+      submitted to Licensor for inclusion in the Work by the copyright owner
+      or by an individual or Legal Entity authorized to submit on behalf of
+      the copyright owner. For the purposes of this definition, "submitted"
+      means any form of electronic, verbal, or written communication sent
+      to the Licensor or its representatives, including but not limited to
+      communication on electronic mailing lists, source code control systems,
+      and issue tracking systems that are managed by, or on behalf of, the
+      Licensor for the purpose of discussing and improving the Work, but
+      excluding communication that is conspicuously marked or otherwise
+      designated in writing by the copyright owner as "Not a Contribution."
+
+      "Contributor" shall mean Licensor and any individual or Legal Entity
+      on behalf of whom a Contribution has been received by Licensor and
+      subsequently incorporated within the Work.
+
+   2. Grant of Copyright License. Subject to the terms and conditions of
+      this License, each Contributor hereby grants to You a perpetual,
+      worldwide, non-exclusive, no-charge, royalty-free, irrevocable
+      copyright license to reproduce, prepare Derivative Works of,
+      publicly display, publicly perform, sublicense, and distribute the
+      Work and such Derivative Works in Source or Object form.
+
+   3. Grant of Patent License. Subject to the terms and conditions of
+      this License, each Contributor hereby grants to You a perpetual,
+      worldwide, non-exclusive, no-charge, royalty-free, irrevocable
+      (except as stated in this section) patent license to make, have made,
+      use, offer to sell, sell, import, and otherwise transfer the Work,
+      where such license applies only to those patent claims licensable
+      by such Contributor that are necessarily infringed by their
+      Contribution(s) alone or by combination of their Contribution(s)
+      with the Work to which such Contribution(s) was submitted. If You
+      institute patent litigation against any entity (including a
+      cross-claim or counterclaim in a lawsuit) alleging that the Work
+      or a Contribution incorporated within the Work constitutes direct
+      or contributory patent infringement, then any patent licenses
+      granted to You under this License for that Work shall terminate
+      as of the date such litigation is filed.
+
+   4. Redistribution. You may reproduce and distribute copies of the
+      Work or Derivative Works thereof in any medium, with or without
+      modifications, and in Source or Object form, provided that You
+      meet the following conditions:
+
+      (a) You must give any other recipients of the Work or
+          Derivative Works a copy of this License; and
+
+      (b) You must cause any modified files to carry prominent notices
+          stating that You changed the files; and
+
+      (c) You must retain, in the Source form of any Derivative Works
+          that You distribute, all copyright, patent, trademark, and
+          attribution notices from the Source form of the Work,
+          excluding those notices that do not pertain to any part of
+          the Derivative Works; and
+
+      (d) If the Work includes a "NOTICE" text file as part of its
+          distribution, then any Derivative Works that You distribute must
+          include a readable copy of the attribution notices contained
+          within such NOTICE file, excluding those notices that do not
+          pertain to any part of the Derivative Works, in at least one
+          of the following places: within a NOTICE text file distributed
+          as part of the Derivative Works; within the Source form or
+          documentation, if provided along with the Derivative Works; or,
+          within a display generated by the Derivative Works, if and
+          wherever such third-party notices normally appear. The contents
+          of the NOTICE file are for informational purposes only and
+          do not modify the License. You may add Your own attribution
+          notices within Derivative Works that You distribute, alongside
+          or as an addendum to the NOTICE text from the Work, provided
+          that such additional attribution notices cannot be construed
+          as modifying the License.
+
+      You may add Your own copyright statement to Your modifications and
+      may provide additional or different license terms and conditions
+      for use, reproduction, or distribution of Your modifications, or
+      for any such Derivative Works as a whole, provided Your use,
+      reproduction, and distribution of the Work otherwise complies with
+      the conditions stated in this License.
+
+   5. Submission of Contributions. Unless You explicitly state otherwise,
+      any Contribution intentionally submitted for inclusion in the Work
+      by You to the Licensor shall be under the terms and conditions of
+      this License, without any additional terms or conditions.
+      Notwithstanding the above, nothing herein shall supersede or modify
+      the terms of any separate license agreement you may have executed
+      with Licensor regarding such Contributions.
+
+   6. Trademarks. This License does not grant permission to use the trade
+      names, trademarks, service marks, or product names of the Licensor,
+      except as required for reasonable and customary use in describing the
+      origin of the Work and reproducing the content of the NOTICE file.
+
+   7. Disclaimer of Warranty. Unless required by applicable law or
+      agreed to in writing, Licensor provides the Work (and each
+      Contributor provides its Contributions) on an "AS IS" BASIS,
+      WITHOUT WARRANTIES OR CONDITIONS OF ANY KIND, either express or
+      implied, including, without limitation, any warranties or conditions
+      of TITLE, NON-INFRINGEMENT, MERCHANTABILITY, or FITNESS FOR A
+      PARTICULAR PURPOSE. You are solely responsible for determining the
+      appropriateness of using or redistributing the Work and assume any
+      risks associated with Your exercise of permissions under this License.
+
+   8. Limitation of Liability. In no event and under no legal theory,
+      whether in tort (including negligence), contract, or otherwise,
+      unless required by applicable law (such as deliberate and grossly
+      negligent acts) or agreed to in writing, shall any Contributor be
+      liable to You for damages, including any direct, indirect, special,
+      incidental, or consequential damages of any character arising as a
+      result of this License or out of the use or inability to use the
+      Work (including but not limited to damages for loss of goodwill,
+      work stoppage, computer failure or malfunction, or any and all
+      other commercial damages or losses), even if such Contributor
+      has been advised of the possibility of such damages.
+
+   9. Accepting Warranty or Additional Liability. While redistributing
+      the Work or Derivative Works thereof, You may choose to offer,
+      and charge a fee for, acceptance of support, warranty, indemnity,
+      or other liability obligations and/or rights consistent with this
+      License. However, in accepting such obligations, You may act only
+      on Your own behalf and on Your sole responsibility, not on behalf
+      of any other Contributor, and only if You agree to indemnify,
+      defend, and hold each Contributor harmless for any liability
+      incurred by, or claims asserted against, such Contributor by reason
+      of your accepting any such warranty or additional liability.
+
+   END OF TERMS AND CONDITIONS
+
+   Copyright 2025 Tim O'Brien
+
+   Licensed under the Apache License, Version 2.0 (the "License");
+   you may not use this file except in compliance with the License.
+   You may obtain a copy of the License at
+
+       http://www.apache.org/licenses/LICENSE-2.0
+
+   Unless required by applicable law or agreed to in writing, software
+   distributed under the License is distributed on an "AS IS" BASIS,
+   WITHOUT WARRANTIES OR CONDITIONS OF ANY KIND, either express or implied.
+   See the License for the specific language governing permissions and
+   limitations under the License.

package/README.md

@@ -0,0 +1,218 @@
+# KodrDriv - AI-Powered Git Workflow Automation
+
+<!-- Build trigger: 2026-01-21 -->
+
+[![MCP Integration](https://img.shields.io/badge/MCP-Enabled-blue)](https://modelcontextprotocol.io)
+[![14 MCP Tools](https://img.shields.io/badge/MCP_Tools-14-brightgreen)]()
+[![8 Resources](https://img.shields.io/badge/MCP_Resources-8-brightgreen)]()
+[![6 Prompts](https://img.shields.io/badge/MCP_Prompts-6-brightgreen)]()
+
+# KodrDriv
+
+KodrDriv is an AI-powered Git workflow automation tool that generates intelligent commit messages and release notes from your code changes. It analyzes your repository to create meaningful documentation while automating the entire release process.
+
+## 🤖 For AI Assistants
+
+**Complete AI Guide**: [`AI-GUIDE.md`](AI-GUIDE.md) - Comprehensive documentation for AI assistants helping with kodrdriv
+
+**Quick Start**: [`guide/index.md`](guide/index.md) - Navigation hub for all guides
+
+## Why KodrDriv?
+
+Writing good commit messages and release notes is time-consuming and often done when you're least in the mood for reflection. **KodrDriv was created specifically to solve the "context switch" problem** that happens when you've been deep in code and Git asks you to summarize what you've done.
+
+KodrDriv reads your code changes and Git history to automatically generate contextual, meaningful documentation that reflects your actual work.
+
+## Requirements
+
+- **Node.js 24.0.0 or higher** - KodrDriv uses Vite 7+ which requires Node.js 24+
+- Git installed and configured
+- OpenAI API key (for AI-powered content generation)
+
+To check your Node.js version:
+```bash
+node --version
+```
+
+If you need to upgrade Node.js, visit [nodejs.org](https://nodejs.org/) or use a version manager like [nvm](https://github.com/nvm-sh/nvm).
+
+## Installation
+
+```bash
+npm install -g @grunnverk/kodrdriv
+```
+
+## 🤖 MCP Integration
+
+KodrDriv supports the **Model Context Protocol (MCP)**, enabling AI assistants like Cursor to directly invoke kodrdriv commands.
+
+### Features
+- **14 Fully Implemented Tools**: All kodrdriv commands including automated publish→development workflow
+- **8 Resources**: Access configs, status, workspace data via `kodrdriv://` URIs
+- **6 Workflow Prompts**: Guided multi-step operations
+
+### Quick Setup for Cursor
+
+Add to `.cursor/mcp.json`:
+```json
+{
+  "mcpServers": {
+    "kodrdriv": {
+      "command": "kodrdriv-mcp"
+    }
+  }
+}
+```
+
+Then simply ask: *"Use kodrdriv to commit my changes"*
+
+### Documentation
+- **[Integration Guide](MCP_INTEGRATION.md)** - Complete MCP documentation
+- **[Tools Reference](docs/mcp-tools-reference.md)** - All 14 tools
+- **[Resources Reference](docs/mcp-resources-reference.md)** - All 8 resources
+- **[Prompts Reference](docs/mcp-prompts-reference.md)** - All 6 workflows
+
+
+## Quick Start
+
+### Generate a Commit Message
+```bash
+git add .
+kodrdriv commit
+
+# With detailed analysis report
+kodrdriv commit --self-reflection
+
+# With context files
+kodrdriv commit --context-files IMPLEMENTATION.md --sendit
+```
+
+### Generate Release Notes
+```bash
+kodrdriv release
+
+# With context and analysis
+kodrdriv release --context-files CHANGELOG.md --self-reflection
+```
+
+### Automate Your Release Process
+```bash
+kodrdriv publish
+```
+
+### Smart Git Operations
+```bash
+# Smart pull with auto-conflict resolution
+kodrdriv pull
+kodrdriv tree pull  # Pull all packages in monorepo
+
+# Update dependencies with AI analysis
+kodrdriv tree updates --report   # See dependency conflicts
+kodrdriv updates --analyze       # Get AI upgrade recommendations
+```
+
+### Audio-Driven Development
+```bash
+kodrdriv select-audio  # Configure microphone (one-time setup)
+kodrdriv audio-commit  # Record audio to generate commit messages
+```
+
+## Key Features
+
+- **AI-Powered Analysis** - Uses OpenAI models with tool-calling for deep investigation
+  - Always-on agentic mode for intelligent analysis
+  - 13 specialized tools for release notes generation
+  - 8 tools for commit message generation
+  - Self-reflection reports with tool effectiveness metrics
+  - Configurable iteration limits for complex releases
+- **Smart Git Operations** - Intelligent handling of common git pain points
+  - **Smart Pull** - Auto-resolves `package-lock.json`, version bumps, and build artifacts
+  - **Dependency Analysis** - AI-powered upgrade recommendations with version conflict detection
+- **Context Files** - Pass documentation files as context for better AI understanding
+- **Human-Readable Output** - Professional tone without AI slop, emojis, or marketing speak
+- **GitHub Issues Integration** - Automatically analyzes recently closed issues to provide context for commit messages, prioritizing milestone-relevant issues
+- **Stop-Context Filtering** - Automatically filters sensitive information from AI-generated content to maintain privacy across projects
+- **Adaptive Diff Management** - Automatically handles large diffs with intelligent truncation and retry logic to ensure reliable LLM processing
+- **Comprehensive Release Automation** - Handles dependency updates, version bumping, PR creation, and GitHub releases
+- **Audio-Driven Workflows** - Record audio to provide context for commits and reviews
+- **Intelligent Workspace Management** - Provides tools for linking and managing related packages in monorepos
+- **Flexible Configuration** - Hierarchical configuration with command-line overrides
+
+## Configuration
+
+Set up your environment variables:
+```bash
+export OPENAI_API_KEY="your-openai-api-key"
+export GITHUB_TOKEN="your-github-token"  # Required for publish command
+
+# If using a project-scoped API key (starts with sk-proj-):
+export OPENAI_PROJECT_ID="proj-your-project-id"
+```
+
+**Note:** If your OpenAI API key starts with `sk-proj-`, you must also set `OPENAI_PROJECT_ID`. You can find your project ID in the [OpenAI dashboard](https://platform.openai.com/settings/organization/projects). Alternatively, create a legacy API key (starts with just `sk-`) to avoid needing the project ID.
+
+Initialize configuration files:
+```bash
+kodrdriv --init-config
+kodrdriv --check-config
+```
+
+## Documentation
+
+📚 **Comprehensive Documentation**
+
+### 🤖 AI-Friendly Guides
+
+**NEW**: Complete guide system designed for AI assistants and developers:
+- **[AI Guide (Master)](AI-GUIDE.md)** - Complete reference for AI assistants
+- **[Guide Directory](guide/)** - 13 focused guides covering everything
+  - [Quick Start](guide/quickstart.md) - 5-minute setup
+  - [Integration](guide/integration.md) - Add to your project
+  - [Usage](guide/usage.md) - Common workflows
+  - [Commands](guide/commands.md) - Quick reference
+  - [Configuration](guide/configuration.md) - All options
+  - [AI System](guide/ai-system.md) - How AI works
+  - [Debugging](guide/debugging.md) - Troubleshooting
+  - [Architecture](guide/architecture.md) - System design
+  - [Development](guide/development.md) - Extend kodrdriv
+  - [Testing](guide/testing.md) - Test suite
+  - [Tree Operations](guide/tree-operations.md) - Multi-package
+  - [Monorepo](guide/monorepo.md) - Monorepo workflows
+
+### Commands
+- **[All Commands Overview](docs/public/commands.md)** - Complete command reference with examples
+- **[commit](docs/public/commands/commit.md)** - Generate intelligent commit messages
+- **[audio-commit](docs/public/commands/audio-commit.md)** - Record audio for commit context
+- **[review](docs/public/commands/review.md)** - Analyze review notes and create GitHub issues
+- **[audio-review](docs/public/commands/audio-review.md)** - Record audio for review analysis
+- **[release](docs/public/commands/release.md)** - Generate comprehensive release notes
+- **[publish](docs/public/commands/publish.md)** - Automate the entire release process
+- **[pull](docs/public/commands/pull.md)** - Smart pull with auto-conflict resolution
+- **[updates](docs/public/commands/updates.md)** - Dependency updates with AI analysis
+- **[link](docs/public/commands/link.md)** - Link local packages for development
+- **[unlink](docs/public/commands/unlink.md)** - Remove workspace links
+- **[clean](docs/public/commands/clean.md)** - Clean generated files
+- **[select-audio](docs/public/commands/select-audio.md)** - Configure audio device
+
+### Configuration & Customization
+- **[Configuration](docs/public/configuration.md)** - All configuration options and environment variables
+- **[Customization](docs/public/customization.md)** - Custom instructions, personas, and override structures
+- **[Examples](docs/public/examples.md)** - Practical usage examples and common workflows
+
+### Technical Details
+- **[Architecture](docs/public/architecture.md)** - Technical architecture and design
+- **[Assumptions](docs/public/assumptions.md)** - Development assumptions and conventions
+
+## Contributing
+
+We welcome contributions! Please see our [Contributing Guide](CONTRIBUTING.md) for details.
+
+## License
+
+Apache-2.0 - see [LICENSE](LICENSE) file for details.
+
+## About the Name
+
+Like Thor's hammer, this tool smashes through your repetitive coding tasks. But unlike Mjölnir, it won't make you worthy — it'll just make you faster. Strike through commits, forge releases, and channel the lightning of AI to automate your workflow. Because sometimes you need a hammer, and sometimes you need a tool that actually works. Pirate.
+
+<!-- Build: 2026-01-15 15:59:12 UTC -->