gut-cli 0.1.19 → 0.1.21

package/.gut/branch.md

@@ -1,18 +1,6 @@
 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}}
+Generate a clean, descriptive branch name based on the description. If a branch type or issue number is available, incorporate them appropriately.
 
 ## Rules
 

package/.gut/changelog.md

@@ -1,18 +1,6 @@
 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}}
-```
+Generate a changelog entry based on the commits and diff. Use the provided fromRef, toRef, and todayDate for the release date.
 
 ## Format
 

package/.gut/checkout.md

@@ -1,14 +1,6 @@
-# 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}}
-```
+Analyze the git diff and generate a clean, descriptive branch name that captures the essence of the changes.
 
 ## Branch Naming Convention
 

package/.gut/commit.md

@@ -1,12 +1,6 @@
 You are an expert at writing git commit messages.
 
-Analyze the following git diff and generate a concise, meaningful commit message.
-
-## Git diff
-
-```
-{{diff}}
-```
+Analyze the git diff and generate a concise, meaningful commit message.
 
 ## Rules
 
@@ -16,7 +10,3 @@ Analyze the following git diff and generate a concise, meaningful commit message
 - 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/explain-file.md

@@ -1,14 +1,6 @@
 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}}
-```
+Analyze the file content and explain what it does, its purpose, and its role in a project.
 
 ## Focus on
 

package/.gut/explain.md

@@ -1,16 +1,6 @@
 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}}
-```
+Analyze the changes based on the target type (commit, PR, file changes, etc.) and diff.
 
 ## Focus on
 

package/.gut/find.md

@@ -1,12 +1,6 @@
 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}}
-```
+Search through the commits to find those matching the user's query.
 
 ## Instructions
 
@@ -15,7 +9,7 @@ Find the commits that best match the user's query. Consider:
 - 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).
+Return commits ordered by relevance (most relevant first).
 Only include commits that actually match the query - if none match well, return an empty array.
 
 ## Output

package/.gut/gitignore.md

@@ -1,26 +1,6 @@
 You are an expert at creating .gitignore files.
 
-Analyze the following project structure and configuration files to generate an appropriate .gitignore file.
-
-## Project Structure
-
-```
-{{files}}
-```
-
-{{#configFiles}}
-## Detected Config Files
-
-{{configFiles}}
-{{/configFiles}}
-
-{{#existingGitignore}}
-## Existing .gitignore
-
-```
-{{existingGitignore}}
-```
-{{/existingGitignore}}
+Analyze the project structure and configuration files to generate an appropriate .gitignore file.
 
 ## Rules
 
@@ -33,9 +13,7 @@ Analyze the following project structure and configuration files to generate an a
 - Include log files and temporary files
 - Do NOT ignore files that should be tracked (source code, configs, etc.)
 - Keep the file organized with comments for each section
-{{#existingGitignore}}
-- Preserve any project-specific patterns from the existing .gitignore
-{{/existingGitignore}}
+- If an existing .gitignore is provided, preserve project-specific patterns from it
 
 ## Output
 

package/.gut/merge.md

@@ -1,17 +1,6 @@
 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}}
-```
+Analyze the conflicted file content and provide a resolution.
 
 ## Rules
 

package/.gut/pr.md

@@ -1,18 +1,6 @@
 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}}
-```
+Generate a clear and informative PR title and description based on the branch information, commits, and diff.
 
 ## Rules for title
 
@@ -24,13 +12,3 @@ Generate a clear and informative PR title and description based on the following
   - ## 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

@@ -1,10 +1,4 @@
-You are an expert code reviewer. Analyze the following git diff and provide a structured review.
-
-## Git diff
-
-```
-{{diff}}
-```
+You are an expert code reviewer. Analyze the git diff and provide a structured review.
 
 ## Focus on
 
@@ -14,11 +8,4 @@ You are an expert code reviewer. Analyze the following git diff and provide a st
 - 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

@@ -1,12 +1,6 @@
 You are an expert at summarizing code changes.
 
-Generate a short, descriptive stash name for the following changes.
-
-## Diff
-
-```
-{{diff}}
-```
+Generate a short, descriptive stash name based on the diff.
 
 ## Rules
 

package/.gut/summary.md

@@ -1,24 +1,6 @@
 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}}
+Generate a clear, professional work summary based on the git activity.
 
 ## Focus on