bobo-ai-cli 3.0.0 → 3.0.3

package/bundled-skills/gitlab/SKILL.md

@@ -1,13 +0,0 @@
----
-id: "gitlab"
-title: "gitlab"
-category: "dev-tools"
-tags: ["gitlab"]
-triggers: []
-dependencies: []
-source: "E:/Bobo's Coding cache/.claude/skills/gitlab"
----
-
-# gitlab
-
-Skill directory: gitlab

package/bundled-skills/gopls-lsp/SKILL.md

@@ -1,32 +0,0 @@
----
-id: "gopls-lsp"
-title: "gopls-lsp"
-category: "other"
-tags: ["gopls-lsp", "supported extensions", "installation", "more information"]
-triggers: []
-dependencies: []
-source: "E:/Bobo's Coding cache/.claude/skills/gopls-lsp"
----
-
-# gopls-lsp
-
-Go language server for Claude Code, providing code intelligence, refactoring, and analysis.
-
-## Supported Extensions
-
-`.go`
-
-## Installation
-
-Install gopls using the Go toolchain:
-
-```bash
-go install golang.org/x/tools/gopls@latest
-```
-
-Make sure `$GOPATH/bin` (or `$HOME/go/bin`) is in your PATH.
-
-## More Information
-
-- [gopls Documentation](https://pkg.go.dev/golang.org/x/tools/gopls)
-- [GitHub Repository](https://github.com/golang/tools/tree/master/gopls)

package/bundled-skills/got-controller/SKILL.md

@@ -1,218 +0,0 @@
----
-id: "got-controller"
-title: "GoT Controller"
-category: "research"
-tags: ["got controller", "role", "what is graph of thoughts?", "core got operations", "decision logic", "graph state management", "got graph state", "tool usage", "best practices", "examples"]
-triggers: []
-dependencies: []
-source: "E:/Bobo's Coding cache/.claude/skills/got-controller"
----
-
----
-name: got-controller
-description: Graph of Thoughts (GoT) Controller - 管理研究图状态，执行图操作（Generate, Aggregate, Refine, Score），优化研究路径质量。当研究主题复杂或多方面、需要策略性探索（深度 vs 广度）、高质量研究时使用此技能。
----
-
-# GoT Controller
-
-## Role
-
-You are a **Graph of Thoughts (GoT) Controller** responsible for managing research as a graph operations framework. You orchestrate complex multi-agent research using the GoT paradigm, optimizing information quality through strategic generation, aggregation, refinement, and scoring operations.
-
-## What is Graph of Thoughts?
-
-Graph of Thoughts (GoT) is a framework inspired by [SPCL, ETH Zürich](https://github.com/spcl/graph-of-thoughts) that models reasoning as a graph where:
-
-- **Nodes** = Research findings, insights, or conclusions
-- **Edges** = Dependencies and relationships between findings
-- **Scores** = Quality ratings (0-10 scale) assigned to each node
-- **Frontier** = Set of active nodes available for further exploration
-- **Operations** = Transformations that manipulate the graph state
-
-## Core GoT Operations
-
-### 1. Generate(k)
-
-**Purpose**: Create k new research paths from a parent node
-
-**When to Use**:
-
-- Initial exploration of a topic
-- Expanding on high-quality findings
-- Exploring multiple angles simultaneously
-
-**Implementation**: Spawn k parallel research agents, each exploring a distinct aspect
-
-### 2. Aggregate(k)
-
-**Purpose**: Combine k nodes into one stronger, comprehensive synthesis
-
-**When to Use**:
-
-- Multiple agents have researched related aspects
-- You need to combine findings into a cohesive whole
-- Resolving contradictions between sources
-
-**Implementation**: Combine findings, resolve conflicts, extract key insights
-
-### 3. Refine(1)
-
-**Purpose**: Improve and polish an existing finding without adding new research
-
-**When to Use**:
-
-- A node has good content but needs better organization
-- Clarifying ambiguous findings
-- Improving citation quality and completeness
-
-**Implementation**: Improve clarity, completeness, citations, structure
-
-### 4. Score
-
-**Purpose**: Evaluate the quality of a research finding (0-10 scale)
-
-**Scoring Criteria**:
-
-- **9-10 (Excellent)**: Multiple high-quality sources (A-B), no contradictions, comprehensive
-- **7-8 (Good)**: Adequate sources, minor ambiguities, good coverage
-- **5-6 (Acceptable)**: Mix of source qualities, some contradictions, moderate coverage
-- **3-4 (Poor)**: Limited/low-quality sources, significant contradictions, incomplete
-- **0-2 (Very Poor)**: No verifiable sources, major errors, severely incomplete
-
-### 5. KeepBestN(n)
-
-**Purpose**: Prune low-quality nodes, keeping only the top n at each level
-
-**When to Use**:
-
-- Managing graph complexity
-- Focusing resources on high-quality paths
-- Preventing exponential growth of nodes
-
-## GoT Research Execution Patterns
-
-### Pattern 1: Balanced Exploration (Most Common)
-
-**Use for**: Most research scenarios - balance breadth and depth
-
-```
-Iteration 1: Generate(4) from root
-  → 4 parallel research paths
-  → Score: [7.2, 8.5, 6.8, 7.9]
-
-Iteration 2: Strategy based on scores
-  → High score (8.5): Generate(2) - explore deeper
-  → Medium scores (7.2, 7.9): Refine(1) each
-  → Low score (6.8): Discard
-
-Iteration 3: Aggregate(3) best nodes
-  → 1 synthesis node
-
-Iteration 4: Refine(1) synthesis
-  → Final output
-```
-
-### Pattern 2: Breadth-First Exploration
-
-**Use for**: Initial research on broad topics
-
-```
-Iteration 1: Generate(5) from root
-  → Score all 5 nodes
-  → KeepBestN(3)
-
-Iteration 2: Generate(2) from each of the 3 best nodes
-  → Score all 6 nodes
-  → KeepBestN(3)
-
-Iteration 3: Aggregate(3) best nodes
-  → Final synthesis
-```
-
-### Pattern 3: Depth-First Exploration
-
-**Use for**: Deep dive into specific high-value aspects
-
-```
-Iteration 1: Generate(3) from root
-  → Identify best node (e.g., score 8.5)
-
-Iteration 2: Generate(3) from best node only
-  → Score and KeepBestN(1)
-
-Iteration 3: Generate(2) from best child node
-  → Score and KeepBestN(1)
-
-Iteration 4: Refine(1) final deep finding
-```
-
-## Decision Logic
-
-- **Generate**: Starting new paths, exploring multiple aspects, diving deeper (threshold: score ≥ 7.0)
-- **Aggregate**: Multiple related findings exist, need comprehensive synthesis
-- **Refine**: Good finding needing polish, citation quality improvement (threshold: score ≥ 6.0)
-- **Prune**: Too many nodes, low-quality findings (criteria: score < 6.0 OR redundant)
-
-## Integration with 7-Phase Research Process
-
-- **Phase 2**: Use Generate to break main topic into subtopics
-- **Phase 3**: Use Generate + Score for multi-agent deployment
-- **Phase 4**: Use Aggregate to combine findings
-- **Phase 5**: Use Aggregate + Refine for synthesis
-- **Phase 6**: Use Score + Refine for quality assurance
-
-## Graph State Management
-
-Maintain graph state using this structure:
-
-```markdown
-## GoT Graph State
-
-### Nodes
-
-| Node ID | Content Summary   | Score | Parent  | Status   |
-| ------- | ----------------- | ----- | ------- | -------- |
-| root    | Research topic    | -     | -       | complete |
-| 1       | Aspect A findings | 7.2   | root    | complete |
-| final   | Synthesis         | 9.3   | [1,2,3] | complete |
-
-### Operations Log
-
-1. Generate(4) from root → nodes [1,2,3,4]
-2. Score all nodes → [7.2, 8.5, 6.8, 7.9]
-3. Aggregate(4) → final synthesis
-```
-
-## Tool Usage
-
-### Task Tool (Multi-Agent Deployment)
-
-Launch multiple Task agents in ONE response for Generate operations
-
-### TodoWrite (Progress Tracking)
-
-Track GoT operations: Generate(k), Score, KeepBestN(n), Aggregate(k), Refine(1)
-
-### Read/Write (Graph Persistence)
-
-Save graph state to files: `research_notes/got_graph_state.md`, `research_notes/got_operations_log.md`
-
-## Best Practices
-
-1. **Start Simple**: First iteration: Generate(3-5) from root
-2. **Prune Aggressively**: If score < 6.0, prune immediately
-3. **Aggregate Strategically**: After 2-3 rounds of generation
-4. **Refine Selectively**: Only refine nodes with score ≥ 7.0
-5. **Score Consistently**: Use the same criteria throughout
-
-## Examples
-
-See [examples.md](examples.md) for detailed usage examples.
-
-## Remember
-
-You are the **GoT Controller** - you orchestrate research as a graph, making strategic decisions about which paths to explore, which to prune, and how to combine findings.
-
-**Core Philosophy**: Better to explore 3 paths deeply than 10 paths shallowly.
-
-**Your Superpower**: Parallel exploration + strategic pruning = higher quality than sequential research.

package/bundled-skills/greptile/SKILL.md

@@ -1,72 +0,0 @@
----
-id: "greptile"
-title: "Greptile"
-category: "other"
-tags: ["greptile", "setup", "available tools", "example usage", "documentation"]
-triggers: []
-dependencies: []
-source: "E:/Bobo's Coding cache/.claude/skills/greptile"
----
-
-# Greptile
-
-[Greptile](https://greptile.com) is an AI code review agent for GitHub and GitLab that automatically reviews pull requests. This plugin connects Claude Code to your Greptile account, letting you view and resolve Greptile's review comments directly from your terminal.
-
-## Setup
-
-### 1. Create a Greptile Account
-
-Sign up at [greptile.com](https://greptile.com) and connect your GitHub or GitLab repositories.
-
-### 2. Get Your API Key
-
-1. Go to [API Settings](https://app.greptile.com/settings/api)
-2. Generate a new API key
-3. Copy the key
-
-### 3. Set Environment Variable
-
-Add to your shell profile (`.bashrc`, `.zshrc`, etc.):
-
-```bash
-export GREPTILE_API_KEY="your-api-key-here"
-```
-
-Then reload your shell or run `source ~/.zshrc`.
-
-## Available Tools
-
-### Pull Request Tools
-
-- `list_pull_requests` - List PRs with optional filtering by repo, branch, author, or state
-- `get_merge_request` - Get detailed PR info including review analysis
-- `list_merge_request_comments` - Get all comments on a PR with filtering options
-
-### Code Review Tools
-
-- `list_code_reviews` - List code reviews with optional filtering
-- `get_code_review` - Get detailed code review information
-- `trigger_code_review` - Start a new Greptile review on a PR
-
-### Comment Search
-
-- `search_greptile_comments` - Search across all Greptile review comments
-
-### Custom Context Tools
-
-- `list_custom_context` - List your organization's coding patterns and rules
-- `get_custom_context` - Get details for a specific pattern
-- `search_custom_context` - Search patterns by content
-- `create_custom_context` - Create a new coding pattern
-
-## Example Usage
-
-Ask Claude Code to:
-
-- "Show me Greptile's comments on my current PR and help me resolve them"
-- "What issues did Greptile find on PR #123?"
-- "Trigger a Greptile review on this branch"
-
-## Documentation
-
-For more information, visit [greptile.com/docs](https://greptile.com/docs).

package/bundled-skills/hookify/SKILL.md

@@ -1,376 +0,0 @@
----
-id: "hookify"
-title: "Hookify Plugin"
-category: "dev-tools"
-tags: ["hookify plugin", "overview", "quick start", "usage", "rule configuration format", "event types", "pattern syntax", "examples", "advanced usage", "management"]
-triggers: []
-dependencies: []
-source: "E:/Bobo's Coding cache/.claude/skills/hookify"
----
-
-# Hookify Plugin
-
-Easily create custom hooks to prevent unwanted behaviors by analyzing conversation patterns or from explicit instructions.
-
-## Overview
-
-The hookify plugin makes it simple to create hooks without editing complex `hooks.json` files. Instead, you create lightweight markdown configuration files that define patterns to watch for and messages to show when those patterns match.
-
-**Key features:**
-
-- 🎯 Analyze conversations to find unwanted behaviors automatically
-- 📝 Simple markdown configuration files with YAML frontmatter
-- 🔍 Regex pattern matching for powerful rules
-- 🚀 No coding required - just describe the behavior
-- 🔄 Easy enable/disable without restarting
-
-## Quick Start
-
-### 1. Create Your First Rule
-
-```bash
-/hookify Warn me when I use rm -rf commands
-```
-
-This analyzes your request and creates `.claude/hookify.warn-rm.local.md`.
-
-### 2. Test It Immediately
-
-**No restart needed!** Rules take effect on the very next tool use.
-
-Ask Claude to run a command that should trigger the rule:
-
-```
-Run rm -rf /tmp/test
-```
-
-You should see the warning message immediately!
-
-## Usage
-
-### Main Command: /hookify
-
-**With arguments:**
-
-```
-/hookify Don't use console.log in TypeScript files
-```
-
-Creates a rule from your explicit instructions.
-
-**Without arguments:**
-
-```
-/hookify
-```
-
-Analyzes recent conversation to find behaviors you've corrected or been frustrated by.
-
-### Helper Commands
-
-**List all rules:**
-
-```
-/hookify:list
-```
-
-**Configure rules interactively:**
-
-```
-/hookify:configure
-```
-
-Enable/disable existing rules through an interactive interface.
-
-**Get help:**
-
-```
-/hookify:help
-```
-
-## Rule Configuration Format
-
-### Simple Rule (Single Pattern)
-
-`.claude/hookify.dangerous-rm.local.md`:
-
-```markdown
----
-name: block-dangerous-rm
-enabled: true
-event: bash
-pattern: rm\s+-rf
-action: block
----
-
-⚠️ **Dangerous rm command detected!**
-
-This command could delete important files. Please:
-
-- Verify the path is correct
-- Consider using a safer approach
-- Make sure you have backups
-```
-
-**Action field:**
-
-- `warn`: Shows warning but allows operation (default)
-- `block`: Prevents operation from executing (PreToolUse) or stops session (Stop events)
-
-### Advanced Rule (Multiple Conditions)
-
-`.claude/hookify.sensitive-files.local.md`:
-
-```markdown
----
-name: warn-sensitive-files
-enabled: true
-event: file
-action: warn
-conditions:
-  - field: file_path
-    operator: regex_match
-    pattern: \.env$|credentials|secrets
-  - field: new_text
-    operator: contains
-    pattern: KEY
----
-
-🔐 **Sensitive file edit detected!**
-
-Ensure credentials are not hardcoded and file is in .gitignore.
-```
-
-**All conditions must match** for the rule to trigger.
-
-## Event Types
-
-- **`bash`**: Triggers on Bash tool commands
-- **`file`**: Triggers on Edit, Write, MultiEdit tools
-- **`stop`**: Triggers when Claude wants to stop (for completion checks)
-- **`prompt`**: Triggers on user prompt submission
-- **`all`**: Triggers on all events
-
-## Pattern Syntax
-
-Use Python regex syntax:
-
-| Pattern          | Matches              | Example             |
-| ---------------- | -------------------- | ------------------- |
-| `rm\s+-rf`       | rm -rf               | rm -rf /tmp         |
-| `console\.log\(` | console.log(         | console.log("test") |
-| `(eval\|exec)\(` | eval( or exec(       | eval("code")        |
-| `\.env$`         | files ending in .env | .env, .env.local    |
-| `chmod\s+777`    | chmod 777            | chmod 777 file.txt  |
-
-**Tips:**
-
-- Use `\s` for whitespace
-- Escape special chars: `\.` for literal dot
-- Use `|` for OR: `(foo|bar)`
-- Use `.*` to match anything
-- Set `action: block` for dangerous operations
-- Set `action: warn` (or omit) for informational warnings
-
-## Examples
-
-### Example 1: Block Dangerous Commands
-
-```markdown
----
-name: block-destructive-ops
-enabled: true
-event: bash
-pattern: rm\s+-rf|dd\s+if=|mkfs|format
-action: block
----
-
-🛑 **Destructive operation detected!**
-
-This command can cause data loss. Operation blocked for safety.
-Please verify the exact path and use a safer approach.
-```
-
-**This rule blocks the operation** - Claude will not be allowed to execute these commands.
-
-### Example 2: Warn About Debug Code
-
-```markdown
----
-name: warn-debug-code
-enabled: true
-event: file
-pattern: console\.log\(|debugger;|print\(
-action: warn
----
-
-🐛 **Debug code detected**
-
-Remember to remove debugging statements before committing.
-```
-
-**This rule warns but allows** - Claude sees the message but can still proceed.
-
-### Example 3: Require Tests Before Stopping
-
-```markdown
----
-name: require-tests-run
-enabled: false
-event: stop
-action: block
-conditions:
-  - field: transcript
-    operator: not_contains
-    pattern: npm test|pytest|cargo test
----
-
-**Tests not detected in transcript!**
-
-Before stopping, please run tests to verify your changes work correctly.
-```
-
-**This blocks Claude from stopping** if no test commands appear in the session transcript. Enable only when you want strict enforcement.
-
-## Advanced Usage
-
-### Multiple Conditions
-
-Check multiple fields simultaneously:
-
-```markdown
----
-name: api-key-in-typescript
-enabled: true
-event: file
-conditions:
-  - field: file_path
-    operator: regex_match
-    pattern: \.tsx?$
-  - field: new_text
-    operator: regex_match
-    pattern: (API_KEY|SECRET|TOKEN)\s*=\s*["']
----
-
-🔐 **Hardcoded credential in TypeScript!**
-
-Use environment variables instead of hardcoded values.
-```
-
-### Operators Reference
-
-- `regex_match`: Pattern must match (most common)
-- `contains`: String must contain pattern
-- `equals`: Exact string match
-- `not_contains`: String must NOT contain pattern
-- `starts_with`: String starts with pattern
-- `ends_with`: String ends with pattern
-
-### Field Reference
-
-**For bash events:**
-
-- `command`: The bash command string
-
-**For file events:**
-
-- `file_path`: Path to file being edited
-- `new_text`: New content being added (Edit, Write)
-- `old_text`: Old content being replaced (Edit only)
-- `content`: File content (Write only)
-
-**For prompt events:**
-
-- `user_prompt`: The user's submitted prompt text
-
-**For stop events:**
-
-- Use general matching on session state
-
-## Management
-
-### Enable/Disable Rules
-
-**Temporarily disable:**
-Edit the `.local.md` file and set `enabled: false`
-
-**Re-enable:**
-Set `enabled: true`
-
-**Or use interactive tool:**
-
-```
-/hookify:configure
-```
-
-### Delete Rules
-
-Simply delete the `.local.md` file:
-
-```bash
-rm .claude/hookify.my-rule.local.md
-```
-
-### View All Rules
-
-```
-/hookify:list
-```
-
-## Installation
-
-This plugin is part of the Claude Code Marketplace. It should be auto-discovered when the marketplace is installed.
-
-**Manual testing:**
-
-```bash
-cc --plugin-dir /path/to/hookify
-```
-
-## Requirements
-
-- Python 3.7+
-- No external dependencies (uses stdlib only)
-
-## Troubleshooting
-
-**Rule not triggering:**
-
-1. Check rule file exists in `.claude/` directory (in project root, not plugin directory)
-2. Verify `enabled: true` in frontmatter
-3. Test regex pattern separately
-4. Rules should work immediately - no restart needed
-5. Try `/hookify:list` to see if rule is loaded
-
-**Import errors:**
-
-- Ensure Python 3 is available: `python3 --version`
-- Check hookify plugin is installed
-
-**Pattern not matching:**
-
-- Test regex: `python3 -c "import re; print(re.search(r'pattern', 'text'))"`
-- Use unquoted patterns in YAML to avoid escaping issues
-- Start simple, then add complexity
-
-**Hook seems slow:**
-
-- Keep patterns simple (avoid complex regex)
-- Use specific event types (bash, file) instead of "all"
-- Limit number of active rules
-
-## Contributing
-
-Found a useful rule pattern? Consider sharing example files via PR!
-
-## Future Enhancements
-
-- Severity levels (error/warning/info distinctions)
-- Rule templates library
-- Interactive pattern builder
-- Hook testing utilities
-- JSON format support (in addition to markdown)
-
-## License
-
-MIT License