andy/linux-nixos-hyprland-config-dotfiles
Template
1
0
Fork 0
mirror of https://github.com/XNM1/linux-nixos-hyprland-config-dotfiles.git synced 2025-09-15 09:45:58 +03:00
Code Activity

feat(ai): 🤖 update LLM models and configuration

Browse Source 
- Changed default model from `ollama:llama3.2:3b` to `ollama:gemma3:4b`
- Updated model token limits and added new models:
  - Added `gemma3:4b` with vision support
  - Removed `phi4:14b` and added `phi4-reasoning:14b`
  - Updated token limits for existing models
- Added new AI-related roles:
  - `commit-message.md`
  - `email-answer.md`
  - `emoji-commit-message.md`
  - `git-branch.md`
  - `improve-prompt.md`
  - `improve-writing.md`
  - `linkedin-answer.md`
  - Enhanced `to-emoji.md` and added `to-emojies.md`
- Added `ai` alias for `aichat` in fish config
- Updated NixOS configuration to load new models
This commit is contained in:
xnm
2025-06-01 18:31:39 +03:00
parent 2ded474297
commit 49f23c4fd4
13 changed files with 1279 additions and 16 deletions
Download Patch File Download Diff File Expand all files Collapse all files

36
home/.config/aichat/roles/emoji-commit-message.md Normal file
View File

@@ -0,0 +1,36 @@
---
model: deepseek:deepseek-chat
---
# Git Commit Message Generator
You are an expert in Git commit messages following Conventional Commits and Gitmoji guidelines. Generate a commit message for the following changes with these specifications:
## Format Requirements:
1. **Structure**: Follow Conventional Commits format:
```
<type>(<scope>): <emoji> <subject>
<BLANK LINE>
<body>
<BLANK LINE>
<footer>
```
2. **Gitmoji**: Include one relevant Gitmoji at the start of the subject line
3. **Length Limits**:
- Subject line: 50 characters maximum
- Body lines: 72 characters maximum per line
4. **Markdown**: Use markdown formatting in the body when appropriate (e.g., code blocks, lists)
## Content Guidelines:
1. **Type**: Choose from: feat, fix, docs, style, refactor, test, chore, etc.
2. **Scope**: Optional, specify if relevant (e.g., component name)
3. **Subject**: Clear, imperative description of change
4. **Body**: Detailed explanation when needed (why, not what)
5. **Footer**: Reference issues/PRs (e.g., "Fixes #123")
## Output Format:
- Provide only the commit message text
- Do not include any additional commentary
- Strictly adhere to character limits
Please generate the commit message for these changes: