• "analyze my code" → Auto-executes /sc:analyze
• "review the codebase" → Auto-executes /sc:analyze
• "check code quality" → Auto-executes /sc:analyze
• "audit for issues" → Auto-executes /sc:analyze
• "work on these in parallel" → Auto-executes /slashsense:parallel:execute

⚡ Lightning Fast

• P95 latency: <2ms (keyword path)
• Zero context overhead
• Lazy model loading
• Automatic caching

🔧 Zero Configuration

• Works out of the box
• Auto-discovers all installed plugins
• No API keys required (keyword + Model2Vec)
• Optional: Semantic Router for complex queries

Quick Start

Installation

Option 1: From Marketplace (Recommended)

# Add SlashSense marketplace
/plugin marketplace add Shakes-tzd/slashsense

# Install plugin
/plugin install slashsense

Option 2: Direct from GitHub

# Install directly
/plugin install Shakes-tzd/slashsense

# Or specify version
/plugin install Shakes-tzd/slashsense@0.1.0

Option 3: Local Development

# Clone repository
git clone https://github.com/Shakes-tzd/slashsense
cd slashsense

# Install locally
/plugin install @local

Usage

Just type what you want in natural language:

# Instead of memorizing:
/sc:analyze --comprehensive

# Just type:
"can you analyze my code for issues?"

# SlashSense auto-executes:
🎯 Auto-executing /sc:analyze (85% confidence, keyword match, 0.02ms)

Supported Commands

SlashSense detects these commands out of the box:

Expandable: SlashSense auto-discovers commands from all your installed plugins!

Parallel Development Workflow

SlashSense includes a powerful parallel development system that lets Claude work on multiple independent tasks simultaneously using git worktrees.

Key Features

• 🚀 Automatic Subagent Spawning - Claude spawns multiple agents to work in parallel
• 🌿 Git Worktrees - Isolated working directories for each task
• 📋 GitHub Integration - Automatic issue creation and tracking
• 🎯 Zero Manual Coordination - Claude manages everything automatically

Commands

Example Workflow

You: "I need to implement authentication, dashboard, and analytics"

Claude: "📋 These tasks are independent. Would you like to work on them in parallel?"

You: "yes, parallelize this work"

SlashSense: 🎯 /slashsense:parallel:execute detected (92% confidence)

Claude:
"✅ Created plan: .parallel/plans/PLAN-20251014.md
✅ Created 3 GitHub issues
✅ Created 3 git worktrees
🚀 Spawning 3 parallel subagents...

Agent 1: Working on authentication (worktrees/task-123)
Agent 2: Working on dashboard (worktrees/task-124)
Agent 3: Working on analytics (worktrees/task-125)

All tasks complete in 2 hours (vs 4.5h sequential - 56% faster!)"

Time Savings

• Sequential: 4.5 hours (sum of all tasks)
• Parallel: 2 hours (longest task duration)
• Speed Up: ~57% faster

Requirements:

• GitHub CLI (gh) installed and authenticated
• Git remote configured
• Clean working tree

How It Works

Architecture

User prompt: "analyze my code please"
              ↓
    UserPromptSubmit Hook
              ↓
    ┌─────────────────────┐
    │   3-Tier Cascade    │
    ├─────────────────────┤
    │ 1. Keyword (0.02ms) │ → 60% coverage
    │ 2. Model2Vec (0.2ms)│ → 30% coverage
    │ 3. Semantic (50ms)  │ → 10% coverage
    └─────────────────────┘
              ↓
    Command: /sc:analyze (85%)
              ↓
    Hook modifies prompt to "/sc:analyze"
              ↓
    Claude Code auto-executes the command

Confidence Levels

• 85%+: Keyword match (high precision, instant)
• 70-85%: Semantic match (good accuracy, fast)
• 50-70%: Fallback match (requires confirmation)
• <50%: No suggestion (pass through)

Development

Prerequisites

• Python 3.10+
• UV package manager
• Claude Code

Setup

# Clone repository
git clone https://github.com/yourusername/slashsense
cd slashsense

# Install dependencies
uv sync

# Run tests
uv run pytest

# Test matchers individually
uv run lib/keyword_matcher.py
uv run lib/model2vec_matcher.py
uv run lib/semantic_router_matcher.py

# Test hook
echo '{"prompt":"analyze my code"}' | uv run hooks/user_prompt_submit.py

Documentation

# Serve docs locally
uv run mkdocs serve
# Visit http://localhost:8000

# Build docs
uv run mkdocs build

# Deploy to GitHub Pages
uv run mkdocs gh-deploy

Code Quality

# Format code
uv run ruff format .

# Lint
uv run ruff check --fix .

# Type check
uv run mypy lib/

# Run all checks
uv run pytest && uv run ruff check . && uv run mypy lib/

Configuration

Basic Configuration

SlashSense works out of the box with zero configuration!

Advanced Configuration

Edit ~/.claude/plugins/slashsense/data/user_patterns.json:

{
  "enabled": true,
  "confidence_threshold": 0.7,
  "tiers": {
    "keyword": true,
    "model2vec": true,
    "semantic_router": false
  },
  "custom_mappings": {
    "make it pretty": "/sc:improve",
    "ship it": "/sc:git"
  }
}

Environment Variables

# Optional: For Semantic Router (Tier 3)
export COHERE_API_KEY="your-key"
# Or
export OPENAI_API_KEY="your-key"

Performance

Benchmarked on M1 MacBook Pro:

Total hook overhead: <2ms for 90% of queries

Roadmap

v1.0 (Current)

• 3-tier detection cascade
• Keyword matching
• Model2Vec embeddings
• Semantic Router integration
• Hook implementation
• Basic command mappings

v1.1 (Current)

• /slashsense:config command
• /slashsense:stats command
• Parallel development workflow
• /slashsense:parallel:plan command
• /slashsense:parallel:execute command
• /slashsense:parallel:status command
• /slashsense:parallel:cleanup command
• Auto-discovery of all plugin commands
• Learning mode (capture corrections)
• Custom pattern editor

v1.2 (Future)

• Multi-command suggestions
• Context-aware ranking
• Command chaining detection
• Team pattern sharing
• VS Code extension

Contributing

We love contributions! Here's how to help:

Reporting Bugs

Open an issue with:

• Clear description of the problem
• Steps to reproduce
• Expected vs actual behavior
• Your environment (OS, Claude Code version, plugin version)

Suggesting Features

Open an issue with:

• Use case description
• Proposed solution
• Why it would help others

Pull Requests

1. Fork the repository
2. Create feature branch: git checkout -b feature/amazing-feature
3. Make changes and add tests
4. Ensure tests pass: uv run pytest
5. Format code: uv run ruff format .
6. Commit changes: git commit -m 'feat: add amazing feature'
7. Push to branch: git push origin feature/amazing-feature
8. Open Pull Request

Development guidelines:

• Follow existing code style
• Add tests for new features
• Update documentation
• Use conventional commits
• Ensure all checks pass

Testing

# Run all tests
uv run pytest

# Run with coverage
uv run pytest --cov=lib --cov-report=html

# Run specific test file
uv run pytest tests/test_keyword.py

# Run with verbose output
uv run pytest -v

# Test individual matchers (built-in tests)
uv run lib/keyword_matcher.py
uv run lib/model2vec_matcher.py
uv run lib/semantic_router_matcher.py

FAQ

Does SlashSense slow down Claude Code?

No! The hook adds <2ms latency for 90% of queries. You won't notice it.

Does it work offline?

Keyword and Model2Vec tiers work completely offline (90% coverage). Semantic Router tier requires an API key but is optional.

Can I add custom commands?

Yes! Edit data/user_patterns.json to add your own mappings.

Does it work with other plugins?

Yes! SlashSense auto-discovers commands from all installed plugins.

What about privacy?

Everything runs locally except Semantic Router (optional). No data is collected.

Troubleshooting

"No command detected"

• Check confidence threshold in config
• Try more specific language
• Add custom mappings for your phrases

"Model2Vec not available"

# Install dependencies
uv sync

The model downloads automatically on first use (~8MB).

"Semantic Router failing"

# Set API key
export COHERE_API_KEY="your-key"
# Or
export OPENAI_API_KEY="your-key"

Or disable in config: "semantic_router": false

License

MIT License - see LICENSE file for details.

Acknowledgments

• Built with Model2Vec by Minish Lab
• Uses Semantic Router by Aurelio Labs
• Inspired by Claude Code's plugin ecosystem
• Special thanks to all contributors

Links

• Documentation: https://yourusername.github.io/slashsense/
• GitHub: https://github.com/yourusername/slashsense
• Issues: https://github.com/yourusername/slashsense/issues
• Discussions: https://github.com/yourusername/slashsense/discussions
• Claude Code Docs: https://docs.claude.com/en/docs/claude-code/plugins
• Website: https://slashsense.com (coming soon)

Support

• 📖 Read the docs
• 💬 Join discussions
• 🐛 Report bugs
• ⭐ Star the repo