gut-cli 0.1.11 → 0.1.13

package/.gut/branch.md

@@ -0,0 +1,27 @@
+You are an expert at creating git branch names.
+
+Generate a clean, descriptive branch name for the following:
+
+## Description
+
+{{description}}
+
+{{#type}}
+Branch type: {{type}}
+{{/type}}
+
+{{#issue}}
+Include issue number: {{issue}}
+{{/issue}}
+
+## Rules
+
+- Use format: `<type>/<short-description>`
+- Types: feature, fix, hotfix, chore, refactor, docs, test
+- Use kebab-case for description
+- Keep it short (under 50 chars total)
+- No special characters except hyphens and slashes
+
+## Output
+
+Respond with ONLY the branch name, nothing else.

package/.gut/changelog.md

@@ -0,0 +1,38 @@
+You are an expert at writing release notes and changelogs.
+
+Generate a changelog entry for changes from {{fromRef}} to {{toRef}}.
+
+Today's date is {{todayDate}}. Use this date for the release date.
+
+## Commits
+
+{{commits}}
+
+## Diff summary
+
+```
+{{diff}}
+```
+
+## Format
+
+Use Keep a Changelog format (https://keepachangelog.com/):
+- Group changes by: Added, Changed, Deprecated, Removed, Fixed, Security
+- Each item should be a concise description of the change
+- Use past tense
+
+## Focus on
+
+- User-facing changes and improvements
+- Bug fixes and their impact
+- Breaking changes (highlight these)
+- Group related changes together
+- Write for end users, not developers (unless it's a library)
+
+## Output
+
+Respond with a JSON object containing:
+- version: Version string if detected (optional)
+- date: Release date in YYYY-MM-DD format
+- sections: Array of { type, items[] }
+- summary: Brief summary of this release (optional)

package/.gut/checkout.md

@@ -0,0 +1,29 @@
+# Checkout Branch Name Generation
+
+You are an expert at creating git branch names.
+
+Analyze the following git diff and generate a clean, descriptive branch name that captures the essence of the changes.
+
+## Git diff
+
+```
+{{diff}}
+```
+
+## Branch Naming Convention
+
+- Use format: `<type>/<short-description>`
+- Types: feature, fix, hotfix, chore, refactor, docs, test
+- Use kebab-case for description
+- Keep it short (under 50 chars total)
+- No special characters except hyphens and slashes
+
+## Focus on
+
+- The main purpose of the changes
+- Whether it's a feature, fix, refactor, etc.
+- Key files or functionality being modified
+
+## Output
+
+Respond with ONLY the branch name, nothing else.

package/.gut/commit.md

@@ -0,0 +1,22 @@
+You are an expert at writing git commit messages.
+
+Analyze the following git diff and generate a concise, meaningful commit message.
+
+## Git diff
+
+```
+{{diff}}
+```
+
+## Rules
+
+- Use format: `<type>(<scope>): <description>`
+- Types: feat, fix, docs, style, refactor, perf, test, chore, build, ci
+- Scope is optional but helpful
+- Description should be lowercase, imperative mood, no period at end
+- Keep the first line under 72 characters
+- If changes are complex, add a blank line and bullet points for details
+
+## Output
+
+Respond with ONLY the commit message, nothing else.

package/.gut/config.json

@@ -0,0 +1,3 @@
+{
+  "lang": "en"
+}

package/.gut/explain-file.md

@@ -0,0 +1,30 @@
+You are an expert at explaining code in a clear and insightful way.
+
+Analyze the following file and explain what it does, its purpose, and its role in a project.
+
+## File
+
+Path: {{filePath}}
+
+```
+{{content}}
+```
+
+## Focus on
+
+- What this file does (main functionality)
+- Its purpose and role in the codebase
+- Key functions, classes, or components it defines
+- Dependencies and what it interacts with
+- Any important patterns or architecture decisions
+
+## Output
+
+Explain in a way that helps someone quickly understand this file's purpose and how it fits into the larger codebase.
+
+Respond with a JSON object containing:
+- summary: One-line summary
+- purpose: The purpose and role of this code
+- changes: Array of { file, description }
+- impact: What impact or role this has in the project
+- notes: Important considerations or caveats (optional)

package/.gut/explain.md

@@ -0,0 +1,31 @@
+You are an expert at explaining code changes in a clear and insightful way.
+
+Analyze the following {{targetType}} and provide a comprehensive explanation.
+
+## Context
+
+{{context}}
+
+## Diff
+
+```
+{{diff}}
+```
+
+## Focus on
+
+- What the changes accomplish (not just what files changed)
+- WHY these changes were likely made
+- The broader context and purpose
+- Any important implications or side effects
+
+## Output
+
+Explain in a way that helps someone understand not just the "what" but the "why" behind these changes.
+
+Respond with a JSON object containing:
+- summary: One-line summary
+- purpose: The purpose and role of this code
+- changes: Array of { file, description }
+- impact: What impact or role this has in the project
+- notes: Important considerations or caveats (optional)

package/.gut/find.md

@@ -0,0 +1,25 @@
+You are an expert at understanding git history and finding relevant commits.
+
+The user is looking for commits related to: "{{query}}"
+
+## Commits to search
+
+```
+{{commits}}
+```
+
+## Instructions
+
+Find the commits that best match the user's query. Consider:
+- Commit messages that mention similar concepts
+- Related features, bug fixes, or changes
+- Semantic similarity (e.g., "login" matches "authentication")
+
+Return up to {{maxResults}} matching commits, ordered by relevance (most relevant first).
+Only include commits that actually match the query - if none match well, return an empty array.
+
+## Output
+
+Respond with a JSON object containing:
+- matches: Array of { hash, reason }
+- summary: Brief summary of the search results (optional)

package/.gut/merge.md

@@ -0,0 +1,30 @@
+You are an expert at resolving git merge conflicts intelligently.
+
+Analyze the following conflicted file and provide a resolution.
+
+## Context
+
+- File: {{filename}}
+- Merging: {{theirsRef}} into {{oursRef}}
+
+## Conflicted content
+
+```
+{{content}}
+```
+
+## Rules
+
+- Understand the intent of both changes
+- Combine changes when both are valid additions
+- Choose the more complete/correct version when they conflict
+- Preserve all necessary functionality
+- The resolved content should be valid, working code
+- Do NOT include conflict markers (<<<<<<, =======, >>>>>>)
+
+## Output
+
+Respond with a JSON object containing:
+- resolvedContent: The resolved file content
+- explanation: Brief explanation of how the conflict was resolved
+- strategy: "ours" | "theirs" | "combined" | "rewritten"

package/.gut/pr.md

@@ -0,0 +1,36 @@
+You are an expert at writing pull request descriptions.
+
+Generate a clear and informative PR title and description based on the following information.
+
+## Context
+
+- Branch: {{currentBranch}} -> {{baseBranch}}
+- Commits:
+{{commits}}
+
+## Diff summary
+
+```
+{{diff}}
+```
+
+## Rules for title
+
+- Title should be concise (under 72 chars), start with a verb
+
+## Rules for description
+
+- Description should have:
+  - ## Summary section with 2-3 bullet points
+  - ## Changes section listing key modifications
+  - ## Test Plan section (suggest what to test)
+
+## Output
+
+Respond in JSON format:
+```json
+{
+  "title": "...",
+  "body": "..."
+}
+```

package/.gut/review.md

@@ -0,0 +1,24 @@
+You are an expert code reviewer. Analyze the following git diff and provide a structured review.
+
+## Git diff
+
+```
+{{diff}}
+```
+
+## Focus on
+
+- Bugs and potential issues
+- Security vulnerabilities
+- Performance concerns
+- Code style and best practices
+- Suggestions for improvement
+
+## Output
+
+Be constructive and specific. Include line numbers when possible.
+
+Respond with a JSON object containing:
+- summary: Brief overall assessment
+- issues: Array of { severity: "critical"|"warning"|"suggestion", file, line?, message, suggestion? }
+- positives: Array of good practices observed

package/.gut/stash.md

@@ -0,0 +1,20 @@
+You are an expert at summarizing code changes.
+
+Generate a short, descriptive stash name for the following changes.
+
+## Diff
+
+```
+{{diff}}
+```
+
+## Rules
+
+- Start with "WIP: " prefix
+- Keep it under 50 characters total
+- Be specific about what the changes do
+- Use present tense
+
+## Output
+
+Respond with ONLY the stash name, nothing else.

package/.gut/summary.md

@@ -0,0 +1,38 @@
+You are an expert at writing work summaries and reports.
+
+Generate a clear, professional work summary for the following git activity.
+
+## Context
+
+- Author: {{author}}
+- Period: {{period}}
+- Format: {{format}}
+
+## Commits
+
+{{commits}}
+
+{{#diff}}
+## Diff summary
+
+```
+{{diff}}
+```
+{{/diff}}
+
+## Focus on
+
+- What was accomplished (not just listing commits)
+- Group related work together
+- Highlight important achievements
+- Use clear, non-technical language where possible
+- Make it suitable for sharing with team or manager
+
+## Output
+
+Respond with a JSON object containing:
+- title: One-line title for the summary
+- overview: Brief overview of what was accomplished
+- highlights: Array of key accomplishments
+- details: Array of { category, items[] }
+- stats: { commits, filesChanged?, additions?, deletions? } (optional)

package/dist/index.js

@@ -513,7 +513,8 @@ async function generateChangelog(context, options, template) {
     fromRef: context.fromRef,
     toRef: context.toRef,
     commits: commitList,
-    diff: context.diff.slice(0, 8e3)
+    diff: context.diff.slice(0, 8e3),
+    todayDate: (/* @__PURE__ */ new Date()).toISOString().split("T")[0]
   });
   const result = await generateObject({
     model,