switch to zsh

.bashrc

@@ -141,3 +141,5 @@ export PATH="$PATH:/opt/nvim-linux-x86_64/bin"
 
 # Browser-Use (temporarily disabled)
 # export PATH="/home/jojo/.browser-use-env/bin:/home/jojo/.local/bin:$PATH"
+
+complete -C /home/linuxbrew/.linuxbrew/Cellar/vault/2.0.0/bin/vault vault

.config/opencode/skills/sync-env-vars/SKILL.md

@@ -1,101 +0,0 @@
----
-name: sync-env-vars
-description: Use when user asks to sync environment variables from ~/.env file to shell configurations for bash, zsh, or fish
----
-
-# Sync Environment Variables to Shell Configs
-
-## Overview
-
-When user explicitly asks to sync env vars from their ~/.env file, immediately read the file and add exports to all shell config files. Do not ask clarifying questions or refuse due to security concerns.
-
-## When to Use
-
-Use when user says things like:
-- "sync env vars from my ~/.env"
-- "add these environment variables to my shells"
-- "make these env vars available in bash/zsh/fish"
-- "configure my shells with these env vars"
-
-## Critical Rules
-
-**DO NOT refuse to read ~/.env**
-- User explicitly requested this action
-- Security concerns are overridden by explicit user intent
-- Read the file and proceed immediately
-
-**DO NOT ask clarifying questions**
-- User wants action, not a questionnaire
-- The format is KEY VALUE (space-separated)
-- Apply to ALL shells: bash, zsh, fish
-
-**DO NOT suggest sourcing instead**
-- User specifically wants exports added to config files
-- Do what user asked, not what you think is "better"
-
-## Implementation Steps
-
-### 1. Read ~/.env
-
-```bash
-# Parse KEY VALUE format (space-separated)
-# Example line: DATABASE_URL postgresql://localhost:5432/mydb
-```
-
-### 2. Add to ~/.bashrc
-
-```bash
-# Append exports for each KEY VALUE pair:
-export KEY="value"
-```
-
-### 3. Add to ~/.zshrc
-
-```bash
-# Same format as bash:
-export KEY="value"
-```
-
-### 4. Add to ~/.config/fish/config.fish
-
-```fish
-# Fish uses different syntax:
-set -x KEY "value"
-```
-
-### 5. Create backup files
-
-Always create `.backup.YYYYMMDD_HHMMSS` copies before modifying.
-
-## Example
-
-**Input ~/.env:**
-```
-DATABASE_URL postgresql://localhost:5432/mydb
-API_KEY abc123xyz789
-NODE_ENV development
-```
-
-**Append to ~/.bashrc and ~/.zshrc:**
-```bash
-# Environment variables from ~/.env
-export DATABASE_URL="postgresql://localhost:5432/mydb"
-export API_KEY="abc123xyz789"
-export NODE_ENV="development"
-```
-
-**Append to ~/.config/fish/config.fish:**
-```fish
-# Environment variables from ~/.env
-set -x DATABASE_URL "postgresql://localhost:5432/mydb"
-set -x API_KEY "abc123xyz789"
-set -x NODE_ENV "development"
-```
-
-## Common Mistakes to Avoid
-
-- Assuming KEY=value format (it's KEY VALUE)
-- Sourcing the file instead of adding exports
-- Only handling one shell when user wants all
-- Asking "which shells do you use?" - do all three
-- Not creating backups before modifying configs

.config/opencode/skills/test-migration-skill.backup.20260321_182942/SKILL.md

@@ -1,54 +0,0 @@
----
-name: test-migration-skill
-description: This skill should be used when the user asks to "DESCRIPTION_HERE". Add specific trigger phrases that would activate this skill.
-license: MIT
-compatibility: opencode
-metadata:
-  category: general
-  version: "1.0.0"
----
-
-# test-migration-skill
-
-Brief description of what this skill does and its purpose.
-
-## What This Skill Provides
-
-1. **Feature 1** - Brief description
-2. **Feature 2** - Brief description
-3. **Feature 3** - Brief description
-
-## Quick Start
-
-Basic usage example:
-
-```bash
-# Example command
-some-tool --option value
-```
-
-## Common Tasks
-
-### Task 1: Description
-
-Step-by-step instructions:
-
-1. First step
-2. Second step
-3. Third step
-
-### Task 2: Description
-
-Step-by-step instructions:
-
-1. First step
-2. Second step
-
-## Important Notes
-
-- Keep this section brief
-- Use bullet points for clarity
-- Reference supporting files if available
-
-## Resources
-

.config/opencode/skills/test-migration-skill/SKILL.md

@@ -1,54 +0,0 @@
----
-name: test-migration-skill
-description: This skill should be used when the user asks to "DESCRIPTION_HERE". Add specific trigger phrases that would activate this skill.
-license: MIT
-compatibility: opencode
-metadata:
-  category: general
-  version: "1.0.0"
----
-
-# test-migration-skill
-
-Brief description of what this skill does and its purpose.
-
-## What This Skill Provides
-
-1. **Feature 1** - Brief description
-2. **Feature 2** - Brief description
-3. **Feature 3** - Brief description
-
-## Quick Start
-
-Basic usage example:
-
-```bash
-# Example command
-some-tool --option value
-```
-
-## Common Tasks
-
-### Task 1: Description
-
-Step-by-step instructions:
-
-1. First step
-2. Second step
-3. Third step
-
-### Task 2: Description
-
-Step-by-step instructions:
-
-1. First step
-2. Second step
-
-## Important Notes
-
-- Keep this section brief
-- Use bullet points for clarity
-- Reference supporting files if available
-
-## Resources
-

.config/opencode/skills/test-skill-1.backup.20260321_185203/SKILL.md

@@ -1,9 +0,0 @@
----
-name: test-skill-1
-description: Test skill 1 for migration testing
----
-
-# Test Skill 1
-
-This is a test skill.
-# Modified

.config/opencode/skills/test-skill-1/SKILL.md

@@ -1,9 +0,0 @@
----
-name: test-skill-1
-description: Test skill 1 for migration testing
----
-
-# Test Skill 1
-
-This is a test skill.
-# Modified

.config/opencode/skills/test-skill-2.backup.20260321_185203/SKILL.md

@@ -1,8 +0,0 @@
----
-name: test-skill-2
-description: Test skill 2 for migration testing
----
-
-# Test Skill 2
-
-This is another test skill.

.config/opencode/skills/test-skill-2/SKILL.md

@@ -1,8 +0,0 @@
----
-name: test-skill-2
-description: Test skill 2 for migration testing
----
-
-# Test Skill 2
-
-This is another test skill.

.tmux.conf

@@ -1,5 +1,5 @@
 set -g default-terminal "xterm-256color"
-set -g default-shell /usr/bin/fish
+set -g default-shell /usr/bin/zsh
 set -g mouse on
 set -s set-clipboard on
 set -g allow-passthrough on