@nomad-e/bluma-cli 0.1.18 → 0.1.19

package/dist/config/models_config.json

@@ -1,78 +0,0 @@
-{
-  "models": [
-    {
-      "id": "google/gemini-3.1-pro-preview-customtools",
-      "tier": "tools",
-      "task_type": "multi_tool",
-      "context_window": 1048576,
-      "pricing": {
-        "input_per_1m_tokens": "$2.00",
-        "output_per_1m_tokens": "$12.00"
-      },
-      "description": "Enhanced version of Gemini 3.1 Pro tuned specifically for reliable tool selection and function calling. Designed to avoid overusing generic shell tools when more targeted tools are available, making it ideal for complex coding agents and multi-tool workflows in the CLI.",
-      "best_for": [
-        "Workflows that involve many different tools (file operations, search, tests, shell) and require the model to pick the right one.",
-        "Coordinating multi-step coding tasks where safe and accurate tool use is more important than raw speed or cost.",
-        "Complex debugging or refactors that need mixing code edits, search, tests, and shell commands.",
-        "Agent-style tasks where tool misuse is risky and you want maximum reliability in tool choice."
-      ],
-      "not_for": "Very simple edits, quick questions, or cheap one-off operations that qwen3.5-flash can handle more economically."
-    },
-    {
-      "id": "qwen/qwen3-coder-next",
-      "tier": "coder",
-      "task_type": "multi_file",
-      "context_window": 262144,
-      "pricing": {
-        "input_per_1m_tokens": "$0.12",
-        "output_per_1m_tokens": "$0.75"
-      },
-      "description": "Coder-focused MoE model optimized for long-horizon coding agents and local development workflows. Handles large codebases, multi-file refactors, and recovery from execution failures while remaining cost-effective for always-on agents.",
-      "best_for": [
-        "Large refactors across many files where the agent must keep track of a global design.",
-        "Implementing new subsystems (features, services, modules) with tests and documentation.",
-        "Agentic coding loops that involve planning, executing edits, running commands/tests, and iterating.",
-        "Complex bug-hunting sessions where the model must reason over many files and past attempts."
-      ],
-      "not_for": "Tiny edits, trivial Q&A, or ultra-simple tasks where qwen3.5-flash is cheaper and fast enough."
-    },
-    {
-      "id": "deepseek/deepseek-chat-v3.1",
-      "tier": "reasoning",
-      "task_type": "reasoning",
-      "context_window": 32768,
-      "pricing": {
-        "input_per_1m_tokens": "$0.15",
-        "output_per_1m_tokens": "$0.75"
-      },
-      "description": "Hybrid reasoning model supporting both thinking and non-thinking modes with strong performance on coding, tool use, and long-context reasoning. Good choice when deep structured reasoning or complex analysis is needed in addition to code generation.",
-      "best_for": [
-        "Deep reasoning on tricky bugs, architecture decisions, or algorithm design.",
-        "Analyzing logs, traces, or large textual outputs to identify root causes.",
-        "Complex code reviews or design reviews where clear, structured justification is needed.",
-        "Cases where you explicitly want more deliberate reasoning rather than only fast responses."
-      ],
-      "not_for": "Purely mechanical edits or very simple tasks where a cheaper, faster model is sufficient."
-    },
-    {
-      "id": "anthropic/claude-haiku-4.5",
-      "tier": "heavy",
-      "task_type": "complex",
-      "context_window": 200000,
-      "pricing": {
-        "input_per_1m_tokens": "$1.00",
-        "output_per_1m_tokens": "$5.00"
-      },
-      "description": "High-end, high-speed frontier model with extended thinking and strong performance on coding, reasoning, and computer-use tasks. Best reserved for the most complex, high-stakes workflows where you need frontier-level capability and robustness.",
-      "best_for": [
-        "Very large, high-risk changes to critical production code where maximum reliability matters.",
-        "Long, multi-phase agentic tasks that must not fail (e.g. migrations, deep refactors, safety-sensitive changes).",
-        "Scenarios where you want frontier-level coding performance and can afford higher cost.",
-        "Coordinating many sub-agents or parallel tool workflows for large projects."
-      ],
-      "not_for": "Routine day-to-day coding tasks, quick fixes, or low-impact work where cheaper models are perfectly adequate."
-    }
-  ],
-  "default_model": "qwen/qwen3-coder-next"
-}
-

package/dist/skills/git-conventional/LICENSE.txt

@@ -1,3 +0,0 @@
-Copyright (c) NomadEngenuity. All rights reserved.
-
-This skill is part of the Bluma CLI and is subject to the same license as the main package (Apache-2.0) unless otherwise stated in the SKILL.md frontmatter.

package/dist/skills/git-conventional/SKILL.md

@@ -1,83 +0,0 @@
----
-name: git-conventional
-description: Git workflow expert. Handles commits, branches, PRs following Conventional Commits.
-version: 1.0.0
-author: NomadEngenuity
-license: LICENSE.txt
-tools:
-  required:
-    - shell_command
-    - command_status
-    - message
-  recommended:
-    - read_file_lines
-    - edit_tool
----
-
-# Instructions
-
-## Context
-You are executing the git-conventional workflow. This skill ensures all Git operations follow best practices with Conventional Commits format.
-
-## Procedure
-
-### Step 1: Check Status
-```bash
-git status --short
-```
-Review what files will be committed.
-
-### Step 2: Stage Changes
-```bash
-git add .
-```
-Or stage specific files if requested.
-
-### Step 3: Review Staged Changes
-```bash
-git diff --staged
-```
-Understand what is being committed to write a good message.
-
-### Step 4: Commit with Conventional Format
-```bash
-git commit -m "type(scope): description"
-```
-
-Format: `<type>(<scope>): <description>`
-
-Types:
-- feat: New feature
-- fix: Bug fix
-- docs: Documentation
-- style: Formatting
-- refactor: Code cleanup
-- perf: Performance
-- test: Tests
-- chore: Maintenance
-
-Rules:
-- Max 72 chars
-- Imperative mood: "add" not "added"
-- Lowercase
-- No trailing period
-
-### Step 5: Push (if requested)
-```bash
-git push origin main
-```
-
-## Blocked Commands
-Never use without explicit user approval:
-- `git push --force`
-- `git reset --hard`
-- `git rebase -i` (public branches)
-- `git branch -D`
-
-## Error Reference
-
-| Error | Cause | Fix |
-|-------|-------|-----|
-| nothing to commit | No staged changes | `git add .` first |
-| rejected (non-fast-forward) | Remote has new commits | `git pull` first |
-| permission denied | Auth issue | Check SSH key or token |