claco 2.0.0

a CLI tool for boosting Claude Code productive.
Documentation 
1
2
3
4
5
6
7
8
9
10
11
12
13
14
15
16
17
18
19
20
21
22
23
24
25
26
27
28
29
30
31
32
33
34
35
36
37
38
39
40
41
42
43
44
45
46
47
48
49
50
51
52
53
54
55
56
57
58
59
60
61
62
63
64

# Plan Wave 2: Lots of Enhancement
- hooks manager
- slash commands manager

## Background

### about slash commands

https://docs.anthropic.com/en/docs/claude-code/slash-commands

> Namespacing
> Organize commands in subdirectories. The subdirectories determine the command’s full name. The description will show whether the command comes from the project directory (.claude/commands) or the user-level directory (~/.claude/commands).
> 
> Conflicts between user and project level commands are not supported. Otherwise, multiple commands with the same base file name can coexist.
> 
> For example, a file at .claude/commands/frontend/component.md creates the command /frontend:component with description showing “(project)”. Meanwhile, a file at ~/.claude/commands/component.md creates the command /component with description showing “(user)”.

- glob the command markdown files when need search and list
- filename is the command name

### about hooks

https://docs.anthropic.com/en/docs/claude-code/hooks

> Claude Code hooks are configured in your settings files:
> 
> ~/.claude/settings.json - User settings
> .claude/settings.json - Project settings
> .claude/settings.local.json - Local project settings (not committed)

```json
{
  "hooks": {
    "PreToolUse|ToolPattern|Notification|Stop|SubagentStop|PreCompact": [
      {
        "matcher": "Task|Bash|Glob|Grep|Read|Edit|MultiEdit|Write|WebFetch|WebSearch", // only applicable for PreToolUse and PostToolUse. * is invalid, instead use "".
        "hooks": [
          {
            "type": "command", // Currently only "command" is supported
            "command": "your-command-here" // The bash command to execute
          }
        ]
      }
    ]
  }
}
```

- no name, display as ${matcher}:${command}

## New subcommands

default scope is current project.

### feature#1 manage slash commands
- `claco commands list --scope=user|project` list all the slash commands
- `claco commands import --scope=user|project $url` import from markdown file from github
- `claco commands clean --scope=user|project` remove all slash commands, need confirm
- `claco commands generate $prompt` generate command from prompt via claude code itself

### feature#2 manage hooks
- `claco hooks list --scope=user|project` list all the slash commands
- `claco hooks add --scope=user|project --event $event --matcher $matcher --command $command`
- `claco hooks del --interactive` list hooks and wait user to pick then delete from config files