superacli 1.13.0 → 1.15.0

package/.beads/metadata.json

@@ -1,4 +0,0 @@
-{
-  "database": "beads.db",
-  "jsonl_export": "issues.jsonl"
-}

package/CONTRIBUTING.md

@@ -1,274 +0,0 @@
-# Contributing to supercli
-
-Welcome to supercli! We're excited that you're interested in contributing. This guide will help you understand how to contribute effectively.
-
-## Introduction
-
-supercli is a universal capability router that bridges humans and AI agents to multiple CLI tools, APIs, MCP servers, and workflows. We welcome contributions in many forms:
-
-- **Code improvements** - Bug fixes, new features, performance improvements
-- **Documentation** - Improving guides, examples, and API references
-- **Plugin development** - Creating new harnesses for CLI tools
-- **Issue reporting** - Helping us identify and reproduce problems
-- **Community support** - Answering questions and helping others
-
-## Getting Started
-
-### Prerequisites
-
-Before contributing, ensure you have:
-
-- [Node.js](https://nodejs.org/) (LTS version recommended)
-- [npm](https://www.npmjs.com/) or [pnpm](https://pnpm.io/)
-- Git for version control
-- Any CLI tools you want to create plugins for
-
-### Setting Up Your Development Environment
-
-```bash
-# Fork the repository on GitHub
-# Clone your fork
-git clone https://github.com/YOUR_USERNAME/supercli.git
-cd supercli
-
-# Install dependencies
-npm install
-
-# Copy environment configuration
-cp .env.example .env
-
-# Run tests to verify setup
-npm test
-```
-
-### Finding Things to Work On
-
-- Check the [Issues](https://github.com/javimosch/supercli/issues) for bugs and feature requests
-- Look for issues tagged with `good first issue` for beginner-friendly contributions
-- Review the [Project Board](https://github.com/javimosch/supercli/projects) for planned work
-- Propose new features by opening a discussion
-
-## Issue Reporting
-
-### Bug Reports
-
-When reporting bugs, include:
-
-1. **Clear title** describing the issue
-2. **Steps to reproduce** - Be specific and detailed
-3. **Expected vs actual behavior** - What you expected vs what happened
-4. **Environment details** - OS, Node.js version, supercli version
-5. **Relevant logs** - Error messages, stack traces
-6. **Minimal reproduction** - If possible, a small code snippet that reproduces the issue
-
-### Feature Requests
-
-For new features:
-
-1. **Describe the feature** - What should happen and why it's useful
-2. **Use cases** - Who benefits and how they'll use it
-3. **Alternatives considered** - What other approaches did you consider?
-4. **Implementation suggestions** - If you have ideas, share them
-
-### Issue Template Example
-
-```markdown
-## Description
-[A clear description of the issue or feature request]
-
-## Steps to Reproduce (for bugs)
-1. Run '...'
-2. Execute '...'
-3. See error
-
-## Expected Behavior
-[What you expected to happen]
-
-## Actual Behavior
-[What actually happened]
-
-## Environment
-- OS: [e.g., macOS 14.0]
-- Node.js: [e.g., v20.10.0]
-- supercli: [e.g., v1.2.3]
-
-## Additional Context
-[Any other relevant information, logs, or screenshots]
-```
-
-## Code Contributions
-
-### Branching Strategy
-
-- `main` - Stable release branch
-- `feature/*` - New features
-- `fix/*` - Bug fixes
-- `docs/*` - Documentation improvements
-
-### Development Workflow
-
-```bash
-# Create a feature branch
-git checkout -b feature/my-new-feature
-
-# Make your changes
-# Write tests for new functionality
-
-# Run tests before committing
-npm test
-
-# Commit with clear messages
-git commit -m "feat: add support for new CLI tool X"
-
-# Push and create PR
-git push origin feature/my-new-feature
-```
-
-### Commit Message Conventions
-
-We follow [Conventional Commits](https://www.conventionalcommits.org/):
-
-```
-<type>(<scope>): <description>
-
-[optional body]
-
-[optional footer]
-```
-
-**Types:**
-- `feat` - New feature
-- `fix` - Bug fix
-- `docs` - Documentation changes
-- `style` - Code style (formatting, no logic change)
-- `refactor` - Code refactoring
-- `test` - Adding or updating tests
-- `chore` - Maintenance tasks
-
-**Examples:**
-```
-feat(plugins): add support for new CLI wrapper
-fix(docker): resolve container listing timeout
-docs(readme): update installation instructions
-```
-
-### Pull Request Process
-
-1. **Ensure tests pass** - Run `npm test` locally
-2. **Update documentation** - If adding features, update relevant docs
-3. **Follow code style** - Use existing patterns in the codebase
-4. **Write meaningful PR description** - Explain what and why
-5. **Respond to feedback** - Be responsive to review comments
-
-### Code Review Guidelines
-
-**For reviewers:**
-- Review code for correctness, not style (let linters handle formatting)
-- Test the changes locally when possible
-- Provide constructive, actionable feedback
-- Focus on the code, not the person
-
-**For contributors:**
-- Keep PRs focused and reasonably sized
-- Respond to feedback promptly
-- Ask for clarification if feedback is unclear
-
-## Documentation Contributions
-
-### Where to Find Documentation
-
-- `/docs/` - Main documentation directory
-- `/docs/plugins-how-to.md` - Plugin development guide
-- `/docs/skills/` - Skill system documentation
-- `/README.md` - Project overview and quick start
-- Plugin-specific docs in `/plugins/*/README.md`
-
-### Documentation Style
-
-- Use clear, concise language
-- Include practical examples
-- Keep code snippets up to date
-- Use consistent formatting
-
-### Contributing Plugin Documentation
-
-When creating or updating plugins:
-
-1. Add a `README.md` in the plugin directory
-2. Include installation instructions
-3. Document available commands
-4. Provide usage examples
-5. Reference the upstream CLI documentation
-
-## Plugin Development
-
-### Want to Create a New Plugin?
-
-New bundled plugins use an **isolated file convention** — no shared file edits needed.
-
-See our detailed [Plugin Harness Development Guide](docs/plugins-how-to.md) for:
-
-- Isolated plugin structure (`plugin.json` + `meta.json`)
-- Command wrapping vs passthrough patterns
-- Argument mapping configuration
-- Testing and debugging tips
-
-### Quick Plugin Checklist
-
-Before submitting a plugin for inclusion:
-
-- [ ] Plugin has a valid `plugin.json` manifest
-- [ ] Plugin has a `meta.json` with description, tags, and optional has_learn
-- [ ] Binary dependency checks are configured
-- [ ] Commands have clear descriptions
-- [ ] JSON output is supported where applicable
-- [ ] Plugin README includes installation and usage instructions
-- [ ] Tests pass (if applicable)
-- [ ] No hardcoded credentials or secrets
-- [ ] **No edits to `plugins/plugins.json` or `cli/plugin-install-guidance.js`**
-
-### Publishing Plugins
-
-Once your plugin is ready:
-
-```bash
-# Install locally for testing
-supercli plugins install ./plugins/my-plugin
-
-# Test functionality
-supercli my-plugin --help
-
-# Publish to community registry
-supercli plugins publish ./my-plugin
-```
-
-## Community Guidelines
-
-### Code of Conduct
-
-We are committed to providing a welcoming, inclusive environment. By participating, you agree to:
-
-- Be respectful and inclusive
-- Welcome newcomers and help others learn
-- Accept constructive criticism professionally
-- Focus on what's best for the community
-
-### Getting Help
-
-- **Discussions** - Use GitHub Discussions for questions
-- **Issues** - For bugs and feature requests
-- **Documentation** - Check docs/ before asking
-
-### Supporting Others
-
-- Answer questions in discussions
-- Help newcomers get started
-- Share your experience and knowledge
-
-## License
-
-By contributing to supercli, you agree that your contributions will be licensed under the [MIT License](LICENSE).
-
----
-
-Thank you for contributing to supercli! Your help makes this project better for everyone.

package/PLUGIN_STANDARDS.md

@@ -1,150 +0,0 @@
-# SuperCLI Plugin Standards
-
-## Overview
-This document defines quality standards for plugins in the SuperCLI collection. These standards ensure consistency, discoverability, and usability across 1,179+ plugins.
-
-## Description Quality
-
-### Requirements
-- **Minimum length:** 30 characters
-- **Maximum length:** 150 characters (for searchability)
-- **Format:** `[Tool Name] — [one sentence purpose/key feature]`
-
-### Examples ✓ Good
-```
-"git-cliff — automated changelog generator from git history"
-"ripgrep-all — search documents with ripgrep backend"
-"Zoxide — smart directory jumper with frecency tracking"
-"Nushell — structured shell language for modern development"
-"Tokio — async runtime for Rust applications"
-```
-
-### Examples ✗ Bad
-```
-"git-cliff"                          # Too short
-"git-cliff utility"                  # Generic
-"git-cliff CLI tool for git"         # Too verbose
-"automated changelog generator"      # Missing tool name
-```
-
-### Guidelines
-1. Start with the tool name (exact match to plugin name)
-2. Use em-dash (—) as separator
-3. Describe primary purpose or key feature
-4. Be specific (avoid "CLI tool" or "utility")
-5. Avoid marketing language
-6. Keep scannable (one sentence max)
-
-## Tags
-
-### Requirements
-- **Minimum:** 3 tags
-- **Maximum:** 8 tags (avoid noise)
-- **Controlled vocabulary:** Use `TAG_VOCABULARY.md`
-
-### Tag Categories
-- **Languages:** python, rust, go, javascript, bash, etc.
-- **DevOps:** docker, kubernetes, devops, ci-cd, deployment
-- **Data:** database, sql, analytics, machine-learning
-- **Web:** web, api, http, rest, frontend, backend
-- **Development:** testing, build, development, compiler
-- **System:** system, linux, unix, process, kernel
-- **Productivity:** productivity, task, note, project-management
-- **Security:** security, crypto, auth, encryption
-- **Utilities:** utilities, cli, terminal, shell
-
-### Example Tags
-```json
-{
-  "ripgrep-all": ["search", "rust", "cli", "file-search"],
-  "tokio": ["rust", "async", "concurrency", "development"],
-  "terraform": ["devops", "iac", "cloud", "infrastructure"],
-  "zoxide": ["shell", "utilities", "productivity", "navigation"]
-}
-```
-
-## Source URLs
-
-### Requirements
-- **Required:** Specific GitHub repository URL
-- **Format:** `https://github.com/[owner]/[repo]`
-- **Verified:** URL must be accessible and canonical
-- **Examples:**
-  ```
-  https://github.com/orhun/git-cliff
-  https://github.com/nushell/nushell
-  https://github.com/ajeetdsouza/zoxide
-  https://github.com/rustwasm/wasm-pack
-  ```
-
-### Anti-patterns ✗
-```
-https://github.com                  # Too generic
-https://github.com/[plugin-name]    # Missing owner
-```
-
-## Install Instructions
-
-### Requirements
-- Minimum 2 methods recommended
-- Include at least one package manager or official installation method
-- Include supercli installation command
-
-### Standard Methods
-1. **Package managers:**
-   ```bash
-   brew install ripgrep-all
-   cargo install ripgrep-all
-   npm install -g ripgrep-all
-   ```
-
-2. **Official site:**
-   ```
-   Download from: https://github.com/phiresky/ripgrep-all/releases
-   ```
-
-3. **SuperCLI:**
-   ```bash
-   supercli plugins install ./plugins/ripgrep-all
-   ```
-
-## Quality Checklist
-
-Before submitting a new plugin, ensure:
-
-- [ ] **Name:** Matches official tool name
-- [ ] **Description:** 30-150 characters, clear purpose
-- [ ] **Tags:** 3-8 tags from controlled vocabulary
-- [ ] **Source URL:** Specific GitHub repo, verified accessible
-- [ ] **Install Steps:** 2+ methods, accurate and current
-- [ ] **No duplicates:** Check existing plugins first
-
-## Validation
-
-### Automated Checks
-- Description length: 30-150 characters
-- Tags count: 3-8 tags
-- Tags validity: Must exist in TAG_VOCABULARY.md
-- Source URL: Must be specific GitHub repo
-- No duplicates: Checked against all existing plugins
-
-### Manual Review
-- Description clarity and accuracy
-- Tag relevance to plugin
-- Install instructions accuracy
-- Overall fit with SuperCLI collection
-
-## Phase Completion
-
-**Phase 1 (Metadata):** ✓ Complete
-- All 1,179 plugins have proper source URLs
-
-**Phase 2 (Descriptions):** ✓ Complete
-- All 105 short descriptions enhanced
-- Avg description: 90 characters
-- Quality score: 100%
-
-**Phase 3 (Automation):** → Next
-- CI/CD pipeline for quality enforcement
-- Community contribution guidelines
-- Automated validation on pull requests

package/QUALITY_REPORT.md

@@ -1,62 +0,0 @@
-# Plugin Quality Improvement Report
-
-## Executive Summary
-Automated quality improvements applied to SuperCLI plugin collection.
-
-### Results
-- **Plugins improved:** 50 (4.2% of collection)
-- **Source URLs added:** 31 plugins
-- **Tags added:** 13 additional tags across multiple plugins
-- **Overall improvement:** +36 quality fixes
-
-### Before vs After
-
-| Metric | Before | After | Improved |
-|--------|--------|-------|----------|
-| Generic source URLs | 86 | 55 | -31 |
-| Minimal tags (< 3) | 121 | 116 | -5 |
-| Short descriptions | 105 | 105 | — |
-| **Quality Score** | **91.2%** | **92.1%** | **+0.9%** |
-
-### Quality Score Breakdown
-
-#### Source URLs (✓ Fixed)
-- 31 plugins: Generic `https://github.com` → Specific repos
-- Examples: actix, atuin, aws-cli, azure-cli, docker
-- Benefit: Better attribution and direct access to official repos
-
-#### Tags (✓ Enhanced)
-- 13 plugins: Added relevant tags for better discoverability
-- Added tags: `cloud`, `devops`, `security`, `testing`, etc.
-- Benefit: Improved search and category filtering
-
-#### Descriptions (→ TODO)
-- 105 plugins still have short descriptions (< 30 chars)
-- Requires manual review/enrichment
-- Examples: actix, atuin, bash, curl
-
-### Process Used
-
-1. **Analysis** - Scanned all 1,179 plugins for quality issues
-2. **Suggestions** - Generated intelligent fixes:
-   - Pattern-based source URL guesses
-   - Keyword-based tag suggestions
-3. **Application** - Auto-applied safe fixes (first 50 plugins)
-4. **Validation** - Verified improvements
-
-### Next Phase
-
-**Manual Description Enhancement** (105 plugins):
-- Review short descriptions
-- Expand with features, purpose, use cases
-- Maintain consistency with documentation
-
-**Automation Setup:**
-- CI/CD validation for new plugins
-- Enforce minimum quality standards
-- Community contribution guidelines
-
-## Files Generated
-- `plugin-quality-report.json` - Full analysis with all 142 suggestions
-- `fix-plugin-quality.ts` - Analysis script (reusable)
-- `apply-plugin-fixes.ts` - Application script (reusable)

package/TAG_VOCABULARY.md

@@ -1,217 +0,0 @@
-# SuperCLI Tag Vocabulary
-
-Standardized tags for categorizing and discovering plugins.
-
-## Language Tags
-- `bash` — Bash shell
-- `c` — C language
-- `cpp` — C++ language
-- `csharp` — C# language
-- `go` — Go language
-- `java` — Java language
-- `javascript` — JavaScript language
-- `python` — Python language
-- `rust` — Rust language
-- `typescript` — TypeScript language
-- `lua` — Lua language
-- `ruby` — Ruby language
-- `php` — PHP language
-
-## Category: Development
-
-### Build & Compilation
-- `build` — Build tools and systems
-- `compiler` — Language compilers
-- `bundler` — Code bundling tools
-- `transpiler` — Code transpilers
-
-### Testing & Quality
-- `testing` — Testing frameworks
-- `unit-testing` — Unit test tools
-- `integration-testing` — Integration test tools
-- `coverage` — Code coverage tools
-- `linting` — Code linters
-- `formatting` — Code formatters
-- `benchmarking` — Performance benchmarking
-
-### Package Management
-- `package-manager` — Package/dependency managers
-- `npm` — NPM packages
-- `cargo` — Rust packages
-- `pip` — Python packages
-
-### Development Tools
-- `development` — General development tools
-- `debugging` — Debuggers and debugging tools
-- `documentation` — Documentation generators
-- `asm` — Assembly language tools
-
-## Category: DevOps & Infrastructure
-
-### Container & Orchestration
-- `docker` — Docker containers
-- `kubernetes` — Kubernetes orchestration
-- `container` — Container technologies
-- `orchestration` — Orchestration tools
-
-### Infrastructure & IaC
-- `devops` — DevOps tools and practices
-- `iac` — Infrastructure as Code
-- `terraform` — Terraform IaC
-- `cloud` — Cloud computing
-- `deployment` — Deployment tools
-- `ci-cd` — CI/CD pipelines
-
-### Cloud Providers
-- `aws` — Amazon Web Services
-- `azure` — Microsoft Azure
-- `gcp` — Google Cloud Platform
-- `linode` — Linode cloud
-- `digital-ocean` — DigitalOcean cloud
-- `vultr` — Vultr cloud
-- `scaleway` — Scaleway cloud
-
-### Monitoring & Logging
-- `monitoring` — Monitoring tools
-- `logging` — Logging tools
-- `observability` — Observability tools
-- `metrics` — Metrics collection
-
-## Category: Data & Database
-
-### Databases
-- `database` — Database tools
-- `sql` — SQL databases
-- `nosql` — NoSQL databases
-- `postgresql` — PostgreSQL
-- `mysql` — MySQL/MariaDB
-- `mongodb` — MongoDB
-- `redis` — Redis cache
-- `elasticsearch` — Elasticsearch
-
-### Data Processing
-- `data` — Data processing tools
-- `analytics` — Data analytics
-- `machine-learning` — ML/AI tools
-- `data-processing` — Data transformation
-
-## Category: Web & Networking
-
-### Web
-- `web` — Web technologies
-- `http` — HTTP tools
-- `api` — API tools
-- `rest` — REST APIs
-- `websocket` — WebSocket tools
-- `frontend` — Frontend development
-- `backend` — Backend development
-- `nodejs` — Node.js
-
-### Networking
-- `network` — Networking tools
-- `dns` — DNS tools
-- `vpn` — VPN tools
-- `proxy` — Proxy servers
-- `socket` — Socket programming
-
-## Category: Security
-
-- `security` — Security tools
-- `crypto` — Cryptography
-- `ssl` — SSL/TLS
-- `auth` — Authentication
-- `encryption` — Encryption tools
-- `password` — Password management
-- `vulnerability` — Vulnerability scanning
-
-## Category: Shell & Terminal
-
-### Shell Tools
-- `shell` — Shell tools and utilities
-- `bash` — Bash shell (also language)
-- `zsh` — Zsh shell
-- `fish` — Fish shell
-- `terminal` — Terminal utilities
-- `console` — Console tools
-- `prompt` — Shell prompts
-
-### Shell Utilities
-- `file-search` — File search tools
-- `text-processing` — Text processing
-- `system` — System utilities
-- `process` — Process management
-
-## Category: Utilities
-
-### System
-- `system` — System tools
-- `linux` — Linux-specific
-- `unix` — Unix-like systems
-- `macos` — macOS-specific
-- `windows` — Windows-specific
-- `os` — OS tools
-- `kernel` — Kernel-related
-
-### File & Directory
-- `filesystem` — File system tools
-- `file-search` — File searching
-- `file-management` — File operations
-- `directory` — Directory utilities
-- `compression` — Compression tools
-- `archive` — Archive tools
-
-### Productivity
-- `productivity` — Productivity tools
-- `task-management` — Task management
-- `note-taking` — Note taking
-- `project-management` — Project management
-- `time-tracking` — Time tracking
-
-### Media & Graphics
-- `media` — Media tools
-- `image` — Image processing
-- `video` — Video processing
-- `audio` — Audio processing
-- `graphics` — Graphics tools
-- `conversion` — File conversion
-
-## Category: CLI & Interface
-
-- `cli` — Command-line tools
-- `command-line` — Command-line utilities
-- `interactive` — Interactive tools
-- `filter` — Data filtering
-- `search` — Search tools
-- `fuzzy-search` — Fuzzy searching
-
-## Emerging Categories
-
-- `ai` — AI/ML tools
-- `llm` — Large Language Models
-- `blockchain` — Blockchain tools
-- `web3` — Web3 tools
-- `devtools` — Developer tools
-- `utility` — General utilities
-
----
-
-## Guidelines for Using Tags
-
-1. **Always use 3-8 tags** per plugin
-2. **Use specific tags** over generic ones
-   - ✓ `rust`, `async`, `tokio`
-   - ✗ `development`, `tool`
-3. **Match tool primary purpose** first
-   - `ripgrep-all` → `search`, `rust`, `file-search`
-   - Not: `cli`, `utility`
-4. **Include language if relevant**
-   - `tokio` → `rust`, `async`, ...
-5. **Include domain if applicable**
-   - `terraform` → `devops`, `iac`, `cloud`, ...
-
-## Statistics
-
-- **Total tags:** 120+
-- **Most used:** `cli`, `utility`, `development`
-- **Categories:** 12 major categories
-- **New tags encouraged** as collection grows (propose in PR)