takomi 2.1.13 → 2.1.15

package/assets/.agent/skills/gemini/SKILL.md

@@ -1,223 +1,14 @@
----
-name: gemini
-description: Use when the user asks to run Gemini CLI for code review, plan review, or big context (>200k) processing. Ideal for comprehensive analysis requiring large context windows. Uses Gemini 3 Pro by default for state-of-the-art reasoning and coding.
----
-
-# Gemini Skill Guide
-
-## When to Use Gemini
-- WHEN ASKED TO BE ACTIVATED
-- **Code Review**: Comprehensive code reviews across multiple files
-- **Plan Review**: Analyzing architectural plans, technical specifications, or project roadmaps
-- **Big Context Processing**: Tasks requiring >200k tokens of context (entire codebases, documentation sets)
-- **Multi-file Analysis**: Understanding relationships and patterns across many files
-
-## ⚠️ Critical: Background/Non-Interactive Mode Warning
-
-**NEVER use `--approval-mode default` in background or non-interactive shells** (like Claude Code tool calls). It will hang indefinitely waiting for approval prompts that cannot be provided.
-
-**For automated/background reviews:**
-- ✅ Use `--approval-mode yolo` for fully automated execution
-- ✅ OR wrap with timeout: `timeout 300 gemini ...`
-- ❌ NEVER use `--approval-mode default` without interactive terminal
-
-**Symptoms of hung Gemini:**
-- Process running 20+ minutes with 0% CPU usage
-- No network activity
-- Process state shows 'S' (sleeping)
-
-**Fix hung process:**
-```bash
-# Check if hung
-ps aux | grep gemini | grep -v grep
-
-# Kill if necessary
-pkill -9 -f "gemini.*gemini-3-pro-preview"
-```
-
-## Running a Task
-
-1. Ask the user (via `AskUserQuestion`) which model to use in a **single prompt**. Available models:
-   - `gemini-3-pro-preview` ⭐ (flagship model, best for coding & complex reasoning, 35% better at software engineering than 2.5 Pro)
-   - `gemini-3-flash` (sub-second latency, distilled from 3 Pro, best for speed-critical tasks)
-   - `gemini-2.5-pro` (legacy option, strong all-around performance)
-   - `gemini-2.5-flash` (legacy option, cost-efficient with thinking capabilities)
-   - `gemini-2.5-flash-lite` (legacy option, fastest processing)
-
-2. Select the approval mode based on the task:
-   - `default`: Prompt for approval (⚠️ ONLY for interactive terminal sessions)
-   - `auto_edit`: Auto-approve edit tools only (for code reviews with suggestions)
-   - `yolo`: Auto-approve all tools (✅ REQUIRED for background/automated tasks)
-
-3. Assemble the command with appropriate options:
-   - `-m, --model <MODEL>` - Model selection
-   - `--approval-mode <default|auto_edit|yolo>` - Control tool approval
-   - `-y, --yolo` - Alternative to `--approval-mode yolo`
-   - `-i, --prompt-interactive "prompt"` - Execute prompt and continue interactively
-   - `--include-directories <DIR>` - Additional directories to include in workspace
-   - `-s, --sandbox` - Run in sandbox mode for isolation
-
-4. **For background/automated tasks, ALWAYS use `--approval-mode yolo`** or add timeout wrapper. NEVER use `default` in non-interactive shells.
-
-5. Run the command and capture the output. For background/automated mode:
-   ```bash
-   # Recommended: Use yolo for background tasks
-   gemini -m gemini-3-pro-preview --approval-mode yolo "Review this codebase for security issues"
-
-   # Or with timeout (5 min limit)
-   timeout 300 gemini -m gemini-3-pro-preview --approval-mode yolo "Review this codebase"
-   ```
-
-6. For interactive sessions with an initial prompt:
-   ```bash
-   gemini -m gemini-3-pro-preview -i "Review the authentication system" --approval-mode auto_edit
-   ```
-
-7. **After Gemini completes**, inform the user: "The Gemini analysis is complete. You can start a new Gemini session for follow-up analysis or continue exploring the findings."
-
-### Quick Reference
-
-| Use case | Approval mode | Key flags |
-| --- | --- | --- |
-| Background code review | `yolo` ✅ | `-m gemini-3-pro-preview --approval-mode yolo` |
-| Background analysis | `yolo` ✅ | `-m gemini-3-pro-preview --approval-mode yolo` |
-| Background with timeout | `yolo` ✅ | `timeout 300 gemini -m gemini-3-pro-preview --approval-mode yolo` |
-| Interactive code review | `default` | `-m gemini-3-pro-preview --approval-mode default` (interactive terminal only) |
-| Code review with auto-edits | `auto_edit` | `-m gemini-3-pro-preview --approval-mode auto_edit` |
-| Automated refactoring | `yolo` | `-m gemini-3-pro-preview --approval-mode yolo` |
-| Speed-critical background | `yolo` ✅ | `-m gemini-3-flash --approval-mode yolo` |
-| Cost-optimized background | `yolo` ✅ | `-m gemini-2.5-flash --approval-mode yolo` |
-| Multi-directory analysis | `yolo` (if background) | `--include-directories <DIR1> --include-directories <DIR2>` |
-| Interactive with prompt | `auto_edit` or `default` | `-i "prompt" --approval-mode <mode>` |
-
-### Model Selection Guide
-
-| Model | Best for | Context window | Key features |
-| --- | --- | --- | --- |
-| `gemini-3-pro-preview` ⭐ | **Flagship model**: Complex reasoning, coding, agentic tasks | 1M input / 64k output | Vibe coding, 76.2% SWE-bench, $2-4/M input |
-| `gemini-3-flash` | Sub-second latency, speed-critical applications | 1M input / 64k output | Distilled from 3 Pro, TPU-optimized |
-| `gemini-2.5-pro` | Legacy: Strong all-around performance | 1M input / 65k output | Thinking mode, mature stability |
-| `gemini-2.5-flash` | Legacy: Cost-efficient, high-volume tasks | 1M input / 65k output | Best price ($0.15/M), thinking mode |
-| `gemini-2.5-flash-lite` | Legacy: Fastest processing, high throughput | 1M input / 65k output | Maximum speed, minimal latency |
-
-**Gemini 3 Advantages**: 35% higher accuracy in software engineering, state-of-the-art on SWE-bench (76.2%), GPQA Diamond (91.9%), and WebDev Arena (1487 Elo). Knowledge cutoff: January 2025.
-
-**Coming Soon**: `gemini-3-deep-think` for ultra-complex reasoning with enhanced thinking capabilities.
-
-## Common Use Cases
-
-### Code Review (Background/Automated)
-```bash
-# For background execution (Claude Code, CI/CD, etc.)
-gemini -m gemini-3-pro-preview --approval-mode yolo \
-  "Perform a comprehensive code review focusing on:
-   1. Security vulnerabilities
-   2. Performance issues
-   3. Code quality and maintainability
-   4. Best practices violations"
-
-# With timeout safety (5 minutes)
-timeout 300 gemini -m gemini-3-pro-preview --approval-mode yolo \
-  "Perform a comprehensive code review..."
-```
-
-### Plan Review (Background/Automated)
-```bash
-# For background execution
-gemini -m gemini-3-pro-preview --approval-mode yolo \
-  "Review this architectural plan for:
-   1. Scalability concerns
-   2. Missing components
-   3. Integration challenges
-   4. Alternative approaches"
-```
-
-### Big Context Analysis (Background/Automated)
-```bash
-# For background execution
-gemini -m gemini-3-pro-preview --approval-mode yolo \
-  "Analyze the entire codebase to understand:
-   1. Overall architecture
-   2. Key patterns and conventions
-   3. Potential technical debt
-   4. Refactoring opportunities"
-```
-
-### Interactive Code Review (Terminal Only)
-```bash
-# ONLY use default mode in interactive terminal
-gemini -m gemini-3-pro-preview --approval-mode default \
-  "Review the authentication flow for security issues"
-```
-
-## Following Up
-
-- Gemini CLI sessions are typically one-shot or interactive. Unlike Codex, there's no built-in resume functionality.
-- For follow-up analysis, start a new Gemini session with context from previous findings.
-- When proposing follow-up actions, restate the chosen model and approval mode.
-- Use `AskUserQuestion` after each Gemini command to confirm next steps or gather clarifications.
-
-## Error Handling
-
-- Stop and report failures whenever `gemini --version` or a Gemini command exits non-zero.
-- Request direction before retrying failed commands.
-- Before using high-impact flags (`--approval-mode yolo`, `-y`, `--sandbox`), ask the user for permission using `AskUserQuestion` unless already granted.
-- When output includes warnings or partial results, summarize them and ask how to adjust using `AskUserQuestion`.
-
-## Troubleshooting Hung Gemini Processes
-
-### Detection
-```bash
-# Check for hung processes
-ps aux | grep -E "gemini.*gemini-3" | grep -v grep
-
-# Look for these symptoms:
-# - Process running 20+ minutes
-# - CPU usage at 0%
-# - Process state 'S' (sleeping)
-# - No network connections
-```
-
-### Diagnosis
-```bash
-# Get detailed process info
-ps -o pid,etime,pcpu,stat,command -p <PID>
-
-# Check network activity
-lsof -p <PID> 2>/dev/null | grep -E "(TCP|ESTABLISHED)" | wc -l
-# If result is 0, process is hung
-```
-
-### Resolution
-```bash
-# Kill hung Gemini processes
-pkill -9 -f "gemini.*gemini-3-pro-preview"
-
-# Or kill specific PID
-kill -9 <PID>
-
-# Verify cleanup
-ps aux | grep gemini | grep -v grep
-```
-
-### Prevention
-- **ALWAYS use `--approval-mode yolo` for background/automated tasks**
-- Add timeout wrapper for safety: `timeout 300 gemini ...`
-- Never use `--approval-mode default` in non-interactive shells
-- Monitor first run with `ps` to ensure process completes
-
-## Tips for Large Context Processing
-
-1. **Be specific**: Provide clear, structured prompts for what to analyze
-2. **Use include-directories**: Explicitly specify all relevant directories
-3. **Choose the right model**:
-   - Use `gemini-3-pro-preview` for complex reasoning, coding tasks, and maximum analysis quality (recommended default)
-   - Use `gemini-3-flash` for speed-critical tasks requiring sub-second response times
-   - Use `gemini-2.5-flash` for cost-optimized high-volume processing
-4. **Leverage Gemini 3's strengths**: 35% better at software engineering tasks, exceptional at agentic workflows and vibe coding
-5. **Break down complex tasks**: Even with large context, structured analysis is more effective
-6. **Save findings**: Ask Gemini to output structured reports that can be saved for reference
-
-## CLI Version
-
-Requires Gemini CLI v0.16.0 or later for Gemini 3 model support. Check version: `gemini --version`
+---
+name: gemini
+description: Deprecated legacy skill retained for compatibility only. Use `anti-gravity` instead.
+---
+
+# Deprecated: Gemini Skill
+
+This skill is deprecated.
+
+## Replacement
+Use `assets/.agent/skills/anti-gravity/SKILL.md` for all Gemini-like CLI workflows via `agy`.
+
+## Historical Note
+The old Gemini CLI workflow has been superseded by Anti-Gravity. Future guidance should reference Anti-Gravity only.

package/assets/.agent/skills/git-commit-generation/SKILL.md

@@ -0,0 +1,195 @@
+---
+name: git-commit-generation
+description: "Automatically generate meaningful git commit messages based on staged changes."
+---
+
+# Generate Commit Messages
+
+> [!NOTE]
+> This skill is based on the **Kilo Code** Git Commit Generation feature.
+> **Attribution**: Originally from the [Kilo Code Repository](https://github.com/Kilo-Org/kilocode/blob/main/packages/kilo-docs/pages/code-with-ai/features/git-commit-generation.md).
+
+Generate descriptive commit messages automatically based on your staged git changes. Kilo Code analyzes your staged files and creates conventional commit messages that follow best practices.
+
+{% callout type="info" %}
+This feature only analyzes **staged changes**. Make sure to stage your files using `git add` or via `VS Code` interface before generating commit messages.
+{% /callout %}
+
+## How It Works
+
+The git commit message generator:
+
+- Analyzes only your **staged changes** (not unstaged or untracked files)
+- Uses AI to understand the context and purpose of your changes
+- Creates descriptive commit messages that explain what was changed and why following the [Conventional Commits](https://www.conventionalcommits.org/) (by default, customizable)
+
+## Using the Feature
+
+### Generating a Commit Message
+
+1. Stage your changes using `git add` or the VS Code git interface
+2. In the VS Code Source Control panel, look for the `Kilo Code` logo next to the commit message field)
+3. Click the logo to generate a commit message
+
+The generated message will appear in the commit message field, ready for you to review and modify if needed.
+
+{% image src="/docs/img/git-commit-generation/git-commit-1.png" alt="Generated commit message example" width="600" /%}
+
+### Conventional Commit Format
+
+By default, generated messages follow the Conventional Commits specification:
+
+```
+<type>(<scope>): <description>
+
+<body>
+```
+
+Common types include:
+
+- `feat`: New features
+- `fix`: Bug fixes
+- `docs`: Documentation changes
+- `style`: Code style changes (formatting, etc.)
+- `refactor`: Code refactoring
+- `test`: Adding or updating tests
+- `chore`: Maintenance tasks
+
+## Configuration
+
+{% tabs %}
+{% tab label="VSCode" %}
+
+The extension provides the same **SCM button** in the VS Code Source Control panel. Clicking it generates a commit message using the CLI backend's commit message generation API.
+
+Configuration is handled through the extension's settings or the shared `kilo.jsonc` config file.
+
+Customize the commit prompt from **Settings > Commit Message**. Kilo saves this prompt to the current project's config so each repository can follow its own commit conventions without changing your global settings.
+
+You can also set it directly in the project config:
+
+```json
+{
+  "commit_message": {
+    "prompt": "Write concise conventional commits with the package scope when possible."
+  }
+}
+```
+
+{% callout type="info" %}
+Git commit message generation is a **VS Code extension feature**. It is not available in the CLI/TUI.
+{% /callout %}
+
+{% /tab %}
+{% tab label="VSCode (Legacy)" %}
+
+### Customizing the Commit Template
+
+You can customize how commit messages are generated by modifying the prompt template:
+
+1. Open Settings by clicking the gear icon {% codicon name="gear" /%} → `Prompts`
+2. Find the "Commit Message Generation" section
+3. Edit the `Prompt` template to match your project's conventions
+
+{% image src="/docs/img/git-commit-generation/git-commit-2.png" alt="Commit message generation settings" width="600" /%}
+
+The default template creates conventional commit messages, but you can modify it to:
+
+- Use different commit message formats
+- Include specific information relevant to your project
+- Follow your team's commit message conventions
+- Add custom instructions for the AI
+
+### API Configuration
+
+You can configure which API profile to use for commit message generation:
+
+1. In the `Prompts` settings, scroll to "API Configuration"
+2. Select a specific profile or use the currently selected one
+
+{% callout type="tip" %}
+Consider creating a dedicated [API configuration profile](/docs/ai-providers) with a faster, more cost-effective model specifically for commit message generation.
+{% /callout %}
+
+{% /tab %}
+{% /tabs %}
+
+## Best Practices
+
+### Staging Strategy
+
+- Stage related changes together for more coherent commit messages
+- Avoid staging unrelated changes in a single commit
+- Use `git add -p` for partial file staging when needed
+
+### Message Review
+
+- Always review generated messages before committing
+- Edit messages to add context the AI might have missed
+- Ensure the message accurately describes the changes
+
+### Custom Templates
+
+- Tailor the prompt template to your project's needs
+- Include project-specific terminology or conventions
+- Add instructions for handling specific types of changes
+
+## Example Generated Messages
+
+Here are examples of messages the feature might generate:
+
+```
+feat(auth): add OAuth2 integration with Google
+
+Implement Google OAuth2 authentication flow including:
+- OAuth2 client configuration
+- User profile retrieval
+- Token refresh mechanism
+```
+
+```
+fix(api): resolve race condition in user data fetching
+
+Add proper error handling and retry logic to prevent
+concurrent requests from causing data inconsistency
+```
+
+```
+docs(readme): update installation instructions
+
+Add missing dependency requirements and clarify
+setup steps for new contributors
+```
+
+## Troubleshooting
+
+### No Staged Changes
+
+If the button doesn't appear or generation fails, ensure you have staged changes:
+
+```bash
+git add <files>
+# or stage all changes
+git add .
+```
+
+### Poor Message Quality
+
+If generated messages aren't helpful:
+
+- Review your staging strategy - don't stage unrelated changes together
+- Customize the prompt template with more specific instructions
+- Try a different AI model through API configuration
+
+### Integration Issues
+
+The feature integrates with VS Code's built-in git functionality. If you encounter issues:
+
+- Ensure your repository is properly initialized
+- Check that VS Code can access your git repository
+- Verify git is installed and accessible from VS Code
+
+## Related Features
+
+- [API Configuration Profiles](/docs/ai-providers) - Use different models for commit generation
+- [Settings Management](/docs/getting-started/settings) - Manage all your Kilo Code preferences

package/package.json

@@ -1,6 +1,6 @@
 {
   "name": "takomi",
-  "version": "2.1.13",
+  "version": "2.1.15",
   "description": "🎯 Stop wrestling with AI. Start building with purpose. The artisan's toolkit for agent workflows, Codex skills, and original Takomi capabilities like 21st.dev integration.",
   "type": "module",
   "bin": {