npcsh 1.1.22__py3-none-any.whl → 1.1.23__py3-none-any.whl

npcsh/npc_team/jinxs/skills/code-review/SKILL.md

@@ -0,0 +1,45 @@
+---
+description: Conducts code reviews. Use when asked to review code, review a PR, or check code quality.
+---
+# Code Review
+
+## approach
+Start by reading the full diff to understand the scope of changes.
+Identify the purpose of the change — is it a bug fix, new feature, refactor, or config change?
+Note which files are modified and how they relate to each other.
+
+## structure
+Check the following structural concerns:
+- Are changes in the right files/modules?
+- Is new code placed in a logical location?
+- Are there any circular dependencies introduced?
+- Is the change minimal — does it avoid unnecessary modifications?
+
+## correctness
+Review for correctness:
+- Does the logic handle edge cases (null, empty, boundary values)?
+- Are error paths handled properly?
+- Is state management correct (no race conditions, stale data)?
+- Do new functions have the right return types?
+
+## style
+Check style and conventions:
+- Naming: are variables, functions, classes named clearly?
+- Consistency: does the code match the project's existing patterns?
+- Comments: are complex sections explained? Are there unnecessary comments?
+- Formatting: consistent indentation, line length, spacing?
+
+## testing
+Evaluate test coverage:
+- Are new code paths tested?
+- Are edge cases covered?
+- Do tests actually assert meaningful behavior (not just "runs without error")?
+- Are there integration tests where needed?
+
+## security
+Check for security issues:
+- Input validation at system boundaries
+- No hardcoded secrets or credentials
+- SQL injection, XSS, command injection prevention
+- Proper authentication/authorization checks
+- Sensitive data not logged or exposed

npcsh/npc_team/jinxs/skills/debugging/SKILL.md

@@ -0,0 +1,44 @@
+---
+description: Systematic debugging methodology. Use when asked to debug, troubleshoot, or diagnose issues.
+---
+# Debugging
+
+## reproduce
+First, reproduce the bug consistently:
+- Get exact steps to trigger the issue
+- Note the environment (OS, versions, config)
+- Determine if it's deterministic or intermittent
+- Find the minimal reproduction case
+
+If you can't reproduce it, you can't verify a fix.
+
+## isolate
+Narrow down the cause:
+- Binary search through the codebase (git bisect)
+- Comment out / disable components to isolate
+- Check recent changes (git log, blame)
+- Add targeted logging at boundaries
+- Test with minimal input/config
+
+## diagnose
+Once isolated, understand the root cause:
+- Read the code path carefully, don't assume
+- Check data flow — what goes in, what comes out?
+- Look for state mutations, race conditions, stale caches
+- Check external dependencies (API changes, schema drift)
+- Verify assumptions with print/log/debugger
+
+## fix
+Apply the minimal fix:
+- Fix the root cause, not the symptom
+- Keep the change as small as possible
+- Add a test that fails without the fix and passes with it
+- Check for similar patterns elsewhere in the codebase
+- Document WHY the bug happened if it's non-obvious
+
+## verify
+Confirm the fix works:
+- Run the reproduction steps — bug should be gone
+- Run the full test suite — no regressions
+- Test edge cases around the fix
+- Review the fix yourself before submitting

npcsh/npc_team/jinxs/skills/git-workflow.jinx

@@ -0,0 +1,44 @@
+jinx_name: git-workflow
+description: "Git workflow best practices. Use when asked about git branching, commits, or merge strategy. [Sections: branching, commits, merging, hotfix]"
+inputs:
+- section: all
+steps:
+  - engine: skill
+    skill_name: git-workflow
+    skill_description: Git workflow best practices.
+    sections:
+      branching: |
+        Use feature branches off main/develop:
+          git checkout -b feature/my-feature develop
+        Name branches descriptively:
+          feature/ — new functionality
+          fix/ — bug fixes
+          chore/ — maintenance, deps, config
+        Keep branches short-lived. Rebase onto target before merging.
+      commits: |
+        Write clear commit messages:
+          Line 1: imperative summary under 72 chars
+          Line 3+: explain WHY, not what (the diff shows what)
+        One logical change per commit. Don't mix refactors with features.
+        Use conventional commits if the project uses them:
+          feat: add user search
+          fix: handle null avatar URL
+          chore: bump eslint to v9
+      merging: |
+        Prefer squash merges for feature branches (clean history).
+        Use merge commits for long-lived branches (preserves context).
+        Always pull/rebase before merging to avoid unnecessary merge commits.
+        Delete branches after merging.
+        Run CI before merging — never merge a red build.
+      hotfix: |
+        For urgent production fixes:
+          1. Branch off main: git checkout -b hotfix/fix-name main
+          2. Make the minimal fix
+          3. Test thoroughly
+          4. Merge to main AND develop/release
+          5. Tag the release
+        Keep hotfix scope minimal — fix only the immediate issue.
+    scripts_json: '[]'
+    references_json: '[]'
+    assets_json: '[]'
+    section: '{{section}}'

npcsh/npc_team/kadiefa.npc

@@ -11,11 +11,10 @@ colors:
   top: "255,255,255"
   bottom: "173,216,230"
 primary_directive: |
-  You are kadiefa, the exploratory snow leopard. You love to find new paths and to explore hidden gems.
-  You go into caverns no cat has ventured into before. You climb peaks that others call crazy.
-  Your role is to lead users on wandering explorations - deep research journeys that follow threads
-  wherever they lead. You help users explore complex research questions and think outside the box.
-  Use web search and browsing tools to discover new information.
+  You are kadiefa, the exploratory snow leopard. You wander into places no one else looks.
+  Think outside the box. Make unexpected connections across domains.
+  Reframe problems. Pull in ideas from biology, music, history, anywhere surprising.
+  Follow the most interesting thread, not the most obvious one.
 jinxs:
   - lib/core/python
   - lib/core/sh

npcsh/npc_team/npcsh.ctx

@@ -3,6 +3,22 @@ context: |
     environment for users where they can work and be as successful as possible.
     npcsh is a command-line tool that makes it easy for users to harness
     the power of LLMs from a command line shell. npcsh is a command line toolkit consisting of several programs.
+
+    ## How to solve tasks with tools
+    You have access to tools (jinxs) like sh, python, edit_file, load_file, etc.
+    When solving tasks that require action:
+    1. PLAN: Break the task into concrete steps before doing anything.
+    2. ORIENT: Check your environment first (ls, pwd, which, cat). Never assume files or tools exist.
+    3. INSTALL: If you need packages or source code, get them first (apt-get install -y, wget, curl, pip install).
+    4. EXECUTE: Run one command at a time. Read the output carefully before proceeding.
+    5. ADAPT: If a command fails, read the error. Diagnose the actual cause and fix it. Never repeat the same failed command without changing something.
+    6. VERIFY: Confirm your work (check files exist, test the output).
+
+    Common mistakes to avoid:
+    - Running ./configure or make before downloading and extracting source code
+    - Retrying the exact same command that just failed
+    - Not checking what directory you're in or what files are present
+    - Trying to use a tool/package without installing it first
 databases:
     - ~/npcsh_history.db
 mcp_servers:

npcsh/npc_team/plonk.npc

@@ -11,15 +11,11 @@ colors:
   top: "34,139,34"
   bottom: "139,69,19"
 primary_directive: |
-  You are plonk, the browser and GUI automation specialist.
-
-  Browser tools: open_browser, browser_action, browser_screenshot, close_browser
-
-  browser_action actions: click, type, type_and_enter, select, wait, scroll, get_text, get_page, get_elements, press_key
-
-  Use get_elements to discover selectors on the page. Use xpath:// prefix for XPath selectors.
-
-  Desktop tools: screenshot, click, type_text, key_press, launch_app, wait
+  You are plonk, the automation specialist for browser and desktop.
+  Browser: open_browser, browser_action, browser_screenshot, close_browser.
+  browser_action: click, type, type_and_enter, select, wait, scroll, get_text, get_page, get_elements, press_key.
+  Desktop: screenshot, click, type_text, key_press, launch_app, wait.
+  Use get_elements to find selectors. Use xpath:// for XPath. Screenshot after each step to verify.
 jinxs:
   - lib/browser/*
   - lib/computer_use/*

npcsh/npc_team/sibiji.npc

@@ -11,14 +11,22 @@ colors:
   top: "148,0,211"
   bottom: "75,0,130"
 primary_directive: |
-  You are sibiji, the orchestrator and general manager of the NPC team.
-  Your role is to delegate tasks to appropriate specialist agents based on their expertise.
+  You are sibiji, the orchestrator of the NPC team.
 
-  When delegating, match the task to the agent whose primary_directive best fits. Basic search inquiries can be handled by yourself. Do not delegate unnecessarily.
-  You have access to the delegate tool to pass tasks to other agents.
+  RULE 1: Simple tasks — do them yourself with sh, python, or web_search. Then tell the user the answer.
+  RULE 2: Complex tasks — delegate to the right agent. Pass the user's request as the task.
+  RULE 3: After running a command, read the output and answer the user. Never delegate after you already have the result.
+
+  Agents:
+  @corca — shell, code, debug, files, sysadmin
+  @guac — data analysis, pandas, SQL, CSV
+  @alicanto — deep research, papers, literature review
+  @kadiefa — exploratory thinking, unexpected connections
+  @frederic — creative/math, unconventional solutions
+  @plonk — browser automation, GUI, screenshots
 jinxs:
   - lib/core/delegate
-  - lib/core/convene
+  - modes/convene
   - lib/core/sh
   - lib/core/python
   - lib/core/search/web_search

npcsh/npcsh.py

@@ -510,6 +510,7 @@ def main(npc_name: str = None) -> None:
         initial_state.npc = default_npc
 
     initial_state.team = team
+    initial_state.command_history = command_history
     if args.command:
          state = initial_state
          state.current_path = os.getcwd()

npcsh/routes.py

@@ -51,10 +51,6 @@ class CommandRouter:
         self.jinx_objects[command_name] = jinx
         self.help_info[command_name] = jinx.description or "Jinx command"
 
-    def is_interactive(self, command_name: str) -> bool:
-        jinx = self.jinx_objects.get(command_name)
-        return bool(jinx and getattr(jinx, 'interactive', False))
-    
     def _execute_jinx(self, jinx: Jinx, command: str, **kwargs):
         messages = kwargs.get("messages", [])
         npc = kwargs.get('npc')

npcsh/yap.py

@@ -4,6 +4,7 @@ yap - Voice chat mode CLI entry point
 This is a thin wrapper that executes the yap.jinx through the jinx mechanism.
 """
 import argparse
+import os
 import sys
 
 from npcsh._state import setup_shell
@@ -14,8 +15,10 @@ def main():
     parser.add_argument("--model", "-m", type=str, help="LLM model to use")
     parser.add_argument("--provider", "-p", type=str, help="LLM provider to use")
     parser.add_argument("--files", "-f", nargs="*", help="Files to load for RAG context")
-    parser.add_argument("--tts-model", type=str, default="kokoro", help="TTS model to use")
-    parser.add_argument("--voice", type=str, default="af_heart", help="Voice for TTS")
+    parser.add_argument("--tts-model", type=str, default=None,
+                        help="TTS engine (kokoro, qwen3, elevenlabs, openai, gemini, gtts)")
+    parser.add_argument("--voice", type=str, default=None,
+                        help="Voice ID (engine-specific, e.g. af_heart for kokoro, ryan for qwen3)")
     args = parser.parse_args()
 
     # Setup shell to get team and default NPC
@@ -25,6 +28,20 @@ def main():
         print("Error: yap jinx not found. Ensure npc_team/jinxs/modes/yap.jinx exists.")
         sys.exit(1)
 
+    # Read saved TTS preferences from env (set by ~/.npcshrc)
+    saved_engine = os.environ.get("NPCSH_TTS_ENGINE", "")
+    saved_voice = os.environ.get("NPCSH_TTS_VOICE", "")
+    setup_done = os.environ.get("NPCSH_YAP_SETUP_DONE", "0") == "1"
+
+    # Resolve TTS engine: explicit arg > saved pref > default
+    tts_model = args.tts_model or saved_engine or "kokoro"
+    voice = args.voice or saved_voice or None
+
+    # Show setup if no explicit args and no saved prefs and not skipped
+    has_explicit_args = args.tts_model is not None or args.voice is not None
+    has_saved_prefs = bool(saved_engine)
+    show_setup = not has_explicit_args and not has_saved_prefs and not setup_done
+
     # Build context for jinx execution
     context = {
         "npc": default_npc,
@@ -33,8 +50,9 @@ def main():
         "model": args.model,
         "provider": args.provider,
         "files": ",".join(args.files) if args.files else None,
-        "tts_model": args.tts_model,
-        "voice": args.voice,
+        "tts_model": tts_model,
+        "voice": voice,
+        "show_setup": show_setup,
     }
 
     # Execute the jinx

npcsh-1.1.23.data/data/npcsh/npc_team/SKILL.md

@@ -0,0 +1,44 @@
+---
+description: Systematic debugging methodology. Use when asked to debug, troubleshoot, or diagnose issues.
+---
+# Debugging
+
+## reproduce
+First, reproduce the bug consistently:
+- Get exact steps to trigger the issue
+- Note the environment (OS, versions, config)
+- Determine if it's deterministic or intermittent
+- Find the minimal reproduction case
+
+If you can't reproduce it, you can't verify a fix.
+
+## isolate
+Narrow down the cause:
+- Binary search through the codebase (git bisect)
+- Comment out / disable components to isolate
+- Check recent changes (git log, blame)
+- Add targeted logging at boundaries
+- Test with minimal input/config
+
+## diagnose
+Once isolated, understand the root cause:
+- Read the code path carefully, don't assume
+- Check data flow — what goes in, what comes out?
+- Look for state mutations, race conditions, stale caches
+- Check external dependencies (API changes, schema drift)
+- Verify assumptions with print/log/debugger
+
+## fix
+Apply the minimal fix:
+- Fix the root cause, not the symptom
+- Keep the change as small as possible
+- Add a test that fails without the fix and passes with it
+- Check for similar patterns elsewhere in the codebase
+- Document WHY the bug happened if it's non-obvious
+
+## verify
+Confirm the fix works:
+- Run the reproduction steps — bug should be gone
+- Run the full test suite — no regressions
+- Test edge cases around the fix
+- Review the fix yourself before submitting

{npcsh-1.1.22.data → npcsh-1.1.23.data}/data/npcsh/npc_team/alicanto.npc

@@ -11,14 +11,10 @@ colors:
   top: "255,215,0"
   bottom: "218,165,32"
 primary_directive: |
-  You are alicanto, a research agent. You investigate hypotheses through experimentation and evidence gathering.
-  Search academic papers to ground your work in existing literature.
-  Search the web for data, documentation, and recent findings.
-  Write and execute Python code to analyze data, compute statistics, and generate results.
-  Use shell commands for data processing and system tasks.
-  Create files to record your findings, analyses, and evidence.
-  When exploring a hypothesis, gather evidence from multiple sources, analyze it quantitatively where possible, and document what you find.
-  Say RESEARCH_COMPLETE when you have sufficient evidence to evaluate your hypothesis.
+  You are alicanto, the deep research specialist. You produce thorough research reports.
+  Search multiple sources, read papers, gather evidence, then synthesize into a report.
+  Use web_search and file_search to find sources. Use python to analyze data.
+  Say RESEARCH_COMPLETE when you have enough evidence to answer.
 jinxs:
   - lib/core/search/web_search
   - lib/core/search/file_search

npcsh/npc_team/jinxs/modes/config_tui.jinx → npcsh-1.1.23.data/data/npcsh/npc_team/config.jinx

@@ -1,4 +1,4 @@
-jinx_name: config_tui
+jinx_name: config
 description: Interactive TUI editor for npcsh configuration (~/.npcshrc)
 interactive: true
 inputs: []