vibe-action 0.2.2

Command router — execute shell commands and LLM prompts via simple YAML actions.
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
65

version: 0.0.1

name: comment
about: Replace TODO with a meaningful comment
notify: true

# IDE plugin integration: maps argument names to IDE contexts
api:
  # Target for the final result (replace | clipboard | dialog)
  output: replace
  # Source for the {query} tag (query | query|file_path | query|prompt | etc)
  input: query

actions:
  # Read input from query (prioritize file path if valid, otherwise use raw text)
  - tag: tag_content
    run: cmd
    expect: string
    check: .+
    action:
      - when: '{query|file_path|empty:not}'
        then: cat "{query|file_path|load}"
      - when: '{query|empty:not}'
        then: echo "{query}"
      - when: 'true'
        then: echo "ERROR - No input provided"

  # Replace TODO placeholders with intelligent technical comments
  - tag: tag_comment
    run: small
    expect: string
    action: |
      [Task]
      Replace EVERY "TODO" or "@todo" placeholder in the code with an intelligent technical comment in English.

      [Supported Languages]
      Most likely languages: Rust, Python, TypeScript, JavaScript, Java, Go, C#, Kotlin, Swift, Dart, Bash, Batch, ArkTS, Markdown.
      If you are certain the code is in another language, specify it.

      [Rules]
      1. Do NOT modify, reformat, or optimize any actual programming code. Your only task is to update the TODO comments.
      2. For file/module placeholders, write a high-level summary strictly in TWO short sentences (one per line).
      3. Start each sentence directly with an action verb or noun (do NOT use "This module...", "It...").
      4. For structures, fields, or methods, write a brief description (max 7 words). Do NOT start with "Represents...", "The...".
      5. Keep the exact same comment syntax and structure used around the TODO placeholder.
      6. Output the ENTIRE code block strictly wrapped in a markdown code fence, starting with ```language (e.g., ```java) and ending with ```.
         Use the language name from the [Supported Languages] list. If unknown, use generic ```.

      [Example]
      ```language
      // Short description of the module.
      // Second sentence with details.

      /// Brief description of the function.
      function doSomething() { ... }
      ```

      [Code]
      {tag_content}

  # Copy result to clipboard and output
  - tag: tag_clipboard
    run: value
    expect: string
    action: '{tag_comment|clipboard}'