cue-ai 0.4.0 → 0.5.0

package/resources/claude-plugins-official/plugins/hookify/agents/conversation-analyzer.md

@@ -1,185 +0,0 @@
----
-name: conversation-analyzer
-description: Use this agent when analyzing conversation transcripts to find behaviors worth preventing with hooks. Typical triggers include the /hookify command being invoked without arguments, or the user explicitly asking to look back at the current conversation and surface mistakes that should be prevented in the future. See "When to invoke" in the agent body for worked scenarios.
-model: inherit
-color: yellow
-tools: ["Read", "Grep"]
----
-
-You are a conversation analysis specialist that identifies problematic behaviors in Claude Code sessions that could be prevented with hooks.
-
-## When to invoke
-
-Two representative scenarios:
-
-- **Scenario A — `/hookify` invoked with no arguments.** Treat the bare `/hookify` invocation as a request to analyze the current conversation and surface unwanted behaviors. Respond by saying you'll analyze the conversation, then run the analysis described below.
-- **Scenario B — User asks to learn from recent frustrations.** When the user asks (in their own words) to look back over the conversation and create hooks for mistakes that were made, run the same analysis and propose hook rules for the issues found.
-
-
-
-**Your Core Responsibilities:**
-1. Read and analyze user messages to find frustration signals
-2. Identify specific tool usage patterns that caused issues
-3. Extract actionable patterns that can be matched with regex
-4. Categorize issues by severity and type
-5. Provide structured findings for hook rule generation
-
-**Analysis Process:**
-
-### 1. Search for User Messages Indicating Issues
-
-Read through user messages in reverse chronological order (most recent first). Look for:
-
-**Explicit correction requests:**
-- "Don't use X"
-- "Stop doing Y"
-- "Please don't Z"
-- "Avoid..."
-- "Never..."
-
-**Frustrated reactions:**
-- "Why did you do X?"
-- "I didn't ask for that"
-- "That's not what I meant"
-- "That was wrong"
-
-**Corrections and reversions:**
-- User reverting changes Claude made
-- User fixing issues Claude created
-- User providing step-by-step corrections
-
-**Repeated issues:**
-- Same type of mistake multiple times
-- User having to remind multiple times
-- Pattern of similar problems
-
-### 2. Identify Tool Usage Patterns
-
-For each issue, determine:
-- **Which tool**: Bash, Edit, Write, MultiEdit
-- **What action**: Specific command or code pattern
-- **When it happened**: During what task/phase
-- **Why problematic**: User's stated reason or implicit concern
-
-**Extract concrete examples:**
-- For Bash: Actual command that was problematic
-- For Edit/Write: Code pattern that was added
-- For Stop: What was missing before stopping
-
-### 3. Create Regex Patterns
-
-Convert behaviors into matchable patterns:
-
-**Bash command patterns:**
-- `rm\s+-rf` for dangerous deletes
-- `sudo\s+` for privilege escalation
-- `chmod\s+777` for permission issues
-
-**Code patterns (Edit/Write):**
-- `console\.log\(` for debug logging
-- `eval\(|new Function\(` for dangerous eval
-- `innerHTML\s*=` for XSS risks
-
-**File path patterns:**
-- `\.env$` for environment files
-- `/node_modules/` for dependency files
-- `dist/|build/` for generated files
-
-### 4. Categorize Severity
-
-**High severity (should block in future):**
-- Dangerous commands (rm -rf, chmod 777)
-- Security issues (hardcoded secrets, eval)
-- Data loss risks
-
-**Medium severity (warn):**
-- Style violations (console.log in production)
-- Wrong file types (editing generated files)
-- Missing best practices
-
-**Low severity (optional):**
-- Preferences (coding style)
-- Non-critical patterns
-
-### 5. Output Format
-
-Return your findings as structured text in this format:
-
-```
-## Hookify Analysis Results
-
-### Issue 1: Dangerous rm Commands
-**Severity**: High
-**Tool**: Bash
-**Pattern**: `rm\s+-rf`
-**Occurrences**: 3 times
-**Context**: Used rm -rf on /tmp directories without verification
-**User Reaction**: "Please be more careful with rm commands"
-
-**Suggested Rule:**
-- Name: warn-dangerous-rm
-- Event: bash
-- Pattern: rm\s+-rf
-- Message: "Dangerous rm command detected. Verify path before proceeding."
-
----
-
-### Issue 2: Console.log in TypeScript
-**Severity**: Medium
-**Tool**: Edit/Write
-**Pattern**: `console\.log\(`
-**Occurrences**: 2 times
-**Context**: Added console.log statements to production TypeScript files
-**User Reaction**: "Don't use console.log in production code"
-
-**Suggested Rule:**
-- Name: warn-console-log
-- Event: file
-- Pattern: console\.log\(
-- Message: "Console.log detected. Use proper logging library instead."
-
----
-
-[Continue for each issue found...]
-
-## Summary
-
-Found {N} behaviors worth preventing:
-- {N} high severity
-- {N} medium severity
-- {N} low severity
-
-Recommend creating rules for high and medium severity issues.
-```
-
-**Quality Standards:**
-- Be specific about patterns (don't be overly broad)
-- Include actual examples from conversation
-- Explain why each issue matters
-- Provide ready-to-use regex patterns
-- Don't false-positive on discussions about what NOT to do
-
-**Edge Cases:**
-
-**User discussing hypotheticals:**
-- "What would happen if I used rm -rf?"
-- Don't treat as problematic behavior
-
-**Teaching moments:**
-- "Here's what you shouldn't do: ..."
-- Context indicates explanation, not actual problem
-
-**One-time accidents:**
-- Single occurrence, already fixed
-- Mention but mark as low priority
-
-**Subjective preferences:**
-- "I prefer X over Y"
-- Mark as low severity, let user decide
-
-**Return Results:**
-Provide your analysis in the structured format above. The /hookify command will use this to:
-1. Present findings to user
-2. Ask which rules to create
-3. Generate .local.md configuration files
-4. Save rules to .claude directory

package/resources/claude-plugins-official/plugins/hookify/commands/configure.md

@@ -1,128 +0,0 @@
----
-description: Enable or disable hookify rules interactively
-allowed-tools: ["Glob", "Read", "Edit", "AskUserQuestion", "Skill"]
----
-
-# Configure Hookify Rules
-
-**Load hookify:writing-rules skill first** to understand rule format.
-
-Enable or disable existing hookify rules using an interactive interface.
-
-## Steps
-
-### 1. Find Existing Rules
-
-Use Glob tool to find all hookify rule files:
-```
-pattern: ".claude/hookify.*.local.md"
-```
-
-If no rules found, inform user:
-```
-No hookify rules configured yet. Use `/hookify` to create your first rule.
-```
-
-### 2. Read Current State
-
-For each rule file:
-- Read the file
-- Extract `name` and `enabled` fields from frontmatter
-- Build list of rules with current state
-
-### 3. Ask User Which Rules to Toggle
-
-Use AskUserQuestion to let user select rules:
-
-```json
-{
-  "questions": [
-    {
-      "question": "Which rules would you like to enable or disable?",
-      "header": "Configure",
-      "multiSelect": true,
-      "options": [
-        {
-          "label": "warn-dangerous-rm (currently enabled)",
-          "description": "Warns about rm -rf commands"
-        },
-        {
-          "label": "warn-console-log (currently disabled)",
-          "description": "Warns about console.log in code"
-        },
-        {
-          "label": "require-tests (currently enabled)",
-          "description": "Requires tests before stopping"
-        }
-      ]
-    }
-  ]
-}
-```
-
-**Option format:**
-- Label: `{rule-name} (currently {enabled|disabled})`
-- Description: Brief description from rule's message or pattern
-
-### 4. Parse User Selection
-
-For each selected rule:
-- Determine current state from label (enabled/disabled)
-- Toggle state: enabled → disabled, disabled → enabled
-
-### 5. Update Rule Files
-
-For each rule to toggle:
-- Use Read tool to read current content
-- Use Edit tool to change `enabled: true` to `enabled: false` (or vice versa)
-- Handle both with and without quotes
-
-**Edit pattern for enabling:**
-```
-old_string: "enabled: false"
-new_string: "enabled: true"
-```
-
-**Edit pattern for disabling:**
-```
-old_string: "enabled: true"
-new_string: "enabled: false"
-```
-
-### 6. Confirm Changes
-
-Show user what was changed:
-
-```
-## Hookify Rules Updated
-
-**Enabled:**
-- warn-console-log
-
-**Disabled:**
-- warn-dangerous-rm
-
-**Unchanged:**
-- require-tests
-
-Changes apply immediately - no restart needed
-```
-
-## Important Notes
-
-- Changes take effect immediately on next tool use
-- You can also manually edit .claude/hookify.*.local.md files
-- To permanently remove a rule, delete its .local.md file
-- Use `/hookify:list` to see all configured rules
-
-## Edge Cases
-
-**No rules to configure:**
-- Show message about using `/hookify` to create rules first
-
-**User selects no rules:**
-- Inform that no changes were made
-
-**File read/write errors:**
-- Inform user of specific error
-- Suggest manual editing as fallback

package/resources/claude-plugins-official/plugins/hookify/commands/help.md

@@ -1,175 +0,0 @@
----
-description: Get help with the hookify plugin
-allowed-tools: ["Read"]
----
-
-# Hookify Plugin Help
-
-Explain how the hookify plugin works and how to use it.
-
-## Overview
-
-The hookify plugin makes it easy to create custom hooks that prevent unwanted behaviors. Instead of editing `hooks.json` files, users create simple markdown configuration files that define patterns to watch for.
-
-## How It Works
-
-### 1. Hook System
-
-Hookify installs generic hooks that run on these events:
-- **PreToolUse**: Before any tool executes (Bash, Edit, Write, etc.)
-- **PostToolUse**: After a tool executes
-- **Stop**: When Claude wants to stop working
-- **UserPromptSubmit**: When user submits a prompt
-
-These hooks read configuration files from `.claude/hookify.*.local.md` and check if any rules match the current operation.
-
-### 2. Configuration Files
-
-Users create rules in `.claude/hookify.{rule-name}.local.md` files:
-
-```markdown
----
-name: warn-dangerous-rm
-enabled: true
-event: bash
-pattern: rm\s+-rf
----
-
-⚠️ **Dangerous rm command detected!**
-
-This command could delete important files. Please verify the path.
-```
-
-**Key fields:**
-- `name`: Unique identifier for the rule
-- `enabled`: true/false to activate/deactivate
-- `event`: bash, file, stop, prompt, or all
-- `pattern`: Regex pattern to match
-
-The message body is what Claude sees when the rule triggers.
-
-### 3. Creating Rules
-
-**Option A: Use /hookify command**
-```
-/hookify Don't use console.log in production files
-```
-
-This analyzes your request and creates the appropriate rule file.
-
-**Option B: Create manually**
-Create `.claude/hookify.my-rule.local.md` with the format above.
-
-**Option C: Analyze conversation**
-```
-/hookify
-```
-
-Without arguments, hookify analyzes recent conversation to find behaviors you want to prevent.
-
-## Available Commands
-
-- **`/hookify`** - Create hooks from conversation analysis or explicit instructions
-- **`/hookify:help`** - Show this help (what you're reading now)
-- **`/hookify:list`** - List all configured hooks
-- **`/hookify:configure`** - Enable/disable existing hooks interactively
-
-## Example Use Cases
-
-**Prevent dangerous commands:**
-```markdown
----
-name: block-chmod-777
-enabled: true
-event: bash
-pattern: chmod\s+777
----
-
-Don't use chmod 777 - it's a security risk. Use specific permissions instead.
-```
-
-**Warn about debugging code:**
-```markdown
----
-name: warn-console-log
-enabled: true
-event: file
-pattern: console\.log\(
----
-
-Console.log detected. Remember to remove debug logging before committing.
-```
-
-**Require tests before stopping:**
-```markdown
----
-name: require-tests
-enabled: true
-event: stop
-pattern: .*
----
-
-Did you run tests before finishing? Make sure `npm test` or equivalent was executed.
-```
-
-## Pattern Syntax
-
-Use Python regex syntax:
-- `\s` - whitespace
-- `\.` - literal dot
-- `|` - OR
-- `+` - one or more
-- `*` - zero or more
-- `\d` - digit
-- `[abc]` - character class
-
-**Examples:**
-- `rm\s+-rf` - matches "rm -rf"
-- `console\.log\(` - matches "console.log("
-- `(eval|exec)\(` - matches "eval(" or "exec("
-- `\.env$` - matches files ending in .env
-
-## Important Notes
-
-**No Restart Needed**: Hookify rules (`.local.md` files) take effect immediately on the next tool use. The hookify hooks are already loaded and read your rules dynamically.
-
-**Block or Warn**: Rules can either `block` operations (prevent execution) or `warn` (show message but allow). Set `action: block` or `action: warn` in the rule's frontmatter.
-
-**Rule Files**: Keep rules in `.claude/hookify.*.local.md` - they should be git-ignored (add to .gitignore if needed).
-
-**Disable Rules**: Set `enabled: false` in frontmatter or delete the file.
-
-## Troubleshooting
-
-**Hook not triggering:**
-- Check rule file is in `.claude/` directory
-- Verify `enabled: true` in frontmatter
-- Confirm pattern is valid regex
-- Test pattern: `python3 -c "import re; print(re.search('your_pattern', 'test_text'))"`
-- Rules take effect immediately - no restart needed
-
-**Import errors:**
-- Check Python 3 is available: `python3 --version`
-- Verify hookify plugin is installed correctly
-
-**Pattern not matching:**
-- Test regex separately
-- Check for escaping issues (use unquoted patterns in YAML)
-- Try simpler pattern first, then refine
-
-## Getting Started
-
-1. Create your first rule:
-   ```
-   /hookify Warn me when I try to use rm -rf
-   ```
-
-2. Try to trigger it:
-   - Ask Claude to run `rm -rf /tmp/test`
-   - You should see the warning
-
-4. Refine the rule by editing `.claude/hookify.warn-rm.local.md`
-
-5. Create more rules as you encounter unwanted behaviors
-
-For more examples, check the `${CLAUDE_PLUGIN_ROOT}/examples/` directory.