claude-termux 1.0.1 → 1.0.3

package/TERMUX.md

@@ -1,204 +1,36 @@
-# Claude Termux - AI CLI Configuration for Android
+# Claude Termux - Android Configuration
 
-Konfigurasi lengkap untuk menjalankan Claude Code dan Gemini CLI di Termux Android.
+Claude Code & Gemini CLI configuration optimized for Termux Android.
 
 ## Installation
 
-### Via NPM (Recommended)
-
 ```bash
 npm install -g claude-termux
 ```
 
-### Via curl
-
-```bash
-curl -fsSL https://raw.githubusercontent.com/zesbe/termux-config/main/install.sh | bash
-```
-
-### Manual Installation
-
-```bash
-git clone https://github.com/zesbe/termux-config.git
-cd termux-config
-./install.sh
-```
-
-## Prerequisites
-
-Pastikan sudah install Claude Code dan/atau Gemini CLI:
-
-```bash
-# Claude Code
-npm install -g @anthropic-ai/claude-code
-
-# Gemini CLI
-npm install -g @google/gemini-cli
-```
-
-## What Gets Installed
-
-### Claude Code (`~/.claude/`)
-
-| Component | Path |
-|-----------|------|
-| Home | `/data/data/com.termux/files/home/.claude/` |
-| Main Config | `/data/data/com.termux/files/home/.claude.json` |
-| Settings | `/data/data/com.termux/files/home/.claude/settings.local.json` |
-| Plugins | `/data/data/com.termux/files/home/.claude/plugins/` |
-| Global Instructions | `/data/data/com.termux/files/home/.claude/CLAUDE.md` |
-| MCP Config | `/data/data/com.termux/files/home/.mcp.json` |
-
-### Gemini CLI (`~/.gemini/`)
-
-| Component | Path |
-|-----------|------|
-| Home | `/data/data/com.termux/files/home/.gemini/` |
-| Superpowers | `/data/data/com.termux/files/home/.gemini/superpowers/` |
-| Settings | `/data/data/com.termux/files/home/.gemini/settings.json` |
-| MCP Config | `/data/data/com.termux/files/home/.gemini/mcp.json` |
-| Instructions | `/data/data/com.termux/files/home/.gemini/GEMINI.md` |
-
-## Features
-
-### Agents (14)
-- `proactive-mode` - Autonomous execution without permission prompts
-- `code-generator` - Generate boilerplate and scaffolding
-- `code-reviewer` - Review code against standards
-- `security-auditor` - Security vulnerability analysis
-- `test-generator` - Generate test suites
-- `doc-generator` - Generate documentation
-- `api-tester` - API testing (functional, load, security)
-- `performance-analyzer` - Performance optimization
-- `accessibility-reviewer` - Accessibility compliance
-- `component-generator` - UI component generation
-- `migration-generator` - Database migration scripts
-- `readme-generator` - README documentation
-- `terraform-generator` - Infrastructure as code
-- `ai-prompt-optimizer` - Optimize AI prompts
+## What's Included
 
-### Skills (34+)
-- `api-development` - REST/GraphQL API patterns
-- `database-development` - SQL, migrations, optimization
-- `frontend-design` - UI/UX best practices
-- `test-driven-development` - TDD methodology
-- `systematic-debugging` - Debug methodology
-- `code-quality` - Code review and refactoring
-- `error-handling` - Exception handling patterns
-- `brainstorming` - Design ideation
-- `writing-plans` - Implementation planning
-- `executing-plans` - Plan execution
-- And many more...
+- **14 Agents** - proactive-mode, code-generator, security-auditor, etc.
+- **48 Skills** - database-design, ui-ux-pro-max, systematic-debugging, etc.
+- **8 Commands** - /brainstorm, /write-plan, /execute-plan, /clean, /worktrees, etc.
+- **7 MCP Servers** - context7, exa, memory, filesystem, fetch, sequential-thinking, web-reader
 
-### Commands (3)
-- `/brainstorm` - Interactive design refinement
-- `/write-plan` - Create implementation plans
-- `/execute-plan` - Execute plans with checkpoints
+## Termux Paths
 
-### MCP Servers (6)
-- `context7` - Up-to-date documentation context
-- `exa` - Web search and crawling
-- `sequential-thinking` - Step-by-step reasoning
-- `memory` - Knowledge graph persistence
-- `filesystem` - File system access
-- `fetch` - Web fetching
+Files are installed to:
+- Claude: `/data/data/com.termux/files/home/.claude/`
+- Gemini: `/data/data/com.termux/files/home/.gemini/`
 
 ## Bypass Permissions
 
-Both Claude and Gemini are configured for bypass mode:
-
-### Claude Code
-```bash
-# Bypass mode enabled in settings.local.json
-claude --dangerously-skip-permissions
-```
-
-### Gemini CLI
-```bash
-# YOLO mode enabled in settings.json
-gemini --yolo
-# atau
-gemini --approval-mode=yolo
-```
-
-## Termux-Specific Notes
+Auto-approve is enabled by default via `settings.local.json`.
 
-### Path Differences
-
-| Standard Linux | Termux Android |
-|----------------|----------------|
-| `~/.claude/` | `/data/data/com.termux/files/home/.claude/` |
-| `~/.gemini/` | `/data/data/com.termux/files/home/.gemini/` |
-| `/home/user/` | `/data/data/com.termux/files/home/` |
-
-### SSH Access from Laptop
-
-```bash
-# Start SSH server in Termux
-sshd
-
-# From laptop
-ssh -p 8022 user@phone-ip
-
-# Copy file
-scp -P 8022 local-file user@phone-ip:/data/data/com.termux/files/home/
-```
-
-### Storage Access
+## Update
 
 ```bash
-# Grant storage permission
-termux-setup-storage
-
-# Access internal storage
-ls ~/storage/shared/
-```
-
-## Updating
-
-```bash
-# NPM
 npm update -g claude-termux
-
-# curl
-curl -fsSL https://raw.githubusercontent.com/zesbe/termux-config/main/install.sh | bash
-```
-
-## Troubleshooting
-
-### Claude not finding config
-```bash
-# Check if config exists
-ls -la ~/.claude/
-cat ~/.claude/settings.local.json
-
-# Reinstall
-npm uninstall -g claude-termux
-npm install -g claude-termux
-```
-
-### Gemini not finding superpowers
-```bash
-# Check superpowers directory
-ls -la ~/.gemini/superpowers/
-
-# Verify settings
-cat ~/.gemini/settings.json
-```
-
-### MCP servers not loading
-```bash
-# Check MCP config
-cat ~/.mcp.json  # for Claude
-cat ~/.gemini/mcp.json  # for Gemini
-
-# Restart terminal
-exit
-# Open new Termux session
 ```
 
-## Repository
+## Source
 
-- GitHub: https://github.com/zesbe/termux-config
-- Issues: https://github.com/zesbe/termux-config/issues
-- NPM: https://www.npmjs.com/package/claude-termux
+https://github.com/zesbe/ClaudeAll

package/commands/clean.md

@@ -0,0 +1,69 @@
+---
+description: Clean the codebase or current working task in focus via Prettier, Import Sorter, ESLint, and TypeScript Compiler
+---
+
+# Code Quality Cleanup
+
+You are a code quality specialist. When provided with $ARGUMENTS (file paths or directories), systematically clean and optimize the code for production readiness. If no arguments provided, focus on currently open or recently modified files.
+
+## Your Cleanup Process:
+
+**Step 1: Analyze Target Scope**
+- If $ARGUMENTS provided: Focus on specified files/directories
+- If no arguments: Check git status for modified files and currently open files
+- Identify file types and applicable cleanup tools
+
+**Step 2: Execute Cleanup Pipeline**
+Perform these actions in order:
+
+1. **Remove Debug Code**
+   - Strip console.log, debugger statements, and temporary debugging code
+   - Remove commented-out code blocks
+   - Clean up development-only imports
+
+2. **Format Code Structure**
+   - Run Prettier (if available) or apply consistent formatting
+   - Ensure proper indentation and spacing
+   - Standardize quote usage and trailing commas
+
+3. **Optimize Imports**
+   - Sort imports alphabetically
+   - Remove unused imports
+   - Group imports by type (libraries, local files)
+   - Use absolute imports where configured
+
+4. **Fix Linting Issues**
+   - Resolve ESLint/TSLint errors and warnings
+   - Apply auto-fixable rules
+   - Report manual fixes needed
+
+5. **Type Safety Validation**
+   - Run TypeScript compiler checks
+   - Fix obvious type issues
+   - Add missing type annotations where beneficial
+
+6. **Comment Optimization**
+   - Remove redundant or obvious comments
+   - Improve unclear comments
+   - Ensure JSDoc/docstring completeness for public APIs
+
+**Step 3: Present Cleanup Report**
+
+## Cleanup Results
+
+### Files Processed
+- [List of files that were cleaned]
+
+### Actions Taken
+- **Debug Code Removed**: [Number of console.logs, debuggers removed]
+- **Formatting Applied**: [Files formatted]
+- **Imports Optimized**: [Unused imports removed, sorting applied]
+- **Linting Issues Fixed**: [Auto-fixed issues count]
+- **Type Issues Resolved**: [TypeScript errors fixed]
+- **Comments Improved**: [Redundant comments removed, unclear ones improved]
+
+### Manual Actions Needed
+- [List any issues that require manual intervention]
+
+### Quality Improvements
+- [Summary of overall code quality improvements made]

package/commands/commit-openagents.md

@@ -0,0 +1,131 @@
+---
+description: Smart commit command with automatic validation and conventional commits
+---
+
+# Smart Commit Command
+
+You are an AI agent that helps create well-formatted git commits. This command handles the complete commit workflow including validation, testing, and pushing changes.
+
+## Instructions for Agent
+
+When the user runs this command, execute the following workflow:
+
+### 1. **Smart Repo Analysis (Automatic)**
+
+**Before doing anything, analyze the repo state:**
+
+```bash
+# Check current branch and status
+git status
+git branch --show-current
+
+# Check recent commits for style
+git log --oneline -5
+```
+
+### 2. **Analyze Changes**
+- Run `git status` to see all untracked files
+- Run `git diff` to see both staged and unstaged changes
+- Run `git log --oneline -5` to see recent commit style
+- Identify the scope of changes
+
+### 3. **Stage Files Intelligently**
+**Auto-stage based on change type:**
+- If modifying agents → stage `agents/`
+- If modifying skills → stage `skills/`
+- If modifying commands → stage `commands/`
+- If modifying context → stage `context/`
+- If modifying hooks → stage `hooks/`
+- If modifying docs → stage `docs/`
+- If modifying CI/CD → stage `.github/workflows/`
+- If user provides specific files → stage only those
+
+**Never auto-stage:**
+- `node_modules/`
+- `.env` files
+- Temporary directories
+
+### 4. **Generate Commit Message**
+
+**Follow Conventional Commits (NO EMOJIS):**
+```
+<type>(<scope>): <description>
+
+[optional body]
+```
+
+**Types:**
+- `feat` - New features
+- `fix` - Bug fixes
+- `refactor` - Code restructuring
+- `test` - Test additions
+- `docs` - Documentation updates
+- `chore` - Maintenance tasks
+- `ci` - CI/CD changes
+- `perf` - Performance improvements
+
+**Scopes:**
+- `agents` - Agent changes
+- `skills` - Skill changes
+- `commands` - Command changes
+- `context` - Context file changes
+- `hooks` - Hook changes
+- `mcp` - MCP server changes
+- `docs` - Documentation changes
+
+**Examples:**
+```
+feat(agents): add new code-generator agent
+fix(skills): correct brainstorming skill logic
+refactor(commands): split commit command into modules
+docs(readme): update installation instructions
+chore(deps): upgrade dependencies
+```
+
+### 5. **Execute Commit**
+```bash
+git add <relevant-files>
+git commit -m "<type>(<scope>): <description>"
+git status  # Verify commit succeeded
+```
+
+### 6. **Post-Commit Actions**
+
+**Ask user:**
+```
+✅ Commit created: <commit-hash>
+📝 Message: <commit-message>
+
+Would you like to:
+1. Push to remote (git push origin <branch>)
+2. Create another commit
+3. Done
+```
+
+## Error Handling
+
+### If No Changes Detected
+```
+ℹ️ No changes to commit. Working tree is clean.
+
+Recent commits:
+<git log --oneline -3>
+```
+
+### If Merge Conflicts
+```
+⚠️ Merge conflicts detected. Please resolve conflicts first.
+
+Conflicted files:
+<list-files>
+```
+
+## Success Criteria
+
+A successful commit should:
+- ✅ Follow conventional commit format (NO EMOJIS)
+- ✅ Have appropriate scope
+- ✅ Be atomic (single purpose)
+- ✅ Have clear, concise message
+- ✅ Not include sensitive information
+- ✅ Not include generated files

package/commands/indexes.md

@@ -0,0 +1,32 @@
+---
+description: Analyze database queries and recommend missing indexes
+argument-hint: Optional - specific tables or queries to analyze
+---
+
+# Database Index Analysis
+
+**Scope:** `$ARGUMENTS` (or entire codebase if not specified)
+
+Scan whole codebase and tell me what indexes are missing.
+
+## 📚 **DOCUMENTATION REQUIREMENTS**
+
+**Create comprehensive database analysis documentation at:**
+- `docs/tasks/backend/DD-MM-YYYY/<semantic-db-id>/`
+
+**Documentation Structure:**
+- `README.md` - Database analysis overview and objectives
+- `query-analysis.md` - Detailed query performance analysis
+- `index-recommendations.md` - Missing indexes and impact analysis
+- `performance-metrics.md` - Before/after performance comparisons
+- `implementation-plan.md` - Index creation strategy and migration plan
+- `monitoring-setup.md` - Performance monitoring and alerting
+
+**Semantic Database Task ID Examples:**
+- `user-query-optimization`
+- `order-performance-indexes`
+- `search-query-acceleration`
+- `relationship-index-analysis`
+- `slow-query-investigation`
+
+Please analyze all database queries, identify missing indexes, and document recommendations according to the standards above.

package/commands/worktrees.md

@@ -0,0 +1,87 @@
+---
+description: Manage git worktrees for parallel development workflows
+---
+
+# Git Worktree Management
+
+You are a git workflow specialist. When provided with $ARGUMENTS, manage git worktrees to enable parallel development on multiple branches. Common arguments: "create", "list", "cleanup", or specific branch names.
+
+## Your Worktree Management Process:
+
+**Step 1: Assess Current State**
+- Check if git worktrees are already in use with `git worktree list`
+- Verify GitHub CLI is available and authenticated for PR operations
+- Identify the main repository directory structure
+- Check for existing `./tree` directory or similar worktree organization
+
+**Step 2: Execute Worktree Operations**
+
+### Create Worktrees for All Open PRs
+When $ARGUMENTS includes "prs" or "all":
+1. Run `gh pr list --json headRefName,title,number` to get open PRs
+2. For each PR branch:
+   - Create directory structure: `./tree/[branch-name]`
+   - Execute `git worktree add ./tree/[branch-name] [branch-name]`
+   - Handle branch names with slashes by creating nested directories
+3. Report successful worktree creation
+
+### Create Worktree for Specific Branch
+When $ARGUMENTS specifies a branch name:
+1. Check if branch exists locally or remotely
+2. Create worktree at `./tree/[branch-name]`
+3. If branch doesn't exist, offer to create it with `git worktree add -b [branch-name] ./tree/[branch-name]`
+
+### Create New Branch with Worktree
+When $ARGUMENTS includes "new" and a branch name:
+1. Prompt for base branch (default: main/master)
+2. Create new branch and worktree simultaneously
+3. Set up proper tracking if needed
+
+### List and Status Check
+When $ARGUMENTS includes "list" or "status":
+1. Show all current worktrees with `git worktree list`
+2. Check status of each worktree
+3. Identify any stale or problematic worktrees
+
+### Cleanup Operations
+When $ARGUMENTS includes "cleanup":
+1. Identify branches that no longer exist remotely
+2. Remove corresponding worktrees safely
+3. Clean up empty directories in `./tree`
+
+**Step 3: Present Worktree Report**
+
+## Worktree Management Results
+
+### Operation Summary
+- **Command**: [What operation was performed]
+- **Target**: [Specific branches or "all open PRs"]
+- **Location**: [Worktree directory structure used]
+
+### Active Worktrees
+```
+[List of active worktrees with format:]
+/path/to/main/repo          [main branch] (main repository)
+/path/to/tree/feature-123   [feature-123] (worktree)
+/path/to/tree/bugfix-456    [bugfix-456]  (worktree)
+```
+
+### Actions Completed
+- **Created**: [Number of new worktrees created]
+- **Removed**: [Number of stale worktrees cleaned up]
+- **Skipped**: [Worktrees that already existed]
+
+### Directory Structure
+```
+project/
+├── main repository files
+└── tree/
+    ├── feature-branch-1/
+    ├── feature-branch-2/
+    └── bugfix-branch/
+```
+
+### Next Steps
+- **To work on a branch**: `cd tree/[branch-name]`
+- **To switch branches**: Use different worktree directories
+- **To clean up later**: Use `/worktrees cleanup` command

package/commands/writing-plans.md

@@ -0,0 +1,13 @@
+---
+description: Create a detailed implementation plan
+argument-hint: [design-doc-path]
+---
+
+# Write Implementation Plan
+
+**User Input:** $ARGUMENTS
+
+**Instructions:**
+1.  **Target:** I want to create a detailed implementation plan.
+2.  **Action:** Please **invoke/use the `writing-plans` skill** immediately.
+3.  Refer to the design document or requirements in "$ARGUMENTS" (if provided).

package/context/README.md

@@ -0,0 +1,27 @@
+# Context Files
+
+Context files provide domain knowledge, process documentation, and templates that agents can reference.
+
+## Structure
+
+```
+context/
+├── core/           # Core system knowledge
+├── development/    # Development practices and patterns
+├── data/           # Data handling and processing
+├── content/        # Content creation guidelines
+├── project/        # Project management context
+├── ui/             # UI/UX design patterns
+└── templates/      # Reusable templates
+```
+
+## Usage
+
+Agents automatically load relevant context based on the task type. You can also explicitly reference context files in prompts.
+
+## Adding Context
+
+1. Create a new .md file in the appropriate subdirectory
+2. Follow the standard format with frontmatter
+3. Keep files focused (50-200 lines)
+4. Include examples where helpful

package/mcp.json

@@ -29,6 +29,11 @@
     "fetch": {
       "command": "npx",
       "args": ["-y", "@wordbricks/fetch-mcp@latest"]
+    },
+    "web-reader": {
+      "command": "npx",
+      "args": ["-y", "@modelcontextprotocol/server-web-reader"],
+      "description": "Read and convert web content to LLM-friendly format"
     }
   }
 }

package/package.json

@@ -1,12 +1,11 @@
 {
   "name": "claude-termux",
-  "version": "1.0.1",
+  "version": "1.0.3",
   "description": "Claude Code & Gemini CLI configuration for Termux Android - agents, skills, commands, MCP servers",
   "main": "postinstall.js",
   "scripts": {
     "postinstall": "node postinstall.js"
   },
-  "bin": {},
   "keywords": [
     "claude",
     "claude-code",
@@ -24,16 +23,17 @@
   "license": "MIT",
   "repository": {
     "type": "git",
-    "url": "git+https://github.com/zesbe/termux-config.git"
+    "url": "git+https://github.com/zesbe/ClaudeAll.git"
   },
   "bugs": {
-    "url": "https://github.com/zesbe/termux-config/issues"
+    "url": "https://github.com/zesbe/ClaudeAll/issues"
   },
-  "homepage": "https://github.com/zesbe/termux-config#readme",
+  "homepage": "https://github.com/zesbe/ClaudeAll#readme",
   "files": [
     "agents/**",
     "skills/**",
     "commands/**",
+    "context/**",
     "hooks/**",
     "plugins/**",
     "lib/**",